Home / Token cost / Quantum

The Quantum MCP server costs 1,925 tokens before the first call.

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

QUICK ANSWER The Quantum MCP server's tool definitions consume 1,925 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 20 tools · 1,925 tokens · 1.0% 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 1.0%
1M WINDOW 0.2%

Corpus context: Quantum ranks #1600 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,925 tokens go.

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

ToolCategoryTokens% of server
quantum_execute Execute 170 8.8%
quantum_subscribe Read 159 8.3%
quantum_ask Read 154 8.0%
quantum_join Read 151 7.8%
quantum_intent Read 136 7.1%
quantum_scan Read 125 6.5%
quantum_settle Read 101 5.2%
quantum_deal Read 95 4.9%
quantum_route Read 95 4.9%
quantum_feed Read 87 4.5%
quantum_rate Read 84 4.4%
quantum_preflight Read 79 4.1%
quantum_nodes Read 75 3.9%
quantum_trust_passport Read 73 3.8%
quantum_reputation Read 68 3.5%
quantum_refer Read 63 3.3%
quantum_history Read 60 3.1%
neural_status Read 53 2.8%
quantum_offer Read 50 2.6%
quantum_status Read 47 2.4%

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

Grant scopeDefinition costReduction
All 20 tools (no gateway) 1,925 tokens
3 granted tools ~289 tokens −85%
5 granted tools ~481 tokens −75%
10 granted tools ~963 tokens −50%

Quantum token-cost questions.

How many tokens does the Quantum MCP server use?+

Its 20 tool definitions total 1,925 tokens — 1.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 Quantum 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 Quantum's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Quantum 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 289 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 Quantum tools. Counts refresh with every site build.

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

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