Home / Token cost / Scout

The Scout MCP server costs 3,929 tokens before the first call.

Connect Scout and its 18 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 Scout MCP server's tool definitions consume 3,929 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 18 tools · 3,929 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: Scout ranks #1161 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,929 tokens go.

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

ToolCategoryTokens% of server
scout.find_public_agent Execute 572 14.6%
scout.route_lead Read 497 12.6%
scout.find_brokerage Read 296 7.5%
scout.get_seller_signals Read 279 7.1%
scout.search_leads Read 270 6.9%
scout.search_listings Read 219 5.6%
scout.verify_license Read 196 5.0%
scout.subscribe_lead_feed Read 194 4.9%
scout.find_agent Read 193 4.9%
scout.market_pulse Read 174 4.4%
scout.team_roster Read 174 4.4%
scout.school_district Read 157 4.0%
scout.purchase_lead Read 134 3.4%
scout.agent_profile Read 129 3.3%
scout.referral_terms Read 128 3.3%
scout.estimate_value Read 124 3.2%
scout.compare_agents Read 120 3.1%
scout.coverage Read 73 1.9%

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

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

Grant scopeDefinition costReduction
All 18 tools (no gateway) 3,929 tokens
3 granted tools ~655 tokens −83%
5 granted tools ~1,091 tokens −72%
10 granted tools ~2,183 tokens −44%

Scout token-cost questions.

How many tokens does the Scout MCP server use?+

Its 18 tool definitions total 3,929 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 Scout 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 Scout's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Scout 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 655 tokens, a 83% 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 18 catalogued Scout tools. Counts refresh with every site build.

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

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