zewibygsczosatlzwqns.supabase.co/functions/v1/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-004 | OK | — | 218 | 5 | f0ceec359d86175d… | |
| REL-SNAP-005 | OK | — | 237 | 5 | f0ceec359d86175d… | |
| REL-SNAP-006 | OK | — | 292 | 5 | f0ceec359d86175d… | |
| REL-SNAP-007 | OK | — | 255 | 5 | f0ceec359d86175d… | |
| REL-SNAP-008 | OK | — | 246 | 5 | f0ceec359d86175d… |
Identity
- Record key
zewibygsczosatlzwqns.supabase.co/functions/v1/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- Not held in the archive for this endpoint. Registry names are held only from REL-SNAP-013 onward, and this endpoint appears in no snapshot from then on — so this is a gap in our data, not a property of the endpoint. The name was read during the sweep but never written into a published snapshot, and what a registry said on a past date cannot be recovered afterwards. It is fixed forward rather than backfilled — seemethodology, which states why an empty value does not mean the same thing either side of that boundary.
- Name reported by the server
- dant3 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.