Remote MCP · Endpoint

HumanFn MCP server

No. HumanFn answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://humanfn.com/mcp

The last check completed an MCP handshake.

Registry name
com.humanfn/humanfn
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
103 ms
Tools exposed
9 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
Qualified human outcomes for AI agents: attorney review of SaaS Terms/Privacy, on-site checks.
Listing
From the official MCP registry (active).
Recent checks of HumanFn
CheckedResultHandshake
7 hours agoHandshake completed103 ms
4 days agoHandshake completed109 ms
14 days agoFailed - the server returned an HTTP error—
15 days agoFailed - the server returned an HTTP error—
15 days agoHandshake completed103 ms
17 days agoHandshake completed94 ms
18 days agoHandshake completed104 ms
19 days agoHandshake completed103 ms
20 days agoHandshake completed113 ms
21 days agoHandshake completed130 ms
23 days agoHandshake completed119 ms
26 days agoHandshake completed122 ms
28 days agoHandshake completed111 ms

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