soren.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-004 | OK | — | 103 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-005 | OK | — | 69 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-006 | OK | — | 137 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-007 | OK | — | 114 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-008 | OK | — | 109 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-009 | OK | — | 81 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-010 | OK | — | 248 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-011 | OK | — | 64 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-012 | OK | — | 98 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-013 | OK | — | 100 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-014 | OK | — | 73 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-015 | OK | — | 92 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-016 | OK | — | 99 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-017 | OK | — | 101 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-018 | OK | — | 86 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-019 | OK | — | 87 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-020 | OK | — | 104 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-021 | OK | — | 88 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-022 | OK | — | 103 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-023 | OK | — | 130 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-024 | OK | — | 126 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-025 | OK | — | 83 | 6 | 3d79b1029b7d8ac0… | |
| REL-SNAP-026 | OK | — | 84 | 6 | 3d79b1029b7d8ac0… |
Identity
- Record key
soren.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.soren/games 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
- soren 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.