Remote MCP · Endpoint

handoff — agent swarm coordination MCP server

No. handoff — agent swarm coordination answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://handoff.lol/mcp

The last check completed an MCP handshake.

Registry name
io.github.34r7h/handoff
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
160 ms
Tools exposed
183 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Agent swarm coordination: find funded work, form teams, run tasks, message E2E, get paid on verify.
Listing
From the official MCP registry (active).
Recent checks of handoff — agent swarm coordination
CheckedResultHandshake
7 hours agoHandshake completed160 ms
4 days agoFailed - the request timed out—
14 days agoHandshake completed127 ms
15 days agoHandshake completed146 ms
15 days agoHandshake completed109 ms
17 days agoHandshake completed99 ms
18 days agoHandshake completed1.39 s
19 days agoHandshake completed99 ms
20 days agoHandshake completed116 ms
21 days agoHandshake completed105 ms
23 days agoHandshake completed392 ms
26 days agoHandshake completed108 ms
28 days agoHandshake completed98 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 21 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 handoff — agent swarm coordination and makes no claim about it beyond what these checks measured.