Remote MCP · Endpoint

CIPHER x402 — Paid Solana & Crypto Tools MCP server

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

DownLast checked 2 hours ago

Server URL

https://cipher-x402-mcp.vercel.app/mcp

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

Registry name
io.github.cryptomotifs/cipher-x402-mcp
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
15 tools
Uptime, last 30 days
29.4% from 17 checks
Described by its publisher as
8 CIPHER tools — Solana scan, breach check, Jito, FRED, Drift, repo health, more. x402-paid on Base.
Website
https://cipher-x402-mcp.vercel.app/
Repository
https://github.com/cryptomotifs/cipher-x402-mcp
Listing
From the official MCP registry (active).
Recent checks of CIPHER x402 — Paid Solana & Crypto Tools
CheckedResultHandshake
2 hours agoFailed - the server returned an HTTP error—
2 days agoFailed - the server returned an HTTP error—
4 days agoFailed - the server returned an HTTP error—
5 days agoHandshake completed871 ms
7 days agoFailed - the server returned an HTTP error—
8 days agoHandshake completed86 ms
9 days agoFailed - the server returned an HTTP error—
12 days agoFailed - the server returned an HTTP error—
13 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed81 ms
18 days agoFailed - the server returned an HTTP error—
19 days agoFailed - the server returned an HTTP error—
20 days agoHandshake completed570 ms
20 days agoFailed - the server returned an HTTP error—
21 days agoHandshake completed104 ms
23 days agoFailed - the server returned an HTTP error—

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

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 CIPHER x402 — Paid Solana & Crypto Tools and makes no claim about it beyond what these checks measured.