api.epivo.ai/api/v1/public/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-037 | OK | — | 508 | — | — | |
| REL-SNAP-038 | OK | — | 463 | — | — | |
| REL-SNAP-039 | OK | — | 756 | — | — | |
| REL-SNAP-040 | OK | — | 708 | — | — | |
| REL-SNAP-041 | OK | — | 554 | 3 | 578db092e2d79db0… | |
| REL-SNAP-042 | OK | — | 512 | 3 | 578db092e2d79db0… | |
| REL-SNAP-043 | OK | — | 631 | — | — | |
| REL-SNAP-044 | OK | — | 651 | 3 | 578db092e2d79db0… | |
| REL-SNAP-045 | OK | — | 871 | — | — | |
| REL-SNAP-046 | OK | — | 611 | 3 | 578db092e2d79db0… | |
| REL-SNAP-047 | OK | — | 879 | 3 | 578db092e2d79db0… | |
| REL-SNAP-048 | OK | — | 482 | 3 | 578db092e2d79db0… | |
| REL-SNAP-049 | OK | — | 486 | 3 | 578db092e2d79db0… | |
| REL-SNAP-050 | OK | — | 501 | 3 | 578db092e2d79db0… | |
| REL-SNAP-051 | OK | — | 528 | 3 | 578db092e2d79db0… | |
| REL-SNAP-052 | OK | — | 630 | 3 | 578db092e2d79db0… | |
| REL-SNAP-053 | OK | — | 651 | 3 | 578db092e2d79db0… | |
| REL-SNAP-054 | OK | — | 762 | 3 | 578db092e2d79db0… | |
| REL-SNAP-055 | OK | — | 685 | 3 | 578db092e2d79db0… | |
| REL-SNAP-056 | OK | — | 855 | 3 | 578db092e2d79db0… | |
| REL-SNAP-057 | OK | — | 472 | 3 | 578db092e2d79db0… | |
| REL-SNAP-058 | OK | — | 474 | 3 | 578db092e2d79db0… | |
| REL-SNAP-059 | OK | — | 673 | 3 | 578db092e2d79db0… |
Identity
- Record key
api.epivo.ai/api/v1/public/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.henrikthome-arch/epivo-catalog 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
- epivo-catalog 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.