harvis.dev/api/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-009 | OK | — | 83 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-010 | OK | — | 523 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-011 | OK | — | 78 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-012 | OK | — | 110 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-013 | OK | — | 89 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-014 | OK | — | 128 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-015 | OK | — | 119 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-016 | OK | — | 471 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-017 | OK | — | 250 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-018 | OK | — | 103 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-019 | OK | — | 266 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-020 | OK | — | 103 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-021 | OK | — | 1381 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-022 | OK | — | 321 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-023 | OK | — | 109 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-024 | OK | — | 116 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-025 | OK | — | 253 | 1 | ebbb9149d5cee2e9… | |
| REL-SNAP-026 | OK | — | 118 | 1 | ebbb9149d5cee2e9… |
Identity
- Record key
harvis.dev/api/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- dev.harvis/harvis 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
- harvis.dev 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.