Home / Token cost / Lician

The Lician MCP server costs 1,581 tokens before the first call.

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

QUICK ANSWER The Lician MCP server's tool definitions consume 1,581 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 16 tools · 1,581 tokens · 0.8% of 200k · 0.2% 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 0.8%
1M WINDOW 0.2%

Corpus context: Lician ranks #1762 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 1,581 tokens go.

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

ToolCategoryTokens% of server
get_insider_trades Read 139 8.8%
get_sec_filings Read 127 8.0%
get_historical_prices Read 125 7.9%
get_balance_sheet Read 119 7.5%
get_income_statement Read 119 7.5%
get_cash_flow Read 118 7.5%
get_investor_portfolio Read 110 7.0%
get_institutional_holders Read 95 6.0%
get_stock_news Read 92 5.8%
get_stock_price Read 89 5.6%
get_analyst_estimates Read 86 5.4%
get_financial_metrics Read 84 5.3%
get_crypto_prices Read 75 4.7%
get_analyst_ratings Read 74 4.7%
get_company_info Read 70 4.4%
get_interest_rates Read 59 3.7%

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

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

Grant scopeDefinition costReduction
All 16 tools (no gateway) 1,581 tokens
3 granted tools ~296 tokens −81%
5 granted tools ~494 tokens −69%
10 granted tools ~988 tokens −38%

Lician token-cost questions.

How many tokens does the Lician MCP server use?+

Its 16 tool definitions total 1,581 tokens — 0.8% 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 Lician 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 Lician's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Lician 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 296 tokens, a 81% 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 16 catalogued Lician tools. Counts refresh with every site build.

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

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