Remote MCP · Endpoint

RWA Data MCP Server MCP server

No. RWA Data MCP Server answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://rwa-data-mcp.dave-a-bear.workers.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.daveabear/rwa-data-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
139 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Pay-per-call crypto data for agents: metrics, claims, custom briefs. USDC via x402.
Listing
From the official MCP registry (active).
Recent checks of RWA Data MCP Server
CheckedResultHandshake
7 hours agoHandshake completed139 ms
4 days agoHandshake completed458 ms
14 days agoHandshake completed227 ms
15 days agoHandshake completed220 ms
15 days agoHandshake completed201 ms
17 days agoHandshake completed258 ms
18 days agoHandshake completed236 ms
19 days agoHandshake completed155 ms
20 days agoHandshake completed148 ms
21 days agoHandshake completed179 ms
23 days agoHandshake completed96 ms
26 days agoHandshake completed53 ms
28 days agoHandshake completed169 ms

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

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