Remote MCP · Endpoint

MAD Synapse · Chain MCP server

No. MAD Synapse · Chain answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://agent.maddegen.art/hub/mcp/chain

The last check completed an MCP handshake.

Registry name
art.maddegen.agent/synapse-chain
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
53 ms
Tools exposed
15 tools
Uptime, last 30 days
85.7% from 14 checks
Described by its publisher as
Cross-chain markets: prices, DeFi TVL, yields, stablecoins, gas, order books, perps funding.
Listing
From the official MCP registry (active).
Recent checks of MAD Synapse · Chain
CheckedResultHandshake
34 minutes agoHandshake completed53 ms
8 days agoHandshake completed81 ms
9 days agoFailed - the request timed out—
11 days agoFailed - the request timed out—
12 days agoHandshake completed83 ms
12 days agoHandshake completed106 ms
14 days agoHandshake completed105 ms
14 days agoHandshake completed81 ms
16 days agoHandshake completed71 ms
19 days agoHandshake completed128 ms
21 days agoHandshake completed71 ms
24 days agoHandshake completed80 ms
26 days agoHandshake completed55 ms
28 days agoHandshake completed60 ms

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

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