Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

France Geodata

NPM · @PIPEWORX/MCP-FRANCE-GEODATA · 2 COMPONENTS

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

+3 this week 83 Trust /100

Last scanned (11 hours ago)

Scores higher than 76% of npm servers

Category Maps and Location

Trust breakdown (7 categories)

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-france-geodata). 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 Usability68
  • AI-judged instruction clarity (good).Pass
  • 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. 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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
Changelog

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 −14
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 29 Oct 26 80

    First indexed and scored.

Diagnostics

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-france-geodata@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-france-geodata
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-france-geodata/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637319148
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5991621c638561e7f8e1e9d30a5deac0489c383dce094ebfd2a2e07c5e76ee5e513c4ad8dcb8004f5678d6e28f782e1d77e2b74b03e68f42a321a01b7

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~642 tokens

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 →

Tool Tokens
fr_buildings_near ~193

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.

NameTypeReqDescription
include_geometryboolean–Include polygon geometry (default true). Set false for attributes only.
latnumberyesLatitude (WGS84), e.g. 45.764.
limitnumber–Max buildings returned, 1-200 (default 50). Nearest first.
lonnumberyesLongitude (WGS84), e.g. 4.8357.
radius_mnumber–Search radius in metres, 1-500 (default 200).

No output schema declared.

No examples provided.

fr_commune ~192

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.

NameTypeReqDescription
insee_codestring–5-character INSEE code, e.g. "69123" (Corsica: "2A004").
latnumber–Latitude (WGS84); pair with lon to find the commune at a point.
limitnumber–Max communes for a name search, 1-20 (default 5).
lonnumber–Longitude (WGS84); pair with lat.
namestring–Commune name, e.g. "Lyon". Returns the best matches.

No output schema declared.

No examples provided.

fr_flood_zones ~143

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.

NameTypeReqDescription
latnumberyesLatitude (WGS84).
lonnumberyesLongitude (WGS84).
radius_mnumber–Search radius in metres, 100-10000 (default 1000).

No output schema declared.

No examples provided.

fr_land_cover ~114

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

NameTypeReqDescription
latnumberyesLatitude (WGS84).
lonnumberyesLongitude (WGS84).

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-france-geodata

# add to Claude Code
claude mcp add pipeworx-io-france-geodata -- npx -y @pipeworx/mcp-france-geodata
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.