Home / Token cost / Freshcontext

The Freshcontext MCP server costs 3,919 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 21 tools · 3,919 tokens · 2.0% of 200k · 0.4% 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 2.0%
1M WINDOW 0.4%

Corpus context: Freshcontext ranks #1163 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,919 tokens go.

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

ToolCategoryTokens% of server
extract_finance_landscape Read 330 8.4%
extract_company_landscape Read 318 8.1%
extract_gov_landscape Read 315 8.0%
search_jobs Read 288 7.3%
extract_idea_landscape Read 281 7.2%
extract_govcontracts Read 216 5.5%
extract_changelog Read 202 5.2%
extract_gebiz Read 194 5.0%
extract_gdelt Read 182 4.6%
extract_sec_filings Read 173 4.4%
extract_landscape Read 144 3.7%
extract_reddit Read 142 3.6%
extract_finance Read 134 3.4%
extract_hackernews Read 134 3.4%
extract_yc Read 133 3.4%
extract_arxiv Read 128 3.3%
extract_producthunt Read 127 3.2%
package_trends Read 125 3.2%
extract_github Read 121 3.1%
search_repos Read 117 3.0%
extract_scholar Read 115 2.9%

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

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

Grant scopeDefinition costReduction
All 21 tools (no gateway) 3,919 tokens
3 granted tools ~560 tokens −86%
5 granted tools ~933 tokens −76%
10 granted tools ~1,866 tokens −52%

Freshcontext token-cost questions.

How many tokens does the Freshcontext MCP server use?+

Its 21 tool definitions total 3,919 tokens — 2.0% 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 Freshcontext 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 Freshcontext's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Freshcontext 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 560 tokens, a 86% 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 21 catalogued Freshcontext tools. Counts refresh with every site build.

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

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