io.github.storylinkpro/storylink-mcp
Storylink
Is the Storylink MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Ask about your Instagram stories, posts and reels in Storylink: views, reach and top content.
needs auth probed 2026-11-15 · HTTP 401
Streamable HTTP error: Error POSTing to endpoint: {"error":{"code":"unauthorized","message":"Missing Authorization header","docs_url":"https://storylink.pro/dev- Endpoint
- https://storylink.pro/mcp (streamable-http)
- Host
- storylink.pro
- Package
- The publisher's package npm:storylink-mcp did not list its tools in the container: needs env, MCP error -32000: Connection closed storylink-mcp: STORYLINK_API_KEY is not set. Create an API key on the Developers page in Storylink and set STORYLINK_API_KEY.
- Getting access
- The server answers HTTP 401 with no WWW-Authenticate header and no OAuth metadata, so the publisher's documentation is the only guide.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/storylinkpro/storylink-mcp
- Website
- https://storylink.pro
- Registry
- active, updated 2026-11-09 · registry entry
Compare this server with others.
More servers
Servers that mention instagram or content.
- Adrio ai.adrio/adrio · needs auth
- AutoRFP.ai ai.autorfp/mcp · needs auth
- Web Content & URL Tools ai.avaloncompany/web-content-url-tools · needs auth
- AwrAIter — Telegram channels ai.awraiter/telegram · needs auth
- Autoposting ai.autoposting/autoposting · not MCP
- SEO Content Factory ai.b77/seo-content-factory · needs auth
- BAMF.ai ai.bamf/bamf · not MCP
- BittleBits GEO Assistant ai.bittlebits/bittlebits · no DNS
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.