Geo Reconcile MCP server

@pipeworx/geo-reconcile

Reconciles Wikidata items against OpenStreetMap features — the join a community mapping effort needs before linking or adding anything. Give a set of Wikidata Q-ids (or a SPARQL selector that picks out an arbitrary class, e.g. "every power station in country X") and an OSM tag filter; get back one of four DISTINCT verdicts per item — matched, ambiguous, unmatched, or error — scored on an existing wikidata= tag, cross-lingual name agreement, and distance. Built generic; Georgian power stations are the first proving case, not the scope.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

resolves each Wikidata item's coordinate (P625) and labels in the requested languages, runs one Overpass bbox search for osm_filter covering every item, and classifies each item:

• reconcilewikidataosm({qids | sparql, osmfilter, languages, radiusm, overpasstimeouts}) —

tag (ground truth) or name agreement + distance.

• matched — a confident link, with the evidence: an existing wikidata=

tagged with the SAME Wikidata item, a data conflict) — ALL returned with scores, never auto-resolved.

• ambiguous — 2+ plausible OSM candidates (or 2+ OSM features already

on Wikidata, carries no coordinate, or the Overpass call failed/timed-out/was capped. Never collapsed into unmatched — a failed lookup is not evidence of absence.

• unmatched — the OSM search completed and nothing plausible was there.
• error — the search did NOT complete for this item: it didn't resolve

Auth

Keyless. All three upstreams (Wikidata API, Wikidata Query Service, OpenStreetMap Overpass API) are free and require no key.

Overpass calls are relayed through Pipeworx's egress proxy when the gateway provides one — overpass-api.de answers 429 then 521 to direct Cloudflare Worker egress while returning 200 to the same request from elsewhere (observed against this same host, fleet #1246; also true of the standalone overpass pack). A standalone (non-gateway) deployment of this pack calls Overpass directly and works from any non-Cloudflare-Worker environment without relay configuration.

The OSM leg goes to overpass.kumi.systems FIRST and falls back to overpass-api.de, because the latter now refuses the relay's egress as well — 406 to every request shape tried, including a bare GET /api/status, while answering 200 to all of them from a residential address (fleet #2036). Until 2026-09-15 this pack had no fallback, so whenever that refusal was in force the reconciliation ran Wikidata-only and reported its OSM leg as error.

Data sources

the P625 coordinate claim for each resolved item.

• (action=wbgetentities) — labels and

to discover the item set when sparql is given instead of qids.

• — runs a caller-supplied SPARQL SELECT

within the bounding box covering every resolved item's coordinate, with as fallback.

• — the OSM feature search

Notes for the next person:

Shortened. The full README is on GitHub.