Remote MCP · Endpoint

NOT FOR HUMANS MCP server

No. NOT FOR HUMANS answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://mcp.notforhumans.fun/mcp

The last check completed an MCP handshake.

Registry name
io.github.notforhumansfun-rgb/not-for-humans
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
39 ms
Tools exposed
69 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Public NFH knowledge, ownership epochs, versioned learning, Odd Jobs, and unsigned preparation.
Listing
From the official MCP registry (active).
Recent checks of NOT FOR HUMANS
CheckedResultHandshake
1 day agoHandshake completed39 ms
3 days agoHandshake completed39 ms
5 days agoHandshake completed36 ms
7 days agoHandshake completed56 ms
8 days agoHandshake completed41 ms
9 days agoHandshake completed43 ms
12 days agoHandshake completed44 ms
13 days agoHandshake completed49 ms
15 days agoHandshake completed50 ms
16 days agoHandshake completed42 ms
18 days agoHandshake completed39 ms
19 days agoHandshake completed33 ms
20 days agoHandshake completed36 ms
20 days agoHandshake completed41 ms
21 days agoHandshake completed44 ms
22 days agoHandshake completed40 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 NOT FOR HUMANS and makes no claim about it beyond what these checks measured.