Relaystation

warnings

api.relaystation.ai

Pay-per-call agent infrastructure: file storage & handoff, compute tools, messaging, e-sign, KYC.

https://api.relaystation.ai/mcpWebsiteOAuthMCP 2025-06-18vv1last checked 24 Aug 2026spoke MCP on 2 of 2 checks (30 days)initialize in 621 ms

How to authenticate

Checked against the endpoint by our probe on 24 Aug 2026. These are the capabilities the server advertises, not a prediction about any particular client.

Scheme	OAuth
Issuer	https://api.relaystation.ai
Dynamic client registration	✓Advertised (RFC 7591)
Client ID Metadata Document	✕Not advertised
PKCE	✓S256
Grant types	authorization_code, refresh_token
Scopes	products:call, account:read
Protected-resource metadata	✓Published (RFC 9728)
Anonymous access	Handshake succeeds; 14 tools listable
Credentials demanded in prose	✕ask_operator, read_baton, balance, create_contract, sign_contract These tools are listed anonymously and their own descriptions ask for an account or key, but no challenge is issued — so a client has nothing to act on and the refusal arrives as a tool error.
Documentation	https://relaystation.ai/docs/mcp

What the probe found

warningTools needing credentials are listed without a challenge

5 of the 14 tools listed anonymously say in their own descriptions that they need an account or a key (ask_operator, read_baton, balance, create_contract, sign_contract), but the endpoint issued no WWW-Authenticate challenge. The requirement is stated only in prose, so a call reaches the tool and comes back as a tool error instead of an authorization step.

14 tools usable without signing in

The server exposes a public surface before authorization: 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.

Tools

append_to_batonask_operatorbalancecall_toolcreate_agent_addresscreate_batoncreate_contractcreate_topup_linkdescribe_toolmessage_agentmint_tokenread_batonsearch_toolssign_contract

Contract history

24 Aug 2026vv1first recorded contract

Get alerted when this contract changes

Depend on this server? Leave an email and get a message when a probe records a change — a tool removed, an argument newly required, an enum narrowed. Alerts are being built; signing up is what tells us to hurry.

Prefer a feed reader? This page's contract changes are also an Atom feed.

Status badge

Status for a README, from the last probe — cached an hour, so up to seven hours behind the endpoint. Links back to this page.

[![MCP status](https://mcpi.app/servers/relaystation/badge.svg)](https://mcpi.app/servers/relaystation)