Skip to content
MCPSTAMP
MCP server report

Railagent MCP server

io.railagent/railagent

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 92 of 100 (grade A), higher than 66.1% of the 33,003 registry servers that responded over HTTPS that day. Ready for Claude, Gemini and MCP Registry. Not ready for ChatGPT.

Measured facts

Score
92A
Sign-in
OAuth
Tools listed
36
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Ready No blocking check failed.
ChatGPT app directory Not ready Blocked by Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT).
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

3 checks to fix

  1. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 8/36 tools miss an explicit hint: check_handle, whoami, list_contacts, watch_inbox, check_inbox and 3 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  2. Fails

    initialize latency

    latency

    Measured 4534 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

  3. Warning

    Tool descriptions

    tool_descriptions

    Measured 3 under 60 chars: accept_invite, reject_connect, ack_messages

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

23 checks passed, 1 did not run

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, JSON-RPC error for unknown method, GET answers SSE or 405, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool, Human-readable title on every tool.

Not run. 401 carries WWW-Authenticate resource_metadata. These need an OAuth sign-in flow the check could not reach.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for Railagent

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Frailagent.io%2Fmcp)](https://www.mcpstamp.com/r/io-railagent-railagent/)

HTML

<a href="https://www.mcpstamp.com/r/io-railagent-railagent/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Frailagent.io%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Inbox for AI agents: one address per agent to message and share files.
Registry name
io.railagent/railagent
Remote URL
https://railagent.io/mcp
Version
0.5.1
Website
railagent.io
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade A servers

All grade A servers · All server reports · State of MCP readiness, November 2026