mcp.ainsof.io
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-004 | OK | — | 361 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-005 | OK | — | 403 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-006 | OK | — | 389 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-007 | OK | — | 490 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-008 | OK | — | 494 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-009 | OK | — | 433 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-010 | OK | — | 766 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-011 | OK | — | 437 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-012 | OK | — | 719 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-013 | OK | — | 465 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-014 | OK | — | 485 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-015 | OK | — | 302 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-016 | OK | — | 367 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-017 | OK | — | 339 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-018 | OK | — | 510 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-019 | OK | — | 299 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-020 | OK | — | 307 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-021 | OK | — | 340 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-022 | OK | — | 331 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-023 | OK | — | 330 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-024 | OK | — | 321 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-025 | OK | — | 319 | 12 | a3d5a3418dd690ac… | |
| REL-SNAP-026 | OK | — | 381 | 12 | a3d5a3418dd690ac… |
Identity
- Record key
mcp.ainsof.io— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.ainsof/mcp 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
- AINSOF 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.