Home / Token cost / France Data Mcp

The France Data MCP server costs 21,307 tokens before the first call.

Connect France Data and its 36 tool definitions are loaded into the model's context on every request — 11% of a 200k window spent before your agent does anything.

QUICK ANSWER The France Data Mcp MCP server's tool definitions consume 21,307 tokens — 11× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 36 tools · 21,307 tokens · 11% of 200k · 2.1% of 1M Method →

What that buys before your agent starts working.

Tool definitions are overhead: they occupy context on every request and compete with your code, documents and conversation history for the same window.

200K WINDOW 11%
1M WINDOW 2.1%

Corpus context: France Data ranks #52 of 3,213 measured MCP servers by definition cost. The median is 1,905 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own.

Where the 21,307 tokens go.

Each row is one tool definition as a tools/list entry — name, description and input schema — counted with o200k_base. Average: 592 tokens per tool.

ToolCategoryTokens% of server
densite_sante Read 1,631 7.7%
professionnels_in_radius Read 1,161 5.4%
professionnels_rpps_in_radius Read 1,126 5.3%
lister_nomenclature Read 983 4.6%
etablissements_finess_by_categorie Read 952 4.5%
panorama_sante_territoire Read 908 4.3%
centres_sante_in_radius Read 795 3.7%
professionnels_par_specialite_dept Read 792 3.7%
verifier_site_actif Read 788 3.7%
professionnels_rpps_par_dept Read 782 3.7%
finess_sirene_coverage_in_radius Read 748 3.5%
panorama_implantation_complet Read 704 3.3%
etablissements_finess_in_radius Read 701 3.3%
inspect_site Read 699 3.3%
rpps_search_by_name Read 662 3.1%
entreprises_in_radius Read 631 3.0%
profil_iris Read 540 2.5%
population Read 521 2.4%
reconcilier_finess_sirene Read 513 2.4%
rpps_dans_etablissement Read 462 2.2%
compare_adresse_cnam_vs_finess Read 446 2.1%
professionnel_by_rpps Read 444 2.1%
entreprise_by_siren Read 422 2.0%
centres_sante_by_finess Read 420 2.0%
etablissement_by_siret Read 415 1.9%
etablissement_by_finess Read 395 1.9%
compare_raison_sociale_finess_vs_rpps Read 360 1.7%
historique_etablissement Read 357 1.7%
data_freshness Read 340 1.6%
dynamique_immobiliere Read 325 1.5%
enrichir_concurrents Read 283 1.3%
autocomplete_commune Read 272 1.3%
geocode_adresse Read 228 1.1%
cout_foncier Read 190 0.9%
get_commune_by_code Read 178 0.8%
reverse_geocode Read 133 0.6%

Most agents use a handful of these tools. They pay for all 36.

A PolicyLayer grant exposes only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. Estimates below assume typical-weight tools (592 tokens each).

Grant scopeDefinition costReduction
All 36 tools (no gateway) 21,307 tokens
3 granted tools ~1,776 tokens −92%
5 granted tools ~2,959 tokens −86%
10 granted tools ~5,919 tokens −72%

France Data Mcp token-cost questions.

How many tokens does the France Data MCP server use?+

Its 36 tool definitions total 21,307 tokens — 11% of a 200k context window — measured with tiktoken o200k_base over the serialised tools/list payload. Exact counts vary slightly by client and model.

Why does France Data Mcp consume tokens before I send a message?+

MCP clients load every connected server's tool definitions — name, description, and input schema — into the model's context so it knows what it can call. That payload is charged against your context window on every request, whether or not a tool is used.

How do I reduce France Data Mcp's token usage?+

Expose fewer tools. A PolicyLayer grant scopes France Data Mcp to only the tools you allow — ungranted definitions are filtered out of the tool list, so they never enter the context window. A grant of 3 typical tools costs roughly 1,776 tokens, a 92% reduction.

Does deferred tool loading fix this?+

Partially, in some clients. Claude Code defers MCP tool schemas behind a tool-search step by default, and VS Code has experimental grouping — but you still pay tokens per search and reload, and Cursor, Windsurf and Gemini CLI load definitions upfront. Reducing the exposed tool set cuts the cost in every client.

How these numbers were measured.

01
Serialisation

Each tool is serialised as a tools/list entry — name, description, input schema — from the schemas in the PolicyLayer scan database. Clients differ slightly in framing, so treat counts as close estimates.

02
Tokeniser

tiktoken o200k_base (GPT-4o/o-series). Anthropic's current tokeniser isn't published, so Claude's exact counts will differ; for English text and JSON schemas the totals are close enough to treat these as estimates.

03
Deferred loading

Some clients now defer schema loading (Claude Code's tool search; VS Code experimental grouping). You still pay per search and reload — and Cursor, Windsurf and Gemini CLI load everything upfront.

Computed 07-06-2026 from the PolicyLayer scan database over all 36 catalogued France Data Mcp tools. Counts refresh with every site build.

Expose only the tools you use — the rest never enter your context.

A PolicyLayer grant scopes France Data Mcp to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.

// GET IN TOUCH

Have a question or want to learn more? Send us a message.

Message sent.

We'll get back to you soon.