Home / Token cost / Driftoracle

The Driftoracle MCP server costs 800 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 15 tools · 800 tokens · 0.4% of 200k · 0.1% 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.4%
1M WINDOW 0.1%

Corpus context: Driftoracle ranks #2411 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 800 tokens go.

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

ToolCategoryTokens% of server
detect_enterprise_drift Read 130 16.3%
full_drift_scan Read 83 10.4%
configure_thresholds Write 63 7.9%
detect_regulatory_drift Read 55 6.9%
mark_drift Write 54 6.8%
trigger_remediation Execute 51 6.4%
drift_history Read 48 6.0%
drift_status Read 46 5.8%
resolve_drift Write 46 5.8%
detect_cloud_drift Read 44 5.5%
detect_control_drift Read 43 5.4%
detect_evidence_drift Read 43 5.4%
obligation_map Read 41 5.1%
health_check Read 27 3.4%
ping Read 26 3.3%

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

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

Grant scopeDefinition costReduction
All 15 tools (no gateway) 800 tokens
3 granted tools ~160 tokens −80%
5 granted tools ~267 tokens −67%
10 granted tools ~533 tokens −33%

Driftoracle token-cost questions.

How many tokens does the Driftoracle MCP server use?+

Its 15 tool definitions total 800 tokens — 0.4% 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 Driftoracle 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 Driftoracle's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Driftoracle 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 160 tokens, a 80% 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 15 catalogued Driftoracle tools. Counts refresh with every site build.

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

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