api.4fetch.com/mcp/v1/fetch
Last observed:— recorded as PROTOCOL_ERROR (fetch_failed)
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-003 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-004 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-005 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-006 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-007 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-008 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-009 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-010 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-011 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-012 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-013 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-014 | TIMEOUT | timeout_exceeded | — | — | — | |
| REL-SNAP-015 | PROTOCOL_ERROR | fetch_failed | — | — | — | |
| REL-SNAP-016 | PROTOCOL_ERROR | fetch_failed | — | — | — |
Identity
- Record key
api.4fetch.com/mcp/v1/fetch— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.amit755/4fetch 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.