Remote MCP · Endpoint

CryptoPulse Data API MCP server

No. CryptoPulse Data API answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://cryptopulse.saascloud.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.saascloud/cryptopulse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
69 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Pay-per-call crypto market intelligence for AI agents. USDC on Base via x402.
Website
https://cryptopulse.saascloud.ai/
Listing
From the official MCP registry (active).
Recent checks of CryptoPulse Data API
CheckedResultHandshake
7 hours agoHandshake completed69 ms
2 days agoHandshake completed158 ms
4 days agoHandshake completed74 ms
5 days agoHandshake completed65 ms
7 days agoHandshake completed95 ms
8 days agoHandshake completed71 ms
9 days agoHandshake completed44 ms
12 days agoHandshake completed84 ms
13 days agoHandshake completed43 ms
15 days agoHandshake completed62 ms
16 days agoHandshake completed37 ms
17 days agoHandshake completed51 ms
19 days agoHandshake completed34 ms
19 days agoHandshake completed39 ms
20 days agoHandshake completed69 ms
21 days agoHandshake completed40 ms
23 days agoHandshake completed53 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 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 CryptoPulse Data API and makes no claim about it beyond what these checks measured.