Remote MCP · Endpoint

HumanEndpoint MCP server

No. HumanEndpoint answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://humanendpoint.au/mcp

The last check completed an MCP handshake.

Registry name
au.humanendpoint/humanendpoint
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
507 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Human-only capabilities for AI agents: ground truth, verification, judgement and real-world action.
Listing
From the official MCP registry (active).
Recent checks of HumanEndpoint
CheckedResultHandshake
1 hour agoHandshake completed507 ms
2 days agoHandshake completed407 ms
5 days agoHandshake completed1.22 s
7 days agoHandshake completed1.21 s
9 days agoHandshake completed603 ms
11 days agoHandshake completed909 ms
13 days agoHandshake completed445 ms
15 days agoHandshake completed429 ms
17 days agoHandshake completed946 ms
19 days agoHandshake completed509 ms
20 days agoHandshake completed907 ms
21 days agoHandshake completed294 ms
23 days agoHandshake completed288 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 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.

Listing data comes from the official MCP registry. Glide is not affiliated with HumanEndpoint and makes no claim about it beyond what these checks measured.