# France Geodata (npm · @pipeworx/mcp-france-geodata)

France Geodata MCP — point/radius questions on French public geodata.

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

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-france-geodata/france-geodata-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-france-geodata/france-geodata-mcp)
- npm · `@pipeworx/mcp-france-geodata`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-france-geodata/pipeworx-mcp-france-geodata.md), [page](https://verifymcp.io/servers/pipeworx-io-france-geodata/pipeworx-mcp-france-geodata)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-france-geodata`
- 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-france-geodata).
  - 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**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 697 tokens (~174/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 France Geodata MCP server?

France Geodata runs locally as an npm package, launched with npx -y @pipeworx/mcp-france-geodata. 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-france-geodata -- npx -y @pipeworx/mcp-france-geodata
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-france-geodata -- npx -y @pipeworx/mcp-france-geodata
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-france-geodata --command npx --arg -y --arg @pipeworx/mcp-france-geodata
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 83, +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 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 66, −14)

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

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

First indexed and scored.

## MCP tools (4)

### `fr_commune` (~192 tokens)

French commune lookup (Etalab/INSEE commune register): INSEE code, postcodes, population, department, region, centre point and area. Look up by name or INSEE code, or pass lat+lon to find the commune containing a point. Example: "population of Lyon" -> 69123, 519,127.

Input parameters:

- `insee_code` (string): 5-character INSEE code, e.g. "69123" (Corsica: "2A004").
- `lat` (number): Latitude (WGS84); pair with lon to find the commune at a point.
- `limit` (number): Max communes for a name search, 1-20 (default 5).
- `lon` (number): Longitude (WGS84); pair with lat.
- `name` (string): Commune name, e.g. "Lyon". Returns the best matches.

### `fr_buildings_near` (~193 tokens)

Buildings within a radius (max 500 m) of a point in France, from the IGN BD TOPO building layer. Each building has GeoJSON polygon geometry, height (m), floors, dwellings, use, nature and construction dates. Reports the total matched and flags truncation. Use for "buildings within 200 m of X" and GeoJSON export of them.

Input parameters:

- `include_geometry` (boolean): Include polygon geometry (default true). Set false for attributes only.
- `lat` (number, required): Latitude (WGS84), e.g. 45.764.
- `limit` (number): Max buildings returned, 1-200 (default 50). Nearest first.
- `lon` (number, required): Longitude (WGS84), e.g. 4.8357.
- `radius_m` (number): Search radius in metres, 1-500 (default 200).

### `fr_land_cover` (~114 tokens)

Land cover at a point in mainland France: the CORINE Land Cover 2018 class (code and label, e.g. 112 "Discontinuous urban fabric") of the polygon containing the point, with its area. Resolution is 25 ha mapping units, so it describes the surrounding area, not the exact spot. found:false when the point is outside the coverage (sea, abroad, overseas).

Input parameters:

- `lat` (number, required): Latitude (WGS84).
- `lon` (number, required): Longitude (WGS84).

### `fr_flood_zones` (~143 tokens)

Flood-risk information around a point in France from Géorisques (French Ministry of Ecological Transition): the flood hazards recorded for the commune at the point, the flood-zone atlases (AZI) covering communes within the radius, and any significant-flood-risk territory (TRI) in range. These are risk-record listings, not parcel-level flood polygons, so absence of a record is not proof of no flood risk.

Input parameters:

- `lat` (number, required): Latitude (WGS84).
- `lon` (number, required): Longitude (WGS84).
- `radius_m` (number): Search radius in metres, 100-10000 (default 1000).

## Diagnostics

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

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 66
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 80

## Common questions

### What is the France Geodata MCP server?

France Geodata is an MCP server listed in the public MCP registry as io.github.pipeworx-io/france-geodata. France Geodata MCP, point/radius questions on French public geodata. This page covers its npm package (@pipeworx/mcp-france-geodata).

### Is the France Geodata MCP server safe to use?

France Geodata scores 83 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 France Geodata MCP server expose?

France Geodata exposes 4 tools: fr_commune, fr_buildings_near, fr_land_cover, fr_flood_zones. Their descriptions and schemas cost roughly 642 tokens of context every time the server is loaded.

### Is the France Geodata MCP server still maintained?

France Geodata 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 France Geodata MCP server under?

France Geodata 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-france-geodata
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-france-geodata
- Repository: https://github.com/pipeworx-io/mcp-france-geodata
- Website: https://pipeworx.io/packs/france-geodata
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-france-geodata/pipeworx-mcp-france-geodata.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-france-geodata/pipeworx-mcp-france-geodata.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-france-geodata/pipeworx-mcp-france-geodata