Remote MCP · Endpoint

Realtap MCP server

No. Realtap answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://realtap.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.CSteenkamp/realtap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
857 ms
Tools exposed
82 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Live Cardano data (token prices, DEX trades, pools, wallets, NFTs, staking, governance). Read-only.
Listing
From the official MCP registry (active).
Recent checks of Realtap
CheckedResultHandshake
44 minutes agoHandshake completed857 ms
3 days agoHandshake completed787 ms
12 days agoHandshake completed799 ms
13 days agoHandshake completed785 ms
14 days agoHandshake completed841 ms
15 days agoHandshake completed784 ms
16 days agoHandshake completed773 ms
17 days agoFailed - the request timed out—
18 days agoFailed - the request timed out—
19 days agoHandshake completed901 ms
22 days agoHandshake completed887 ms
25 days agoHandshake completed761 ms
27 days agoHandshake completed795 ms

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

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 Realtap and makes no claim about it beyond what these checks measured.