Remote MCP · Endpoint

MAD Synapse · Utils MCP server

No. MAD Synapse · Utils answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

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

The last check completed an MCP handshake.

Registry name
art.maddegen.agent/synapse-util
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
76 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Exact local utils: QR, hashing/encoding, JSON Schema, cron, markdown, diff, units, JWT, random.
Listing
From the official MCP registry (active).
Recent checks of MAD Synapse · Utils
CheckedResultHandshake
4 hours agoHandshake completed76 ms
2 days agoHandshake completed70 ms
4 days agoHandshake completed61 ms
6 days agoHandshake completed58 ms
8 days agoHandshake completed246 ms
10 days agoHandshake completed79 ms
12 days agoHandshake completed54 ms
13 days agoHandshake completed87 ms
14 days agoHandshake completed59 ms
15 days agoHandshake completed66 ms
18 days agoHandshake completed54 ms
20 days agoHandshake completed56 ms
21 days agoHandshake completed21 ms
23 days agoHandshake completed22 ms

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

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