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.

io.github.cturkieh/france-data-mcp

REMOTE · FRANCE-DATA-MCP.VERCEL.APP · 2 COMPONENTS

French public-data MCP: cross-ref health, demographics, business, geo & real-estate.

0 this week 83 Trust /100

Last scanned (22 hours ago)

Scores higher than 83% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 22372 tokens (~604/item across 37 items; 37 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 92% of tool parameters carry a description.Partial
  • Structured output schemas are declared (81% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 37 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 38 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 9 Nov 26 0
    • Stability: 0.97 → pass security
  • 8 Nov 26 0
    • Stability: pass → 0.97 functional
  • 7 Nov 26 0
    • Tool “cout_foncier” rewrote its description, which is the text the model reads security
    • Tool “dynamique_immobiliere” rewrote its description, which is the text the model reads security
    • Tool “data_freshness” rewrote its description, which is the text the model reads security
    • Server version: 0.31.2 → 0.32.0 functional
    • Server version: 0.31.1 → 0.31.2 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 22 Sept 26 0
    • Tool “data_freshness” rewrote its description, which is the text the model reads security
    • Tool “dynamique_immobiliere” rewrote its description, which is the text the model reads security
    • Server version: 0.30.0 → 0.31.0 functional
    • New tool “etablissement_finess_by_nom” functional
  • 6 Sept 26 0
    • Tool “etablissements_finess_in_radius” rewrote its description, which is the text the model reads security
    • Tool “etablissements_finess_by_categorie” rewrote its description, which is the text the model reads security
    • Tool “etablissement_by_finess” rewrote its description, which is the text the model reads security
    • Tool “data_freshness” rewrote its description, which is the text the model reads security
    • Server version: 0.29.0 → 0.30.0 functional
    • Server version: 0.28.0 → 0.29.0 functional
    • Server version: 0.27.0 → 0.28.0 functional
    • “rpps_search_by_name” reworded the description of “include_freshness” cosmetic
    • “professionnels_rpps_in_radius” reworded the description of “include_freshness” cosmetic
    • “professionnels_rpps_par_dept” reworded the description of “include_freshness” cosmetic
    • “rpps_dans_etablissement” reworded the description of “include_freshness” cosmetic
    • “centres_sante_by_finess” reworded the description of “include_freshness” cosmetic
    • “centres_sante_in_radius” reworded the description of “include_freshness” cosmetic
    • “etablissement_by_finess” reworded the description of “include_freshness” cosmetic
    • “etablissements_finess_by_categorie” reworded the description of “include_freshness” cosmetic
    • “etablissements_finess_in_radius” reworded the description of “include_freshness” cosmetic
    • “lister_nomenclature” reworded the description of “include_freshness” cosmetic
    • “professionnel_by_rpps” reworded the description of “include_freshness” cosmetic
    • “professionnels_in_radius” reworded the description of “include_freshness” cosmetic
    • “professionnels_par_specialite_dept” reworded the description of “include_freshness” cosmetic
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 21 Nov 2026 · Probed https://france-data-mcp.vercel.app/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.vercel.app CN=WR1,O=Google Trust Services,C=US 31 Oct 2026 29 Jan 2027 RSA 2048 SHA256-RSA 9c5f0e6a35c955e113044c86848e4cd5
SANs: *.vercel.app
CN=WR1,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7fd9e2c2d2048a0474b627a26d0868a7
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of france-data-mcp.vercel.app. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
app. DS published 23684 8 Verified
vercel.app. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://france-data-mcp.vercel.app/mcp Verified 200
http (plaintext) http://france-data-mcp.vercel.app/mcp HTTPS enforced 308 https://france-data-mcp.vercel.app/mcp
MCP tools · 37 exposed · ~22,318 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
rpps_search_by_name ~675

Trouve un PS par identité (matching trigram tolérant aux accents/typos). Usage : "Dr Martin à Paris" → `nom: "Martin", departement: "75"`. Nom obligatoire ; `prenom` et `departement` affinent. Tri par `match_score` ∈ [0..1] décroissant (score trigram pg_trgm). Un score <0.5 = homonymie partielle à confirmer côté caller. Sans `departement`, des homonymes exacts ("Pierre Martin") ont TOUS le même score ~1.0 et ne sont pas départagés — toujours filtrer par dept ou prénom sur un nom commun. `truncated: true` = d'autres résultats existent (restreindre, ne pas parcourir). Chaque résultat géolocalisé porte `geo_precision` ∈ {`"adresse"`, `"etablissement_finess"`, `"centroide_commune"`} — lire ce champ pour évaluer la fiabilité des `coords` (précise BAN/FINESS au m près vs centroïde commune ~3 km, non discriminant intra-commune). Catégorie par défaut : Civil (C, ~97 % — libéraux, salariés privés, hospitaliers contractuels). Opt-in : `include_agents_publics: true` ajoute Agents publics (M, ~0,3 % — PH titulaires, ARS, CNAM, Éducation nationale, PMI, militaires SSA) ; `include_etudiants: true` ajoute Étudiants (E, ~2,5 % — internes, externes, élèves IDE/SF). Réf : https://mos.esante.gouv.fr/NOS/TRE_R09-CategorieProfessionnelle/. Source : Annuaire Santé, Agence du Numérique en Santé (ANS) — Licence Ouverte v2.0

NameTypeReqDescription
departementstring–Code département INSEE (ex: '75', '2A', '2B', '971'). Métropole 2 caractères (Corse '2A'/'2B', pas '20'), DOM/COM 3 caractères.
include_agents_publicsboolean––
include_etudiantsboolean––
include_freshnessboolean–Si true, ajoute un champ `data_freshness` au payload (dans `query_metadata` si présent, sinon à la racine) listant, par source (FINESS, Ameli, RPPS, CDS, IRIS), la dernière ingestion réussie (`last_s…
limitnumber–Nombre max de résultats (1-500, défaut 100).
nomstringyesNom de famille (non vide).
prenomstring–Prénom du PS.
NameTypeReqDescription
activite_hebergeeobject–Compte juxtaposé des sites hébergeant l'activité correspondant à la famille filtrée, sous une autre catégorie FINESS. Distinct du `count` principal — lire `note` pour comprendre la sémantique et ne J…
countnumberyesNombre d'entrées retournées dans `results` (post-troncature).
freshnessobject–Fraîcheur des sources (présent si `include_freshness: true`).
perimetreobject–Lentille de la source : ce que le comptage inclut/exclut. Lire `completeness_note` et la restituer au lecteur final.
query_metadataobject–Metadata de la query (radius_km, departement, filtres appliqués, …).
resultsarrayyesEntrées métier (shape spécifique au tool, cf. description du tool).
totalnumber–Effectif réel avant troncature. Présent sur les tools de nomenclature paginés (lister_*) : `count` = échantillon, `total` = total réel, re-appeler avec un `limit` supérieur si `truncated`.
truncatedboolean–true si le total réel dépasse `limit` (re-paginer via `offset` si supporté, ou augmenter `limit` sur les lister_*). Optional sur les tools de listing exhaustif (lister_*).

No examples provided.

verifier_site_actif ~751

Vérifie si un établissement de santé FINESS est encore en activité en croisant FINESS DREES ↔ RPPS (pivot SIRET) ↔ DINUM (liste complète des SIRET du SIREN, incluant les fermés). Détecte les SIRET fermés encore listés actifs côté FINESS (DREES a 1-2 mois de retard). **V0.16 — fix succession M&A** : quand un site a changé d'exploitant (rachat), l'ancien SIRET fermé et le repreneur actif coexistent à la même adresse. Le resolver privilégie désormais le SIRET ACTIF co-localisé avec le FINESS (distance géodésique ≤ 100 m, recalibré V0.16.1 — le géocodage DREES place le point FINESS à plusieurs dizaines de mètres de l'adresse réelle) — avant, le verdict pouvait être `ferme` à tort, le best_match étant choisi sur la seule ressemblance d'adresse. Parmi les co-localisés, seul l'actif de la bande la plus proche prime : un voisin actif d'une autre adresse ne bascule pas le verdict. Un site RÉELLEMENT fermé reste `ferme` (aucun SIRET actif co-localisé). Logique : 1. Lookup FINESS pour récupérer raison sociale + adresse + téléphone DREES 2. SIRET candidats via le resolver : pivot RPPS, puis fallback géo DINUM /near_point (récupère TOUS les SIRET autour de l'adresse FINESS, actifs ET fermés — capte le repreneur invisible côté RPPS) 3. `best_match` = le SIRET ACTIF co-localisé avec le FINESS s'il en existe un ; sinon le meilleur candidat (possiblement fermé). La co-localisation est une distance géo, pas un score textuel. 4. **2 verdicts distincts** : - `verdict_site` (`actif` / `ferme` / `indetermine`) : basé sur `best_match.actif`. C'est le verdict qui compte pour un audit territorial. - `verdict_groupe` (`actif` / `ferme` / `indetermine`) : basé sur l'état admin de l'UL parente (champ `actif` DINUM). Une UL active peut très bien avoir un site fermé. **Format de retour** : objet `LookupResult` discriminé par `found`. Quand `found: true`, le payload contient `finess` (vue DREES), `candidates` (liste enrichie — chaque candidat porte `distance_finess_m`), `best_match`, `sir…

NameTypeReqDescription
num_finessstringyesNuméro FINESS exact (9 chiffres).
NameTypeReqDescription
foundbooleanyes–
keystring–Clé recherchée (SIREN, num_finess, code INSEE, …).
lookupStatusstringyes–
messagestring–Explication actionnable quand `found=false` (cause probable + remédiation).

No examples provided.

Install

How do I install the io.github.cturkieh/france-data-mcp server?

io.github.cturkieh/france-data-mcp is a hosted endpoint at https://france-data-mcp.vercel.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · france-data-mcp.vercel.app

# add to Claude Code
claude mcp add --transport http cturkieh-france-data-mcp 'https://france-data-mcp.vercel.app/mcp'
Common questions

What is the io.github.cturkieh/france-data-mcp server?

io.github.cturkieh/france-data-mcp is listed in the public MCP registry as io.github.cturkieh/france-data-mcp. French public-data MCP: cross-ref health, demographics, business, geo & real-estate. This page covers its hosted endpoint (https://france-data-mcp.vercel.app/mcp).

Is the io.github.cturkieh/france-data-mcp server safe to use?

io.github.cturkieh/france-data-mcp scores 83 out of 100 on VerifyMCP. 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 io.github.cturkieh/france-data-mcp server expose?

io.github.cturkieh/france-data-mcp exposes 37 tools: autocomplete_commune, get_commune_by_code, geocode_adresse, reverse_geocode, population, and 32 more. Their descriptions and schemas cost roughly 22,318 tokens of context every time the server is loaded.

Does the io.github.cturkieh/france-data-mcp server require authentication?

No. We connected to io.github.cturkieh/france-data-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.cturkieh/france-data-mcp server still maintained?

io.github.cturkieh/france-data-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the io.github.cturkieh/france-data-mcp server?

VerifyMCP ran 13 checks on io.github.cturkieh/france-data-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.