viraloutliers.com/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 790 | 21 | 411cbdbb4ab8c508… | |
| REL-SNAP-010 | OK | — | 818 | 21 | 411cbdbb4ab8c508… | |
| REL-SNAP-011 | OK | — | 820 | 21 | 411cbdbb4ab8c508… | |
| REL-SNAP-012 | OK | — | 1000 | 21 | 411cbdbb4ab8c508… | |
| REL-SNAP-013 | OK | — | 744 | 21 | 411cbdbb4ab8c508… | |
| REL-SNAP-014 | OK | — | 437 | 21 | 411cbdbb4ab8c508… | |
| REL-SNAP-015 | OK | — | 738 | 22 | 3057c71dd785202e… | |
| REL-SNAP-016 | OK | — | 733 | 22 | 3057c71dd785202e… | |
| REL-SNAP-017 | OK | — | 748 | 22 | 3057c71dd785202e… | |
| REL-SNAP-018 | OK | — | 706 | 22 | 3057c71dd785202e… | |
| REL-SNAP-019 | OK | — | 1056 | 22 | 3057c71dd785202e… | |
| REL-SNAP-020 | OK | — | 1053 | 22 | 3057c71dd785202e… | |
| REL-SNAP-021 | OK | — | 722 | 22 | 3057c71dd785202e… | |
| REL-SNAP-022 | OK | — | 744 | 22 | 3057c71dd785202e… | |
| REL-SNAP-023 | OK | — | 1198 | 23 | f5986d281c13fac4… | |
| REL-SNAP-024 | OK | — | 745 | 23 | f5986d281c13fac4… | |
| REL-SNAP-025 | OK | — | 1116 | 23 | f5986d281c13fac4… | |
| REL-SNAP-026 | OK | — | 735 | 23 | f5986d281c13fac4… |
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
viraloutliers.com/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.viraloutliers/viral-outliers 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
- viral-outliers 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.