Developer · Remote MCP server
Relaystation
Pay-per-call agent infrastructure: file storage & handoff, compute tools, messaging, e-sign, KYC.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
ai.relaystation/relaystation- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-07-09
- Updated
- 2026-07-09
- Publisher
- ai.relaystation
- Namespace
- Namespace verified by the MCP Registry via the domain relaystation.ai · how
- Website
- relaystation.ai
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://api.relaystation.ai/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- relaystation v1 · protocol 2025-06-18
- Tools discovered
14 - show names
ask_operator,message_agent,create_agent_address,create_baton,read_baton,append_to_baton,mint_token,balance,create_topup_link,search_tools,describe_tool,call_tool,create_contract,sign_contract- Checked on
- 2026-10-05
How to connect Relaystation
Relaystation is a remote MCP server: there is nothing to install. Its endpoint is https://api.relaystation.ai/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| Regulatory SignalsAudit GitHub repos for security, compliance, and EU AI Act exposure from Claude or Cursor. | Local · stdio |
| RektREKT Store - browse and buy REKT drinks with AI-discounted pricing from any MCP client. | Local · stdio |
| RelayMCP relay server for Claude Desktop <-> Claude Code communication. | Local · stdio |
| RelayShield Security IntelligenceBreach, SIM swap, infostealer, domain lookalikes, MCP registry risk, prompt-injection detection. | Local · stdio |
| Release GatePre-deploy security auditor for AI agent code - the risks generic SAST misses. | Local · stdio |
| Release RadarCorrelate GitHub releases with Sentry issues and PagerDuty incidents. | Remote · HTTPLive check: ✓ handshake |
| RelinInspect webhook health, investigate delivery failures, configure sources, and replay events. | Remote · HTTPLive check: ✓ handshake |
| RelvatoWebsite monitoring: add sites, configure and run monitors, read health, review results, apply fixes. | Remote · HTTPLive check: ✓ handshake |