https://pvu5bumk5ggt.hostc.app/mcpanswers HTTP, not MCP
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | — of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 246 ms, 95th 246 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 404 |
https://rp4uqyzyzee5.hostc.app/mcpanswered, tools listed
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-10-15 |
| Completed sessions | — of the last 7 probes · 100% of the last 30 |
| Handshake latency | median 201 ms, 95th 201 ms |
| Tools listed | 22 |
| Tool contract | aea14a2da6a2 — first reading; nothing to compare it against yet |
| Protocol answered | 2025-06-18 |
| Transport | streamable-http |
https://t39m24jcmmse.hostc.app/mcpanswers HTTP, not MCP
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | — of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 288 ms, 95th 288 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 404 |
https://8prtkj444ihx.hostc.app/mcpno usable response (DNS, TLS, timeout or 5xx)
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 279 ms, 95th 279 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 502 |
https://r5jsim3t2m6v.hostc.app/mcpanswers HTTP, not MCP
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 242 ms, 95th 242 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 404 |
https://5xgaysn2ai6q.hostc.app/mcpanswered, tools listed
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-10-19 |
| Completed sessions | 100% of the last 7 probes · 100% of the last 30 |
| Handshake latency | median 246 ms, 95th 246 ms |
| Tools listed | 22 |
| Tool contract | aee0403d223c — first reading; nothing to compare it against yet |
| Protocol answered | 2025-06-18 |
| Transport | streamable-http |
https://vr7yw42imwgq.hostc.app/mcpanswers HTTP, not MCP
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 195 ms, 95th 195 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 404 |
https://knarxps4aw6g.hostc.app/mcpanswers HTTP, not MCP
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 199 ms, 95th 199 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 404 |
https://r9dt8bvwi8pf.hostc.app/mcpanswers HTTP, not MCP
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 165 ms, 95th 165 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 404 |
https://adqe7gavge4j.hostc.app/mcpanswers HTTP, not MCP
| Last 30 probes | |
|---|---|
| Last seen healthy | not once, in the days we have probed |
| Completed sessions | 0% of the last 7 probes · 0% of the last 30 |
| Handshake latency | median 214 ms, 95th 214 ms |
| Tools listed | — |
| Protocol answered | — |
| Transport | streamable-http |
| Last detail | HTTP 404 |
[](https://referencesource.org/mcp-health/server/sh-surge-unlockbot-onchain-intel/)
The badge shows the most recent probe. It is generated from the same file this page is, updates once a day, and needs no key. This entry publishes 10 endpoints, and the badge reports the best result among them — the question a badge answers is whether a client can reach this project at all, and one dead spare URL is not a reason to call the project down. The per-endpoint verdicts are above, each with its own link.
One HTTP POST carrying a JSON-RPC initialize, and if
that succeeds, a tools/list. Nothing here is a score, a rating or a
judgement about whether the server is any good — only whether an ordinary MCP
client could complete a session with it on the day we asked.
“Needs credentials” is not a fault: it means the endpoint wants
an account, which is a perfectly reasonable thing for it to want.
The tool contract row is a digest of what
tools/list returned — each tool's name, description and input
schema, hashed — so that a rename, a newly-required field or a rewritten
description can be spotted even though none of them breaks the connection. We
keep the digests and nothing else: no tool name, description or schema of
anybody's is stored or republished here, which is also why this can say that a
contract moved and by how much, but not what it now says.
The method and the daily totals · every server we probe, A–Z · feed.json · licence · corrections and removals: [email protected]