mcp.scienceswarm.org/mcp
Last observed:— recorded as HTTP_5XX (http_530)
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 1039 | — | — | |
| REL-SNAP-003 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-004 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-005 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-006 | OK | — | 556 | — | — | |
| REL-SNAP-007 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-008 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-009 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-010 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-011 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-012 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-013 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-014 | OK | — | 835 | — | — | |
| REL-SNAP-015 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-016 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-017 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-018 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-019 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-020 | OK | — | 714 | — | — | |
| REL-SNAP-021 | OK | — | 979 | — | — | |
| REL-SNAP-022 | OK | — | 1031 | — | — | |
| REL-SNAP-023 | OK | — | 1015 | — | — | |
| REL-SNAP-024 | OK | — | 976 | — | — | |
| REL-SNAP-025 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-026 | HTTP_5XX | http_530 | — | — | — |
Identity
- Record key
mcp.scienceswarm.org/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- org.scienceswarm/commerce-validators 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
- Not reported. 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.