mcp.frogeye.ai/sse
Last observed:— recorded as HTTP_5XX (http_500)
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 766 | 7 | 9155bb677fe277f8… | |
| REL-SNAP-003 | OK | — | 791 | 7 | 9155bb677fe277f8… | |
| REL-SNAP-004 | OK | — | 765 | 7 | 9155bb677fe277f8… | |
| REL-SNAP-005 | OK | — | 997 | — | — | |
| REL-SNAP-006 | OK | — | 923 | — | — | |
| REL-SNAP-007 | OK | — | 1241 | — | — | |
| REL-SNAP-008 | OK | — | 788 | 7 | 9155bb677fe277f8… | |
| REL-SNAP-009 | OK | — | 965 | — | — | |
| REL-SNAP-010 | OK | — | 807 | 7 | 9155bb677fe277f8… | |
| REL-SNAP-011 | OK | — | 906 | — | — | |
| REL-SNAP-012 | OK | — | 824 | 7 | 9155bb677fe277f8… | |
| REL-SNAP-013 | OK | — | 1003 | — | — | |
| REL-SNAP-014 | OK | — | 980 | — | — | |
| REL-SNAP-015 | OK | — | 478 | 7 | 9155bb677fe277f8… | |
| REL-SNAP-016 | OK | — | 460 | 7 | 9155bb677fe277f8… | |
| REL-SNAP-017 | OK | — | 580 | — | — | |
| REL-SNAP-018 | HTTP_5XX | http_500 | — | — | — | |
| REL-SNAP-019 | HTTP_5XX | http_500 | — | — | — | |
| REL-SNAP-020 | HTTP_5XX | http_500 | — | — | — | |
| REL-SNAP-021 | HTTP_5XX | http_500 | — | — | — | |
| REL-SNAP-022 | HTTP_5XX | http_500 | — | — | — | |
| REL-SNAP-023 | HTTP_5XX | http_500 | — | — | — | |
| REL-SNAP-024 | HTTP_5XX | http_500 | — | — | — | |
| REL-SNAP-025 | HTTP_5XX | http_500 | — | — | — | |
| REL-SNAP-026 | HTTP_5XX | http_500 | — | — | — |
Identity
- Record key
mcp.frogeye.ai/sse— the normalised endpoint observed. See the methodology for the rule.- Transport
- sse
- Registry names (not anchored)
- io.github.frogeye-ai/mcp 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.