com.relaydin/relay
Relay
Is the Relay MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-13.
Outreach campaigns, one inbox and safety limits for the LinkedIn accounts an agency manages.
needs auth probed 2026-11-14 · unchanged since 2026-11-13 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Missing API key. Send \"Authorization: Bearer rl_live_…\" (- Endpoint
- https://app.relaydin.com/mcp (streamable-http)
- Host
- app.relaydin.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.relaydin.com/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 app.relaydin.com, PKCE S256, grants authorization_code, refresh_token.
Scopes read write send.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://relaydin.com
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention relay.
- ai.orgsdk/mcp · no DNS
- PigeonRelay ai.pigeonrelay/pigeonrelay · needs auth
- Relaystation ai.relaystation/relaystation · alive
- app.allagents/directory · alive
- France Logistics (buy Mondial Relay + more labels + tracking via Shippo) app.wishpool/france-logistics-mcp · no DNS
- Uruguay Invoices (DGI e-Factura CFE, merchant-signed SOAP relay) app.wishpool/uruguay-invoice-mcp · no DNS
- Agent Email List — Free SMTP Relay for AI Agents com.agentemaillist.ai/free-transactional-email-smtp-relay · alive
- AlfaNest Relay com.alfanestlabs/relay · 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.