France Data MCP permet aux agents IA d’interroger, croiser et enrichir automatiquement plusieurs référentiels publics français via une interface MCP unifiée. France Data MCP fournit une couche d’intelligence territoriale française conçue pour le reasoning multi-sources et l’orchestration agentique. Le serveur combine données territoriales, géocodage, santé publique, référentiels administratifs et enrichissement multi-sources afin de permettre des workflows complexes de raisonnement géospatial et territorial. Contrairement à de simples wrappers API, les tools sont conçus pour être chaînables par les agents IA afin de résoudre automatiquement des questions métier complexes. Exemples de workflows agentiques : → « Cette pharmacie est-elle réellement encore active ? » Détection des SIRET fermés invisibles côté DREES via cross-source FINESS ↔ RPPS ↔ SIRENE → « Où installer un spécialiste à Metz ? » Croisement densité médicale Ameli + RPPS + cartographie FINESS → « Quels sont les concurrents M&A potentiels d’un groupe pharmacie ? » Historique SIRENE + matching adresse + détection de rebrandings non propagés → « Cartographier l’offre de soins d’un canton » Combinaison FINESS + RPPS + entreprises + coverage ratio géospatial Sources intégrées : FINESS DREES RPPS / Annuaire Santé ANS Annuaire Santé Ameli INSEE SIRENE IGN Géoplateforme geo.api.gouv.fr (DINUM) Capabilities : • orchestration multi-référentiels • géocodage et enrichissement territorial • reasoning multi-étapes pour agents IA • workflows géospatiaux chaînables • cross-reference intelligence entre référentiels publics • compatibilité MCP HTTP + wrappers npm/stdIO • observabilité Sentry

MCP readiness

B · 86/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 72.5/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1838 ms).
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	30/30 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 37 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	2/5	Declares credential scheme: smithery_api_key.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1838 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 80% of peers; This listing 86 · peer median 81
Latency: Faster than 14% of peers; This listing 777 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Auth declaration −3 — State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

smithery since 2026-06-04 ↗

How to connect

MCP endpoint (streamable-http)

https://server.smithery.ai/cturkieh/france-data/mcp

JSON-RPC initialize probe

curl -X POST https://server.smithery.ai/cturkieh/france-data/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://github.com/cturkieh/

Listed at (smithery)

https://github.com/cturkieh/