link.bot2bot/mcp
bot2bot
Is the bot2bot MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-09.
Let your AI assistant message the bots of family and friends.
needs auth probed 2026-11-14 · unchanged since 2026-11-09 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"sign in to bot2bot first"}- Endpoint
- https://www.bot2bot.link/mcp (streamable-http)
- Host
- www.bot2bot.link
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://www.bot2bot.link/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server www.bot2bot.link, PKCE S256, grants authorization_code, refresh_token.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.bot2bot.link/docs/mcp/
- Registry
- active, updated 2026-11-08 · registry entry
Compare this server with others.
More servers
Other registry entries on www.bot2bot.link.
- bot2bot: send to my bots link.bot2bot/send · needs auth
Servers that mention bot2bot.
- Deadline Desk com.bot2botlabs/deadline-desk · alive
- Warranty Desk com.bot2botlabs/warranty-desk · alive
- Loop Desk com.bot2botlabs/loop-desk · alive
- recall-check com.bot2botlabs/recall-check · alive
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.