api.gisfinder.com/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-054 | OK | — | 248 | 7 | 5ce3826cc16f3f64… | |
| REL-SNAP-055 | OK | — | 244 | 7 | 5ce3826cc16f3f64… | |
| REL-SNAP-056 | OK | — | 232 | 8 | 3a045da643d966cd… | |
| REL-SNAP-057 | OK | — | 621 | 8 | 3a045da643d966cd… | |
| REL-SNAP-058 | OK | — | 232 | 8 | 3a045da643d966cd… | |
| REL-SNAP-059 | OK | — | 235 | 8 | 3a045da643d966cd… |
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.gisfinder.com/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- com.gisfinder/directory 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
- gisfinder 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.