Home / Token cost / Service Public France

The Service Public France MCP server costs 9,368 tokens before the first call.

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

QUICK ANSWER The Service Public France MCP server's tool definitions consume 9,368 tokens — 4.9× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 38 tools · 9,368 tokens · 4.7% of 200k · 0.9% 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 4.7%
1M WINDOW 0.9%

Corpus context: Service Public France ranks #191 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 9,368 tokens go.

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

ToolCategoryTokens% of server
simuler_impot_revenu Read 523 5.6%
simuler_taxe_fonciere Read 384 4.1%
rechercher_offre_emploi Read 350 3.7%
consulter_parcoursup_stats Read 321 3.4%
consulter_fiscalite_locale Read 320 3.4%
consulter_resultats_lycee Read 320 3.4%
consulter_transactions_immobilieres Read 306 3.3%
consulter_insertion_professionnelle Read 303 3.2%
rechercher_marche_public Read 303 3.2%
consulter_parcoursup Read 299 3.2%
rechercher_etablissement_scolaire Read 299 3.2%
rechercher_annonce_legale Read 292 3.1%
rechercher_formation Read 287 3.1%
consulter_journal_officiel Read 279 3.0%
consulter_aide_sociale Read 268 2.9%
rechercher Read 268 2.9%
rechercher_code_juridique Read 267 2.9%
simuler_frais_notaire Read 260 2.8%
consulter_sirene_historique Read 254 2.7%
consulter_prix_carburant Read 251 2.7%
consulter_evaluations_nationales Read 245 2.6%
rechercher_texte_legal Read 235 2.5%
consulter_securite Read 221 2.4%
rechercher_subvention Read 217 2.3%
comparer_communes Read 215 2.3%
rechercher_jurisprudence Read 211 2.3%
consulter_acces_soins Read 206 2.2%
consulter_zonage_immobilier Read 199 2.1%
consulter_risques_naturels Read 187 2.0%
rechercher_entreprise Read 172 1.8%
consulter_budget_epci Read 168 1.8%
rechercher_convention_collective Read 167 1.8%
consulter_budget_commune Read 165 1.8%
rechercher_service_local Read 155 1.7%
rechercher_doctrine_fiscale Read 151 1.6%
rechercher_fiche Read 150 1.6%
lire_fiche Read 81 0.9%
naviguer_themes Read 69 0.7%

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

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 (247 tokens each).

Grant scopeDefinition costReduction
All 38 tools (no gateway) 9,368 tokens
3 granted tools ~740 tokens −92%
5 granted tools ~1,233 tokens −87%
10 granted tools ~2,465 tokens −74%

Service Public France token-cost questions.

How many tokens does the Service Public France MCP server use?+

Its 38 tool definitions total 9,368 tokens — 4.7% 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 Service Public France 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 Service Public France's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Service Public France 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 740 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 38 catalogued Service Public France tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Service Public France 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.