Home / Token cost / Cultural Intelligence

The Cultural Intelligence MCP server costs 3,073 tokens before the first call.

Connect Cultural Intelligence and its 43 tool definitions are loaded into the model's context on every request — 1.5% of a 200k window spent before your agent does anything.

QUICK ANSWER The Cultural Intelligence MCP server's tool definitions consume 3,073 tokens — around the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 43 tools · 3,073 tokens · 1.5% of 200k · 0.3% 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 1.5%
1M WINDOW 0.3%

Corpus context: Cultural Intelligence ranks #1288 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 3,073 tokens go.

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

ToolCategoryTokens% of server
compound_query Read 152 4.9%
cultural_profile Read 142 4.6%
blend Read 124 4.0%
creator_match Read 121 3.9%
ad_creative_brief Read 119 3.9%
shop_world Read 111 3.6%
resolve Write 105 3.4%
creator_deploy Execute 101 3.3%
dcr_query Read 101 3.3%
audience_segment Read 89 2.9%
opportunities Execute 88 2.9%
neighbors Read 87 2.8%
construct Read 85 2.8%
emerging Read 76 2.5%
simulate Read 76 2.5%
recommend_products Read 70 2.3%
expand Read 68 2.2%
get_trend_momentum Read 67 2.2%
lookup_world Read 67 2.2%
resolve_vibe Write 67 2.2%
compare_worlds Read 63 2.1%
bridge Read 62 2.0%
decode Read 62 2.0%
media_pyramid Read 62 2.0%
compare Read 61 2.0%
gap Read 59 1.9%
position Read 56 1.8%
ask_culture Read 54 1.8%
trajectory Read 52 1.7%
brand_position Read 51 1.7%
recommend Read 51 1.7%
signal Read 51 1.7%
get_product_link Read 50 1.6%
ask Read 48 1.6%
velocity Read 47 1.5%
lookup_creator Read 45 1.5%
pulse Read 43 1.4%
trending Read 43 1.4%
get_forecast Read 42 1.4%
detect_anomalies Read 41 1.3%
cultural_pulse Read 39 1.3%
gap_predictions Read 39 1.3%
search Read 36 1.2%

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

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

Grant scopeDefinition costReduction
All 43 tools (no gateway) 3,073 tokens
3 granted tools ~214 tokens −93%
5 granted tools ~357 tokens −88%
10 granted tools ~715 tokens −77%

Cultural Intelligence token-cost questions.

How many tokens does the Cultural Intelligence MCP server use?+

Its 43 tool definitions total 3,073 tokens — 1.5% 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 Cultural Intelligence 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 Cultural Intelligence's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Cultural Intelligence 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 214 tokens, a 93% 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 43 catalogued Cultural Intelligence tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Cultural Intelligence 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.