api.duoleads.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-056 | OK | — | 51 | 31 | bf37c6a04d3983b6… | |
| REL-SNAP-057 | OK | — | 67 | 33 | c06d6da4c83a9276… | |
| REL-SNAP-058 | AUTH_REQUIRED | http_403 | — | — | — | |
| REL-SNAP-059 | OK | — | 63 | 33 | c06d6da4c83a9276… |
Tool schema changed 1 time 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
api.duoleads.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.duoleads.api/data-utilities 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
- Duo Data Utilities 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.