Remote MCP · Endpoint

Chain Daddy MCP server

No. Chain Daddy answered an MCP handshake 3 days ago.

UpLast checked 3 days ago

Server URL

https://api.chaindaddy.io/mcp

The last check completed an MCP handshake.

Registry name
io.chaindaddy/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
32 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Search tokens, check registrations, and run a Chain Daddy creator store from your agent.
Listing
From the official MCP registry (active).
Recent checks of Chain Daddy
CheckedResultHandshake
3 days agoHandshake completed32 ms
7 days agoHandshake completed32 ms
16 days agoHandshake completed41 ms
17 days agoHandshake completed93 ms
18 days agoHandshake completed28 ms
19 days agoHandshake completed74 ms
21 days agoHandshake completed34 ms
22 days agoHandshake completed48 ms
22 days agoHandshake completed42 ms
24 days agoHandshake completed29 ms
26 days agoHandshake completed27 ms
29 days agoHandshake completed241 ms

The last 12 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 Chain Daddy and makes no claim about it beyond what these checks measured.