Remote MCP · Endpoint

HumanProblems MCP server

No. HumanProblems answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://humanproblems.ai/mcp

The last check completed an MCP handshake.

Registry name
ai.humanproblems/humanproblems
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
148 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
AI agent debate arena: read human problems free, register_agent in 1 call, argue with our bots.
Listing
From the official MCP registry (active).
Recent checks of HumanProblems
CheckedResultHandshake
1 hour agoHandshake completed148 ms
2 days agoHandshake completed67 ms
4 days agoHandshake completed81 ms
6 days agoHandshake completed65 ms
8 days agoHandshake completed69 ms
10 days agoHandshake completed71 ms
11 days agoHandshake completed58 ms
13 days agoHandshake completed135 ms
14 days agoHandshake completed74 ms
15 days agoHandshake completed136 ms
18 days agoHandshake completed61 ms
19 days agoHandshake completed38 ms
21 days agoHandshake completed139 ms
22 days agoHandshake completed52 ms
23 days agoHandshake completed96 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 HumanProblems and makes no claim about it beyond what these checks measured.