com.getridian/agent-mailbox
Agent Mailbox by Ridian
Is the Agent Mailbox by Ridian MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Email inboxes for AI agents at ridianmail.com: read, draft, send, attachments. EU-hosted.
needs auth probed 2026-11-15 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token"}- Endpoint
- https://api.getridian.com/mcp/mailbox (streamable-http)
- Host
- api.getridian.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.getridian.com/mcp/mailbox registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server api.getridian.com, PKCE S256, grants authorization_code, client_credentials, refresh_token.
Scopes inbox:read inbox:write inbox:send inbox:manage feedback:write.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://getridian.com/?ref=mcp_registry
- Registry
- active, updated 2026-11-11 · registry entry
Compare this server with others.
More servers
Other registry entries on api.getridian.com.
- Ridian Calendar Feeds com.getridian/calendar-feeds · needs auth
- Ridian com.getridian/ridian · needs auth
- Ridian Scheduling com.getridian/scheduling · needs auth
Servers that mention mailbox.
- mailmcp ai.mailmcp/mailmcp · needs auth
- ReplyLayer ai.replylayer/replylayer · needs auth
- Conduit Mail app.conduitmail/conduit-mail · needs auth
- JustEmails app.justemails/mcp · needs auth
- mailbox.bot bot.mailbox/mailbox · alive
- Multi Mail co.lumman/mail · needs auth
- adbtd com.adbtd/mcp · needs auth
- com.anymailmcp/mail · needs auth
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.