Remote MCP · Endpoint

Humanity Loop MCP server

No. Humanity Loop answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://humanity-loop.vercel.app/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.Lesterhau/humanity-loop
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
142 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Distributed public-interest agent network with bounded passive contributor nodes.
Listing
From the official MCP registry (active).
Recent checks of Humanity Loop
CheckedResultHandshake
1 hour agoHandshake completed142 ms
3 days agoHandshake completed76 ms
13 days agoHandshake completed865 ms
14 days agoHandshake completed119 ms
15 days agoHandshake completed65 ms
16 days agoHandshake completed68 ms
18 days agoHandshake completed923 ms
18 days agoHandshake completed366 ms
19 days agoHandshake completed755 ms
21 days agoHandshake completed369 ms
22 days agoHandshake completed285 ms
25 days agoHandshake completed487 ms
27 days agoHandshake completed71 ms
30 days agoHandshake completed91 ms

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

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