Remote MCP · Endpoint

cryptofeed402 MCP server

No. cryptofeed402 answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://cryptofeed402.site/mcp

The last check completed an MCP handshake.

Registry name
site.cryptofeed402/feed
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
202 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Hyperliquid perp funding, OI, preflight & news sentiment for agents. Pay per call in USDC (x402).
Listing
From the official MCP registry (active).
Recent checks of cryptofeed402
CheckedResultHandshake
3 hours agoHandshake completed202 ms
9 days agoHandshake completed211 ms
10 days agoHandshake completed220 ms
11 days agoHandshake completed251 ms
12 days agoHandshake completed202 ms
14 days agoHandshake completed213 ms
14 days agoHandshake completed206 ms
15 days agoHandshake completed208 ms
17 days agoHandshake completed203 ms
19 days agoHandshake completed207 ms
21 days agoHandshake completed198 ms
24 days agoHandshake completed205 ms
26 days agoHandshake completed199 ms
28 days agoHandshake completed204 ms

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

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.

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