asistent-crypto.vercel.app/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-012 | OK | — | 582 | 13 | b3db0ef59dcdd53d… | |
| REL-SNAP-013 | OK | — | 929 | 14 | a54727ba06715a6d… | |
| REL-SNAP-014 | OK | — | 868 | 14 | a54727ba06715a6d… | |
| REL-SNAP-015 | OK | — | 317 | 15 | 5a100df0456e9fac… | |
| REL-SNAP-016 | OK | — | 325 | 17 | 33652e123747abc3… |
Tool schema changed 3 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
asistent-crypto.vercel.app/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.dopionut-jpg/crypto-data-market-analysis 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
- Crypto Data & Market Analysis Agent (CryptoMacro) 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.