io.github.Reelspan/mcp

Reelspan

Is the Reelspan MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-14.

Publish videos, photos and text to TikTok, YouTube, Instagram, X, LinkedIn and more.

needs auth probed 2026-11-14 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32000,"message":"missing authorization header"},"id":null}

Endpoint: https://api.reelspan.com/mcp (streamable-http)
Host: api.reelspan.com
Package: The publisher's package npm:@reelspan/mcp did not list its tools in the container: needs network, MCP error -32000: Connection closed reelspan-mcp: Could not reach the Reelspan MCP at https://api.reelspan.com/mcp: fetch failed.
Getting access: OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.reelspan.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server app.reelspan.com, PKCE S256, grants authorization_code, client_credentials, refresh_token.
Read from the server's public OAuth metadata, without a token. Method.
Repository: https://github.com/Reelspan/reelspan-mcp
Website: https://reelspan.com/docs/mcp
Registry: active, updated 2026-11-11 · registry entry

More servers

Servers that mention instagram or linkedin.

Adako: ad ops for AI assistants ai.adako/ads · needs auth
ai.adside/adside · needs auth
Adrio ai.adrio/adrio · needs auth
Autoposting ai.autoposting/autoposting · not MCP
BAMF.ai ai.bamf/bamf · not MCP
Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram ai.bowmark/bowmark · alive
LinkedIn MCP Server ai.com.mcp/linkedin · not MCP
DataForB2B ai.dataforb2b/dataforb2b · needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

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.