Remote MCP · Endpoint

ai.firmbrain/x402-services MCP server

Yes, as of 2 hours ago: the server returned an HTTP error.

DownLast checked 2 hours ago

Server URL

https://x402-services-production.up.railway.app/mcp

The last check failed: the server returned an HTTP error.

Registry name
ai.firmbrain/x402-services
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
159 tools
Uptime, last 30 days
55.6% from 18 checks
Described by its publisher as
The only x402 MCP server for Robinhood Chain (chainId 4663) - 147 onchain, trading & AI tools.
Repository
https://github.com/bkrigmo1/robinhood-chain-x402
Listing
From the official MCP registry (active).
Recent checks of ai.firmbrain/x402-services
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
1 day agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
3 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoFailed - the server returned an HTTP error—
7 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed103 ms
14 days agoHandshake completed94 ms
17 days agoHandshake completed116 ms
19 days agoHandshake completed240 ms
21 days agoHandshake completed103 ms
23 days agoHandshake completed117 ms
25 days agoHandshake completed94 ms
26 days agoHandshake completed116 ms
28 days agoHandshake completed93 ms
29 days agoHandshake completed92 ms

The last 18 checks. Full history is kept for 30 days; the all-time counter stands at 21 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 ai.firmbrain/x402-services and makes no claim about it beyond what these checks measured.