Remote MCP · Endpoint

HumanFn MCP server

No. HumanFn answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
119 ms
Tools exposed
9 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Qualified human outcomes for AI agents: attorney review of SaaS Terms/Privacy, on-site checks.
Website
https://humanfn.com/agents
Listing
From the official MCP registry (active).
Recent checks of HumanFn
CheckedResultHandshake
1 hour agoHandshake completed119 ms
2 days agoHandshake completed122 ms
5 days agoHandshake completed111 ms
7 days agoHandshake completed101 ms
9 days agoHandshake completed122 ms
11 days agoHandshake completed99 ms
13 days agoHandshake completed103 ms
15 days agoFailed - the server returned an HTTP error—
17 days agoHandshake completed114 ms
19 days agoHandshake completed94 ms
20 days agoHandshake completed92 ms
21 days agoHandshake completed121 ms
23 days agoHandshake completed105 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

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.