# Geo Reconcile (npm · @pipeworx/mcp-geo-reconcile)

Wikidata <-> OpenStreetMap reconciliation.

- Trust score: 80/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 71/100, [markdown](https://verifymcp.io/servers/pipeworx-io-geo-reconcile/geo-reconcile-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-geo-reconcile/geo-reconcile-mcp)
- npm · `@pipeworx/mcp-geo-reconcile`: 80/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-geo-reconcile/pipeworx-mcp-geo-reconcile.md), [page](https://verifymcp.io/servers/pipeworx-io-geo-reconcile/pipeworx-mcp-geo-reconcile)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-geo-reconcile`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-geo-reconcile).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 50/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-geo-reconcile -- npx -y @pipeworx/mcp-geo-reconcile
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-geo-reconcile": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-geo-reconcile"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-geo-reconcile": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-geo-reconcile"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-geo-reconcile -- npx -y @pipeworx/mcp-geo-reconcile
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-geo-reconcile": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-geo-reconcile"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-geo-reconcile --command npx --arg -y --arg @pipeworx/mcp-geo-reconcile
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-geo-reconcile:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-geo-reconcile"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-geo-reconcile": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-geo-reconcile"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-geo-reconcile -t stdio -c npx -a -y @pipeworx/mcp-geo-reconcile
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-geo-reconcile": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-geo-reconcile"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 80, +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.

### 2026-11-03 (score 79, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 63, −13)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.13
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 76, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 76)

First indexed and scored.

## MCP tools (1)

### `reconcile_wikidata_osm` (~776 tokens)

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.

Input parameters:

- `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, required): 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…

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-geo-reconcile/pipeworx-mcp-geo-reconcile#diagnostics

## Score history

- 2026-11-05: 80
- 2026-11-04: 79
- 2026-11-03: 79
- 2026-11-02: 63
- 2026-11-01: 76
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 76

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-geo-reconcile
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-geo-reconcile
- Repository: https://github.com/pipeworx-io/mcp-geo-reconcile
- Website: https://pipeworx.io/packs/geo-reconcile
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-geo-reconcile/pipeworx-mcp-geo-reconcile.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-geo-reconcile/pipeworx-mcp-geo-reconcile.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-geo-reconcile/pipeworx-mcp-geo-reconcile