Liquidation radar, execution context and Li.Fi swaps for AI agents. 6 MCP tools; x402 payments.
https://hypernatt.com/mcp/protocolanswered, tools listed
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-10-23 |
| Completed sessions | 100% of the last 7 probes · 100% of the last 30 |
| Handshake latency | median 364 ms, 95th 451 ms |
| Tools listed | 4 |
| Tool contract | 9472078a97a0 — last moved 2026-10-01 (1 changed in place, against 2026-09-30) |
| Protocol answered | 2025-06-18 |
| Transport | streamable-http |
https://hypernatt.com/mcp/sseanswered, tools listed
| Last 30 probes | |
|---|---|
| Last seen healthy | 2026-10-23 |
| Completed sessions | 100% of the last 7 probes · 93.1% of the last 30 |
| Handshake latency | median 1431 ms, 95th 6019 ms |
| Tools listed | 4 |
| Tool contract | 9472078a97a0 — last moved 2026-10-01 (1 changed in place, against 2026-09-30) |
| Protocol answered | 2024-11-05 |
| Transport | sse |
| Last detail | legacy HTTP+SSE transport |
[](https://referencesource.org/mcp-health/server/io-github-dialloube-research-hypernatt-terminal/)
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 2 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]