Remote MCP · Endpoint

MAD Synapse MCP server

No. MAD Synapse answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
art.maddegen.agent/synapse
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
54 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Solana + pump.fun intel for agents: launch verdicts, token risk, dev/wallet records, smart money.
Listing
From the official MCP registry (active).
Recent checks of MAD Synapse
CheckedResultHandshake
2 hours agoHandshake completed54 ms
2 days agoHandshake completed61 ms
4 days agoHandshake completed59 ms
6 days agoHandshake completed24 ms
7 days agoHandshake completed24 ms
9 days agoHandshake completed27 ms
10 days agoHandshake completed19 ms
11 days agoHandshake completed22 ms
14 days agoHandshake completed16 ms
16 days agoHandshake completed26 ms
17 days agoHandshake completed65 ms
19 days agoHandshake completed74 ms
20 days agoHandshake completed52 ms
21 days agoHandshake completed60 ms
22 days agoHandshake completed78 ms
22 days agoHandshake completed170 ms

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

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