Remote MCP · Endpoint

io.github.onrampbtc/proof-of-custody MCP server

No. io.github.onrampbtc/proof-of-custody answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://proofofcustody.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.onrampbtc/proof-of-custody
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
94 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Bitcoin custody scores, failure registry, ETF custody, stablecoin and x402 data, source router.
Listing
From the official MCP registry (active).
Recent checks of io.github.onrampbtc/proof-of-custody
CheckedResultHandshake
5 hours agoHandshake completed94 ms
9 days agoHandshake completed132 ms
10 days agoHandshake completed79 ms
11 days agoHandshake completed151 ms
12 days agoHandshake completed62 ms
14 days agoHandshake completed74 ms
14 days agoHandshake completed137 ms
15 days agoHandshake completed213 ms
17 days agoHandshake completed180 ms
19 days agoHandshake completed81 ms
21 days agoHandshake completed149 ms
24 days agoHandshake completed70 ms
26 days agoHandshake completed75 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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 io.github.onrampbtc/proof-of-custody and makes no claim about it beyond what these checks measured.