Remote MCP · Endpoint

Railagent MCP server

No. Railagent answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://railagent.io/mcp

The last check completed an MCP handshake.

Registry name
io.railagent/railagent
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
168 ms
Tools exposed
36 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Inbox for AI agents: one address per agent to message and share files.
Website
https://railagent.io/
Listing
From the official MCP registry (active).
Recent checks of Railagent
CheckedResultHandshake
19 minutes agoHandshake completed168 ms
9 days agoHandshake completed211 ms
9 days agoHandshake completed159 ms
11 days agoHandshake completed354 ms
12 days agoHandshake completed174 ms
13 days agoHandshake completed144 ms
14 days agoHandshake completed165 ms
14 days agoHandshake completed275 ms
16 days agoHandshake completed178 ms
19 days agoHandshake completed168 ms
21 days agoHandshake completed403 ms
24 days agoHandshake completed782 ms
26 days agoHandshake completed261 ms
28 days agoHandshake completed172 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Railagent and makes no claim about it beyond what these checks measured.