permitreporter.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-008 | OK | — | 571 | 8 | d8232359e86b6cfb… | |
| REL-SNAP-009 | OK | — | 562 | 8 | d8232359e86b6cfb… | |
| REL-SNAP-010 | OK | — | 606 | 8 | d8232359e86b6cfb… | |
| REL-SNAP-011 | OK | — | 564 | 8 | d8232359e86b6cfb… | |
| REL-SNAP-012 | OK | — | 872 | 8 | d8232359e86b6cfb… | |
| REL-SNAP-013 | OK | — | 579 | 8 | 639ae09bfad49610… | |
| REL-SNAP-014 | HTTP_5XX | http_530 | — | — | — | |
| REL-SNAP-015 | OK | — | 553 | 8 | 489775f34f516833… | |
| REL-SNAP-016 | OK | — | 555 | 8 | 489775f34f516833… | |
| REL-SNAP-017 | OK | — | 277 | 8 | 489775f34f516833… | |
| REL-SNAP-018 | OK | — | 327 | 8 | 489775f34f516833… | |
| REL-SNAP-019 | OK | — | 270 | 8 | 489775f34f516833… | |
| REL-SNAP-020 | OK | — | 355 | 8 | 489775f34f516833… | |
| REL-SNAP-021 | OK | — | 469 | 8 | 489775f34f516833… | |
| REL-SNAP-022 | OK | — | 493 | 8 | 489775f34f516833… | |
| REL-SNAP-023 | OK | — | 314 | 8 | 489775f34f516833… | |
| REL-SNAP-024 | OK | — | 467 | 8 | 489775f34f516833… | |
| REL-SNAP-025 | OK | — | 258 | 8 | 489775f34f516833… | |
| REL-SNAP-026 | OK | — | 446 | 8 | 489775f34f516833… |
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
permitreporter.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.permitreporter/georgia-permits 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
- permitreporter-georgia-permits 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.