dep-diff.digicatalyst.ca/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-021 | OK | — | 417 | 2 | 0f1d1fac378e150a… | |
| REL-SNAP-022 | OK | — | 226 | 2 | 0f1d1fac378e150a… | |
| REL-SNAP-023 | OK | — | 199 | 2 | 0f1d1fac378e150a… | |
| REL-SNAP-024 | OK | — | 220 | 2 | 0f1d1fac378e150a… | |
| REL-SNAP-025 | OK | — | 258 | 2 | 0f1d1fac378e150a… | |
| REL-SNAP-026 | OK | — | 253 | 2 | 0f1d1fac378e150a… |
Identity
- Record key
dep-diff.digicatalyst.ca/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.DigiCatalyst-Systems/dep-diff-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
- dep-diff 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.