mcp.abstraxn.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 175 | 8 | 27f1e995366a9ca4… | |
| REL-SNAP-010 | OK | — | 282 | 8 | 27f1e995366a9ca4… | |
| REL-SNAP-011 | OK | — | 174 | 8 | 27f1e995366a9ca4… | |
| REL-SNAP-012 | OK | — | 134 | 8 | 27f1e995366a9ca4… | |
| REL-SNAP-013 | OK | — | 235 | 8 | 27f1e995366a9ca4… | |
| REL-SNAP-014 | OK | — | 382 | 8 | 27f1e995366a9ca4… | |
| REL-SNAP-015 | OK | — | 441 | 11 | 83cc9b154c18eee1… | |
| REL-SNAP-016 | OK | — | 915 | 11 | 83cc9b154c18eee1… | |
| REL-SNAP-017 | OK | — | 620 | 11 | 83cc9b154c18eee1… | |
| REL-SNAP-018 | OK | — | 623 | 12 | eb4c5f0bb2432a87… | |
| REL-SNAP-019 | OK | — | 657 | 12 | eb4c5f0bb2432a87… | |
| REL-SNAP-020 | OK | — | 813 | 12 | eb4c5f0bb2432a87… | |
| REL-SNAP-021 | OK | — | 608 | 12 | eb4c5f0bb2432a87… | |
| REL-SNAP-022 | OK | — | 505 | 12 | eb4c5f0bb2432a87… | |
| REL-SNAP-023 | OK | — | 815 | 12 | eb4c5f0bb2432a87… | |
| REL-SNAP-024 | OK | — | 676 | 12 | eb4c5f0bb2432a87… | |
| REL-SNAP-025 | OK | — | 823 | 12 | eb4c5f0bb2432a87… | |
| REL-SNAP-026 | OK | — | 857 | 12 | eb4c5f0bb2432a87… |
Tool schema changed 2 times across this history — the fingerprint differs between consecutive observations. A change can occur while the tool count stays identical, which is why the fingerprint is recorded alongside the count.
Identity
- Record key
mcp.abstraxn.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.sandeep-antier/abstraxn 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
- abstraxn-web3-public-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.