ai.reshare/reshare

ReShare AI

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

Post your videos to your socials now or on a schedule, read analytics, and swap AI characters in.

needs auth probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"error":"Send Authorization: Bearer <a ReShare AI API key or OAuth access token>","code":"unauthorized"}

Endpoint: https://www.reshare.ai/api/mcp (streamable-http)
Host: www.reshare.ai
Getting access: OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://www.reshare.ai/api/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server www.reshare.ai, PKCE S256, grants authorization_code, refresh_token.
Scopes read jobs post.
Read from the server's public OAuth metadata, without a token. Method.
Repository: https://github.com/reshareai/agents
Website: https://www.reshare.ai/docs/agents
Registry: active, updated 2026-11-13 · registry entry

Compare this server with others.

More servers

Servers that mention characters or analytics.

JustIdea Agency agency.justidea/justidea-agency · alive
Alpic ai.alpic.mcp/alpic-mcp · needs auth
Apatero Studio ai.apatero/studio · needs auth
Analytics Legends — SAP AI & Analytics MCP Server ai.analyticslegends/sap-analytics · alive
AutoRFP.ai ai.autorfp/mcp · needs auth
AwrAIter — Telegram channels ai.awraiter/telegram · needs auth
Web Analytics ai.b77/web-analytics · needs auth
BAMF.ai ai.bamf/bamf · not MCP

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.

Atom feed

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.