gateway.pipeworx.io/geoapify/mcp
Last observed:— recorded as OK
Observations
| Observed | Snapshot | Recorded as | Detail | Latency (ms) | Tools | Tool schema fingerprint |
|---|---|---|---|---|---|---|
| REL-SNAP-002 | OK | — | 25 | — | — | |
| REL-SNAP-003 | OK | — | 26 | — | — | |
| REL-SNAP-004 | OK | — | 28 | — | — | |
| REL-SNAP-005 | OK | — | 34 | — | — | |
| REL-SNAP-006 | OK | — | 51 | — | — | |
| REL-SNAP-007 | OK | — | 33 | — | — | |
| REL-SNAP-008 | OK | — | 37 | — | — | |
| REL-SNAP-009 | OK | — | 31 | — | — | |
| REL-SNAP-010 | OK | — | 29 | — | — | |
| REL-SNAP-011 | OK | — | 30 | — | — | |
| REL-SNAP-012 | OK | — | 86 | — | — | |
| REL-SNAP-013 | OK | — | 30 | — | — | |
| REL-SNAP-014 | OK | — | 30 | — | — | |
| REL-SNAP-015 | OK | — | 52 | — | — | |
| REL-SNAP-016 | OK | — | 53 | — | — | |
| REL-SNAP-017 | OK | — | 51 | — | — | |
| REL-SNAP-018 | OK | — | 50 | — | — | |
| REL-SNAP-019 | OK | — | 53 | — | — | |
| REL-SNAP-020 | OK | — | 53 | — | — | |
| REL-SNAP-021 | OK | — | 52 | — | — | |
| REL-SNAP-022 | OK | — | 50 | — | — | |
| REL-SNAP-023 | OK | — | 52 | — | — | |
| REL-SNAP-024 | OK | — | 46 | — | — | |
| REL-SNAP-025 | OK | — | 49 | — | — | |
| REL-SNAP-026 | OK | — | 52 | — | — |
Identity
- Record key
gateway.pipeworx.io/geoapify/mcp— the normalised endpoint observed. See the methodology for the rule.- Transport
- streamable-http
- Registry names (not anchored)
- io.github.pipeworx-io/geoapify 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
- pipeworx-gateway 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.