www.rafsoft.net/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-004 | OK | — | 759 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-005 | OK | — | 758 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-006 | OK | — | 774 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-007 | OK | — | 826 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-008 | OK | — | 1487 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-009 | OK | — | 775 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-010 | OK | — | 796 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-011 | OK | — | 764 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-012 | OK | — | 949 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-013 | OK | — | 789 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-014 | OK | — | 789 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-015 | OK | — | 224 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-016 | OK | — | 158 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-017 | OK | — | 151 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-018 | OK | — | 158 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-019 | OK | — | 136 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-020 | OK | — | 146 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-021 | OK | — | 243 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-022 | OK | — | 90 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-023 | OK | — | 162 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-024 | OK | — | 131 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-025 | OK | — | 88 | 5 | 5bb31e71e07966db… | |
| REL-SNAP-026 | OK | — | 135 | 5 | 5bb31e71e07966db… |
Identity
- Record key
www.rafsoft.net/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- net.rafsoft/faktura-vat 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
- rafsoft-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.