Remote MCP · Endpoint

GadgetHumans API Hub MCP server

No. GadgetHumans API Hub answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.gadgethumans.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.scotia1973-bot/gadgethumans-x402
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
122 ms
Tools exposed
229 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
47 MCP tools free (rate-limited) + x402 pay-per-call REST on Base. Flagship: Token Verdict, $0.02.
Listing
From the official MCP registry (active).
Recent checks of GadgetHumans API Hub
CheckedResultHandshake
1 hour agoHandshake completed122 ms
1 day agoHandshake completed36 ms
3 days agoHandshake completed49 ms
3 days agoHandshake completed75 ms
4 days agoHandshake completed76 ms
5 days agoHandshake completed50 ms
7 days agoHandshake completed211 ms
10 days agoHandshake completed118 ms
12 days agoHandshake completed54 ms
15 days agoHandshake completed105 ms
17 days agoHandshake completed115 ms
19 days agoHandshake completed144 ms
21 days agoHandshake completed62 ms
23 days agoHandshake completed130 ms
25 days agoHandshake completed32 ms

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

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 GadgetHumans API Hub and makes no claim about it beyond what these checks measured.