compliance.dropwatchhq.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 63 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-003 | OK | — | 59 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-004 | OK | — | 60 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-005 | OK | — | 54 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-006 | OK | — | 114 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-007 | OK | — | 63 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-008 | OK | — | 64 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-009 | OK | — | 64 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-010 | OK | — | 180 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-011 | OK | — | 58 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-012 | OK | — | 353 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-013 | OK | — | 67 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-014 | OK | — | 97 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-015 | OK | — | 90 | 4 | e273c9c4411a7ea5… | |
| REL-SNAP-016 | OK | — | 100 | 4 | e273c9c4411a7ea5… |
Identity
- Record key
compliance.dropwatchhq.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.dropwatchhq/compliance-radar 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
- compliance-radar 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.