Remote MCP · Endpoint

Criptonlabs Agent APIs MCP server

No. Criptonlabs Agent APIs answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.criptonlabs.com/mcp/pro

The last check completed an MCP handshake.

Registry name
com.criptonlabs/agent-apis
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
301 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read-only XRPL and Solana data for agents: fees, slippage, readiness. Free /mcp; x402 /mcp/pro.
Listing
From the official MCP registry (active).
Recent checks of Criptonlabs Agent APIs
CheckedResultHandshake
5 hours agoHandshake completed301 ms
9 days agoHandshake completed653 ms
10 days agoHandshake completed556 ms
11 days agoHandshake completed315 ms
12 days agoHandshake completed284 ms
14 days agoHandshake completed77 ms
14 days agoHandshake completed432 ms
15 days agoHandshake completed654 ms
17 days agoHandshake completed308 ms
19 days agoHandshake completed614 ms
21 days agoHandshake completed289 ms
24 days agoHandshake completed271 ms
26 days agoHandshake completed332 ms
28 days agoHandshake completed349 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 Criptonlabs Agent APIs and makes no claim about it beyond what these checks measured.