Home / Token cost / LION - keyless data for AI agents: CPG, enrichment, social (attested)

The LION - keyless data for AI agents: CPG, enrichment, social (attested) MCP server costs 6,367 tokens before the first call.

Connect LION - keyless data for AI agents: CPG, enrichment, social (attested) and its 20 tool definitions are loaded into the model's context on every request — 3.2% of a 200k window spent before your agent does anything.

QUICK ANSWER The LION - keyless data for AI agents: CPG, enrichment, social (attested) MCP server's tool definitions consume 6,367 tokens — 3.3× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 20 tools · 6,367 tokens · 3.2% of 200k · 0.6% 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 3.2%
1M WINDOW 0.6%

Corpus context: LION - keyless data for AI agents: CPG, enrichment, social (attested) ranks #941 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 6,367 tokens go.

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

ToolCategoryTokens% of server
lion_enrich_v1 Read 738 11.6%
lion_composite_bundle Write 581 9.1%
lion_poi_business_search Read 483 7.6%
lion_keyless_base_rpc Destructive 466 7.3%
lion_sec_financials Read 338 5.3%
lion_vat_validation Read 329 5.2%
lion_adaptive_query Read 323 5.1%
lion_domain_intel Read 317 5.0%
lion_ofac_sanctions_screen Read 306 4.8%
lion_wikidata_firmographics Read 291 4.6%
lion_cpg_product_intel Read 269 4.2%
lion_declare_need Destructive 264 4.1%
lion_web_enrichment_bundle Read 241 3.8%
lion_social_signal_intel Read 237 3.7%
lion_credits_purchase Read 227 3.6%
lion_enrichment_tx_bundle Execute 221 3.5%
lion_token_risk_indicators Read 210 3.3%
lion_location_solar_enrichment Read 205 3.2%
lion_tx_receipt_decoded Read 176 2.8%
lion_quick_intel Read 145 2.3%

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

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

Grant scopeDefinition costReduction
All 20 tools (no gateway) 6,367 tokens
3 granted tools ~955 tokens −85%
5 granted tools ~1,592 tokens −75%
10 granted tools ~3,184 tokens −50%

LION - keyless data for AI agents: CPG, enrichment, social (attested) token-cost questions.

How many tokens does the LION - keyless data for AI agents: CPG, enrichment, social (attested) MCP server use?+

Its 20 tool definitions total 6,367 tokens — 3.2% 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 LION - keyless data for AI agents: CPG, enrichment, social (attested) 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 LION - keyless data for AI agents: CPG, enrichment, social (attested)'s token usage?+

Expose fewer tools. A PolicyLayer grant scopes LION - keyless data for AI agents: CPG, enrichment, social (attested) 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 955 tokens, a 85% 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 20 catalogued LION - keyless data for AI agents: CPG, enrichment, social (attested) tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes LION - keyless data for AI agents: CPG, enrichment, social (attested) 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.