api.mcp.ai/jus
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-021 | OK | — | 276 | — | — | |
| REL-SNAP-022 | OK | — | 251 | — | — | |
| REL-SNAP-023 | OK | — | 252 | — | — | |
| REL-SNAP-024 | OK | — | 272 | — | — | |
| REL-SNAP-025 | OK | — | 320 | — | — | |
| REL-SNAP-026 | OK | — | 242 | — | — |
Identity
- Record key
api.mcp.ai/jus— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.mcp-dir/jus-mcp What the registry said when we swept it, as observed by us — not evidence that the registry was correct, that the name belongs to whoever registered it, or that it still resolves. Not covered by the chain: no inclusion proof reaches this field.
- Name reported by the server
- Jus MCP Self-reported and unverified — never used as identity.
Verifying this record
Each observation above carries a merkle leaf in the published snapshot it belongs to. Verify the chain explains how to walk a leaf to a published root without taking our word for any of it.