Remote MCP · Endpoint

chainpulse — real-time crypto + prediction market data for AI agents MCP server

No. chainpulse — real-time crypto + prediction market data for AI agents answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://md.fastdb.in/pulse/mcp

The last check completed an MCP handshake.

Registry name
in.fastdb.md/chainpulse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
314 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Crypto prices, gas, DeFi TVL, and live Polymarket odds. x402 pay-per-call, $0.001, no API key.
Listing
From the official MCP registry (active).
Recent checks of chainpulse — real-time crypto + prediction market data for AI agents
CheckedResultHandshake
1 hour agoHandshake completed314 ms
11 hours agoHandshake completed439 ms
1 day agoHandshake completed292 ms
2 days agoHandshake completed294 ms
4 days agoHandshake completed293 ms
4 days agoHandshake completed308 ms
5 days agoHandshake completed305 ms
6 days agoHandshake completed300 ms
8 days agoHandshake completed300 ms
11 days agoHandshake completed290 ms
13 days agoHandshake completed302 ms
16 days agoHandshake completed293 ms
18 days agoHandshake completed318 ms
20 days agoHandshake completed304 ms
22 days agoHandshake completed315 ms
24 days agoHandshake completed297 ms
26 days agoHandshake completed365 ms
27 days agoHandshake completed310 ms
29 days agoHandshake completed305 ms

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

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 chainpulse — real-time crypto + prediction market data for AI agents and makes no claim about it beyond what these checks measured.