crypto.api.trendsapi.ai/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 606 | — | — | |
| REL-SNAP-003 | OK | — | 534 | — | — | |
| REL-SNAP-004 | OK | — | 586 | — | — | |
| REL-SNAP-005 | OK | — | 548 | — | — | |
| REL-SNAP-006 | OK | — | 655 | — | — | |
| REL-SNAP-007 | OK | — | 562 | — | — | |
| REL-SNAP-008 | OK | — | 635 | — | — | |
| REL-SNAP-009 | OK | — | 633 | — | — | |
| REL-SNAP-010 | OK | — | 573 | — | — | |
| REL-SNAP-011 | OK | — | 632 | — | — | |
| REL-SNAP-012 | OK | — | 633 | — | — | |
| REL-SNAP-013 | OK | — | 625 | — | — | |
| REL-SNAP-014 | OK | — | 645 | — | — | |
| REL-SNAP-015 | OK | — | 347 | — | — | |
| REL-SNAP-016 | OK | — | 313 | — | — | |
| REL-SNAP-017 | OK | — | 316 | — | — | |
| REL-SNAP-018 | OK | — | 307 | — | — | |
| REL-SNAP-019 | OK | — | 295 | — | — | |
| REL-SNAP-020 | OK | — | 293 | — | — | |
| REL-SNAP-021 | OK | — | 311 | — | — | |
| REL-SNAP-022 | OK | — | 361 | — | — | |
| REL-SNAP-023 | OK | — | 301 | — | — | |
| REL-SNAP-024 | OK | — | 325 | — | — | |
| REL-SNAP-025 | OK | — | 338 | 3 | 6d51c77745988fd9… | |
| REL-SNAP-026 | OK | — | 318 | 3 | 1f7d95ec7786a3c2… |
Tool schema changed 1 time 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
crypto.api.trendsapi.ai/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- ai.trendsapi/crypto 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
- paradox-intelligence-trends-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.