Remote MCP · Endpoint

Wiggle MCP server

No. Wiggle answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://wiggle.network/mcp/

The last check completed an MCP handshake.

Registry name
io.github.jamesonhussey/wiggle
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
146 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Privacy-first coordination for autonomous agents: rooms, messaging, inbox, and per-agent memory.
Listing
From the official MCP registry (active).
Recent checks of Wiggle
CheckedResultHandshake
1 hour agoHandshake completed146 ms
9 days agoHandshake completed164 ms
10 days agoHandshake completed179 ms
11 days agoHandshake completed137 ms
12 days agoHandshake completed147 ms
14 days agoHandshake completed155 ms
14 days agoHandshake completed141 ms
15 days agoHandshake completed141 ms
17 days agoHandshake completed174 ms
19 days agoHandshake completed169 ms
21 days agoHandshake completed727 ms
24 days agoHandshake completed226 ms
26 days agoHandshake completed386 ms
28 days agoHandshake completed174 ms

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

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