Geo Reconcile
NPM · @PIPEWORX/MCP-GEO-RECONCILE · 2 COMPONENTS
Wikidata <-> OpenStreetMap reconciliation.
Available components
Last scanned (2 hours ago)
Scores higher than 65% of npm servers
Category Maps and Location
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-geo-reconcile). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability50
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 831 tokens (~831/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −13
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.13 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 76
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-geo-reconcile@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-geo-reconcile |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-geo-reconcile/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637322732 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:94911f830fcaafdd5b4f93e45eb856d662e413dec7532a0b3c99054273a737a73581031a67f9232e83391c74f72c8c66888538a70ff42991495906c47 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
reconcile_wikidata_osm ~776
Reconcile a set of Wikidata items against OpenStreetMap features of a given tag — the join Wikidata<->OSM community mapping efforts need before editing anything. Give either explicit Q-ids ("qids") or a SPARQL query that selects them ("sparql", must bind ?item to a wd:Q... URI — used to discover an arbitrary class, e.g. "every power station in country X"), plus an OSM tag filter ("osm_filter", e.g. "power=plant"). Fetches each item's coordinate (P625) and labels in the requested languages, searches OSM within radius_m of each, and scores candidates on THREE signals: an existing `wikidata=` tag (ground truth when present), cross-lingual name agreement, and distance. Returns one of four DISTINCT states per item: "matched" (confident link + evidence), "ambiguous" (2+ plausible candidates, ALL returned with scores — never auto-resolved), "unmatched" (the OSM search completed and found nothing plausible), or "error" (the search did NOT complete — no Wikidata coordinate, the item didn't resolve, or the Overpass call failed/timed out/was capped). "error" is never collapsed into "unmatched": a failed lookup is not evidence a thing is missing from OSM. Read-only — this does not write to Wikidata, Wikipedia or OpenStreetMap.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | string | – | Comma/pipe-joined language codes to compare, e.g. "ka,ru,en" — the shape needed when the same real-world place has different names in different languages (his own example: a Georgian power station na… |
| osm_filter | string | yes | OSM tag filter(s) candidates must carry, as key=value, e.g. "power=plant" — or several alternatives comma-joined, e.g. "power=plant,power=generator" (OR-ed together). Required. |
| overpass_timeout_s | number | – | Timeout passed to the Overpass query itself, 5-180 seconds (default 25). Lower it to fail fast over a large area rather than wait. |
| qids | – | – | Wikidata Q-ids to reconcile, up to 200 — an array of strings or a comma/pipe-joined string (e.g. ["Q162887","Q3650523"] or "Q162887,Q3650523"). Provide this OR "sparql". |
| radius_m | number | – | Search radius in metres around each item's coordinate, 10-20000 (default 300). An OSM feature carrying a matching wikidata= tag is still recognised as "matched" even if it falls outside this radius —… |
| sparql | string | – | A SPARQL SELECT that binds ?item to the Wikidata items to reconcile (up to 200 used) — e.g. "SELECT ?item WHERE { ?item wdt:P31/wdt:P279* wd:Q159719 . ?item wdt:P17 wd:Q230 . }" for every power stati… |
No output schema declared.
No examples provided.
How do I install the Geo Reconcile MCP server?
Geo Reconcile runs locally as an npm package, launched with npx -y @pipeworx/mcp-geo-reconcile. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-geo-reconcile
claude mcp add pipeworx-io-geo-reconcile -- npx -y @pipeworx/mcp-geo-reconcile
What is the Geo Reconcile MCP server?
Geo Reconcile is an MCP server listed in the public MCP registry as io.github.pipeworx-io/geo-reconcile. Wikidata <-> OpenStreetMap reconciliation. This page covers its npm package (@pipeworx/mcp-geo-reconcile).
Is the Geo Reconcile MCP server safe to use?
Geo Reconcile scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Geo Reconcile MCP server expose?
Geo Reconcile exposes 1 tool: reconcile_wikidata_osm. Their descriptions and schemas cost roughly 776 tokens of context every time the server is loaded.
Is the Geo Reconcile MCP server still maintained?
Geo Reconcile is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Geo Reconcile MCP server under?
Geo Reconcile declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.