Is the Relaystation MCP server down?

mcp-registry/ai.relaystation/relaystation · vv1

healthy
Last checked 2026-10-27 15:08 UTC · handshake 254ms

As of 2026-10-27 15:08 UTC, the Relaystation MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
5,024
outages (90d)
0
tools
14

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

Point your MCP client at this streamable-http endpoint: https://api.relaystation.ai/mcp

Agent-readiness: D (67/100)

D (67/100): 0 error(s), 3 warning(s) across 14 tool(s); ~3,179 tokens of tool definitions.
Scores higher than 1% of 15,808 MCP servers Glimind has audited.
Its tool list costs an agent ~3,179 tokens per session — more than 55% of servers.
65 → 67 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions30
Safety hints0
Token cost100
Client compatibility70
Protocol100
Reliability100
Stability100

What to fix (4)

14 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: append_to_baton, ask_operator, balance, call_tool, create_agent_address and 9 more

46 parameter(s) across 12 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: append_to_baton, ask_operator, call_tool, create_agent_address, create_baton and 7 more

4 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.

Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads. How to fix →

Tools: create_agent_address, create_baton, create_contract, create_topup_link

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 7 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 12 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fai.relaystation%2Frelaystation/fixes

create_agent_address 1 change 
{
  "name": "create_agent_address",
  "description": "Mint a new ephemeral Relaystation address for this agent to receive messages from other agents. Returns a unique <local_part>@courier.relaystation.ai address tied to this agent's customer. Free up to the daily mint cap (default 10/day per customer); above-cap mints debit bridge.agent_address.over_cap_price_micros (default $0.001) via Pattern A. purpose_label is informational. ttl_seconds defaults to 24h; addresses past TTL bounce inbound messages. Example: create_agent_address {purpose_label:\"in",
  "inputSchema": {
    "type": "object",
    "properties": {
      "ttl_seconds": {
        "type": "integer",
        "maximum": 2592000,
        "minimum": 60
      },
      "purpose_label": {
        "type": "string",
        "maxLength": 100
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_baton 1 change 
{
  "name": "create_baton",
  "description": "Create a baton — a prepaid storage object. Pick a preset (drop=store a file, pass=share a file, scratchpad=collaborate via append log, checkpoint=a single current document that each write REPLACES, ledger=hash-chained tamper-evident log) and optional tier, or supply a customShape. **To collaborate on a document — human↔human, human↔agent or agent↔agent — use `checkpoint`**: it holds one current state, so every reader sees the same document and a write replaces it rather than piling up entries. `",
  "inputSchema": {
    "type": "object",
    "oneOf": [
      {
        "properties": {
          "tier": {
            "enum": [
              "femto",
              "pico",
              "nano",
              "micro",
              "standard",
              "big",
              "custom"
            ],
            "type": "string"
          },
          "preset": {
            "const": "drop"
          }
        }
      },
      {
        "properties": {
          "tier": {
            "enum": [
              "femto",
              "pico",
              "nano",
              "custom"
            ],
            "type": "string"
          },
          "preset": {
            "const": "pass"
          }
        }
      },
      {
        "properties": {
          "tier": {
            "enum": [
              "pico",
              "nano",
              "micro",
              "standard",
              "big",
              "custom"
            ],
            "type": "string"
          },
          "preset": {
            "const": "scratchpad"
          }
        }
      },
      {
        "properties": {
          "tier": {
            "enum": [
              "nano",
              "micro",
              "standard",
              "big",
              "custom"
            ],
            "type": "string"
          },
          "preset": {
            "const": "checkpoint"
          }
        }
      },
      {
        "properties": {
          "tier": {
            "enum": [
              "femto",
              "pico",
              "nano",
              "micro",
              "standard",
              "big",
              "custom"
            ],
            "type": "string"
          },
          "preset": {
            "const": "ledger"
          }
        }
      }
    ],
    "required": [
      "preset"
    ],
    "properties": {
      "name": {
        "type": "string",
        "maxLength": 200
      },
      "tags": {
        "type": "array",
        "items": {
          "type": "string"
        }
      },
      "tier": {
        "type": "string",
        "description": "Bundle tier — valid tiers depend on preset (drop: femto/pico/nano/micro/standard/big · pass: femto/pico/nano · scratchpad: pico/nano/micro/standard/big · checkpoint: nano/micro/standard/big · ledger: femto/pico/nano/micro/standard/big). Plus 'custom' (with customShape) for any preset."
      },
      "flags": {
        "type": "object",
        "properties": {
          "witness": {
            "type": "boolean"
          },
          "hashChaining": {
            "type": "boolean"
          }
        }
      },
      "preset": {
        "enum": [
          "drop",
          "pass",
          "scratchpad",
          "checkpoint",
          "ledger"
        ],
        "type": "string"
      },
      "content": {
        "type": "string"
      },
      "contentType": {
        "type": "string"
      },
      "customShape": {
        "type": "object",
        "properties": {
          "sizeBytes": {
            "type": "string"
          },
          "readsAllowed": {
            "type": "integer",
            "minimum": 0
          },
          "writesAllowed": {
            "type": "integer",
            "minimum": 0
          },
          "maxEgressBytes": {
            "type": "string"
          },
          "durationSeconds": {
            "type": "string"
          }
        }
      },
      "description": {
        "type": "string",
        "maxLength": 1000
      },
      "contentEncoding": {
        "enum": [
          "utf-8",
          "base64",
          "binary"
        ],
        "type": "string"
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}
create_contract 1 change 
{
  "name": "create_contract",
  "description": "Create a binding-by-goodwill agreement between agents/parties and get back a contractId + termsHash + per-signer read tokens. The contract IS a hash-chained, auto-witnessed record (terms = entry 1, consents append after); it is tamper-evident and permanently verifiable, but it is NOT legally binding, NOT court-enforceable, and involves NO escrow or money movement — enforcement rests on the good faith of the parties. BILLABLE (contracts.create, charge-on-attempt). The system appends a canonical s",
  "inputSchema": {
    "type": "object",
    "required": [
      "terms",
      "requiredSigners"
    ],
    "properties": {
      "terms": {
        "type": "string",
        "maxLength": 900000,
        "minLength": 1
      },
      "arbitration": {
        "type": "boolean"
      },
      "requiredSigners": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "identity",
            "kind"
          ],
          "properties": {
            "kind": {
              "enum": [
                "wallet",
                "account"
              ],
              "type": "string"
            },
            "identity": {
              "type": "string"
            }
          }
        },
        "maxItems": 20,
        "minItems": 1
      },
      "signingWindowSeconds": {
        "type": "integer",
        "maximum": 31536000,
        "minimum": 60
      }
    }
  },
  "annotations": {
    "readOnlyHint": false,
    "destructiveHint": false,
    "idempotentHint": false
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/ai.relaystation/relaystation"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/ai.relaystation/relaystation"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.relaystation%2Frelaystation.svg)](https://glimind.com/server/mcp-registry%2Fai.relaystation%2Frelaystation?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fai.relaystation%2Frelaystation?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.relaystation%2Frelaystation.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fai.relaystation%2Frelaystation.svg
   :target: https://glimind.com/server/mcp-registry%2Fai.relaystation%2Frelaystation?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:1bf8af21d1b9c509…, first seen 2026-10-17, included at leaf 3004 of 79,969. Version history · verify what your client received.

Tools (14)

Compare: most reliable files servers · most reliable communication servers · most reliable finance servers · most reliable other servers · most reliable security servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Relaystation MCP server down right now?

As of 2026-10-27 15:08 UTC, the Relaystation MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Relaystation MCP server provide?

Relaystation MCP server advertises 14 tools, including append_to_baton, ask_operator, balance, call_tool, create_agent_address.

How do I install Relaystation MCP server?

Point your MCP client at this streamable-http endpoint: https://api.relaystation.ai/mcp

Is the Relaystation MCP server safe to connect to an AI agent?

Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Relaystation MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve