This server can only be called with an API key (a Smithery proxy address). We cannot connect without one, so no measurements are taken and the metrics below stay empty.

france-data

https://france-data--cturkieh.run.tools ↗

france-data is a remote MCP server published at france-data--cturkieh.run.tools. Its tool list could not be read; the server is closed to direct calls. It answers direct calls with an authentication wall.

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 concu

Auth-gatedWebsite ↗5260 usesVersion: —First probe: —Last probe: —

Agent readability score

Can an LLM agent pick the right tool here — names, descriptions and parameter clarity are assessed.

Agent readability score

A premier territorial intelligence server offering deep, multi-source French data with expert-level guidance for complex agentic reasoning and tool chaining.based on catalog declaration

Strengths

Exceptional documentation explaining not just 'what' but 'when' and 'why' to use specific tools
Clear differentiation between overlapping tools (e.g., Ameli vs RPPS) to prevent agent confusion
Robust error and reliability signaling, such as confidence scores and 'found' discriminators
Excellent guidance on parameter constraints, required combinations, and supported aliases

Weaknesses

High token overhead due to extremely detailed, long-form descriptions
High complexity for the agent to navigate 36 specialized tools without a meta-strategy

autocomplete_commune — Aliases are documented in the description but not explicitly defined in the parameter schema

Verdict

This server is a gold standard for agentic orchestration, providing the semantic nuance required for high-stakes territorial reasoning. It minimizes hallucinations by explicitly defining data reliability and cross-referencing logic.

9/4/2026, 11:20:04 AM

Event narrative

Raw observations

Run	Era	Modern	ms	Legacy	ms	Versions

Supported versions

—

as declared by server/discover + initialize

Capabilities

—

not readable

Schema score

—

not measurable

Schema compliance

tools/list structure, inputSchema validity, and a functional smoke test — the components of the 0-100 score.

—

not measurable

tools/list not measurable
inputSchema not measurable
Smoke test not run this round
Cold-start not measurable (no handshake)

Era history

Each cell is one probe run. Faded cells are incomplete probes — one leg did not answer, so the era is inconclusive.

No era measurements yet.

Response time history

The two probe legs separately: modern server/discover and legacy initialize.

No response-time measurements yet.

Event log

Derived by comparing consecutive probes — changes in era, protocol version, build and reachability.

Get your badge

Add this badge to your README — it updates automatically as measurements change.

Markdown

[![mcpmetrics](https://mcpmetrics.io/badge/cturkieh/france-data/era.svg)](https://mcpmetrics.io/servers/cturkieh-france-data)

HTML

<a href="https://mcpmetrics.io/servers/cturkieh-france-data"><img src="https://mcpmetrics.io/badge/cturkieh/france-data/era.svg" alt="mcpmetrics"></a>

Raw observations

You are seeing the last 7 days. Sign up for the full history. Which check failed and why is in the dashboard.