Remote MCP · Endpoint

MEKU Human Cloud MCP server

No. MEKU Human Cloud answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://meku.farm/api/public/mcp

The last check completed an MCP handshake.

Registry name
farm.meku/human-cloud
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.38 s
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
AI agents discover human capabilities, request real-world human execution, and track status.
Listing
From the official MCP registry (active).
Recent checks of MEKU Human Cloud
CheckedResultHandshake
17 minutes agoHandshake completed1.38 s
9 days agoHandshake completed1.39 s
9 days agoHandshake completed76 ms
11 days agoHandshake completed1.64 s
12 days agoHandshake completed833 ms
13 days agoHandshake completed1.15 s
14 days agoHandshake completed1.22 s
14 days agoHandshake completed1.45 s
16 days agoHandshake completed1.08 s
19 days agoHandshake completed790 ms
21 days agoCredentials required—
24 days agoCredentials required—
26 days agoCredentials required—
28 days agoCredentials required—

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

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