1f3d9.com/mcp/connect
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-043 | OK | — | 292 | 40 | 720a99e0a8c38bf9… | |
| REL-SNAP-044 | OK | — | 350 | 40 | 78833ec9ef22a7f5… | |
| REL-SNAP-045 | OK | — | 348 | 40 | 78833ec9ef22a7f5… | |
| REL-SNAP-046 | OK | — | 327 | 40 | 78833ec9ef22a7f5… | |
| REL-SNAP-047 | OK | — | 306 | 40 | a7c4545ef5cf8ce8… | |
| REL-SNAP-048 | OK | — | 253 | 40 | ae82c3325d55b64d… | |
| REL-SNAP-049 | OK | — | 306 | 40 | ae82c3325d55b64d… | |
| REL-SNAP-050 | OK | — | 275 | 41 | 4dc881c4787cc271… | |
| REL-SNAP-051 | OK | — | 403 | 41 | f900373bbdd6cf8a… | |
| REL-SNAP-052 | OK | — | 370 | 43 | 1166182e8eaa6a16… | |
| REL-SNAP-053 | OK | — | 271 | 43 | 3262b78a0dc621c5… | |
| REL-SNAP-054 | OK | — | 372 | 43 | 3262b78a0dc621c5… | |
| REL-SNAP-055 | OK | — | 370 | 43 | 7eed61a8c83aed08… | |
| REL-SNAP-056 | OK | — | 308 | 43 | 7eed61a8c83aed08… | |
| REL-SNAP-057 | OK | — | 387 | 43 | 7eed61a8c83aed08… | |
| REL-SNAP-058 | OK | — | 317 | 43 | 7eed61a8c83aed08… | |
| REL-SNAP-059 | OK | — | 403 | 43 | 7eed61a8c83aed08… |
Tool schema changed 8 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
1f3d9.com/mcp/connect— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.onetapstudiogames/1f3d9 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
- 1f3d9 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.