mcp.agendaforge.app/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-022 | OK | — | 59 | 51 | 3e3cccf186037b89… | |
| REL-SNAP-023 | OK | — | 54 | 53 | 9e94aa0f34dbff9c… | |
| REL-SNAP-024 | OK | — | 97 | 53 | 9e94aa0f34dbff9c… | |
| REL-SNAP-025 | OK | — | 59 | 53 | 9e94aa0f34dbff9c… | |
| REL-SNAP-026 | OK | — | 64 | 55 | 259ebbd7bc9288d3… |
Tool schema changed 2 times across this history — the fingerprint differs between consecutive observations. A change can occur while the tool count stays identical, which is why the fingerprint is recorded alongside the count.
Identity
- Record key
mcp.agendaforge.app/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- app.agendaforge/agendaforge 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
- agendaforge-mcp 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.