Home / Token cost / Drwho Me developer tools

The Drwho Me developer tools MCP server costs 4,084 tokens before the first call.

Connect Drwho Me developer tools and its 19 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 Drwho Me developer tools MCP server's tool definitions consume 4,084 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 19 tools · 4,084 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: Drwho Me developer tools ranks #1133 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 4,084 tokens go.

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

ToolCategoryTokens% of server
dossier_dkim Read 284 7.0%
dossier_cors Write 284 7.0%
dns_lookup Read 282 6.9%
dossier_full Execute 240 5.9%
dossier_dmarc Read 235 5.8%
dossier_dns Read 232 5.7%
dossier_spf Read 231 5.7%
dossier_web_surface Read 221 5.4%
dossier_headers Read 215 5.3%
dossier_mx Read 212 5.2%
user_agent_parse Execute 205 5.0%
dossier_tls Read 203 5.0%
dossier_redirects Read 201 4.9%
ip_lookup Read 190 4.7%
dossier_dnssec Read 185 4.5%
dossier_mta_sts Read 185 4.5%
dossier_whois Read 163 4.0%
dossier_ct_log Read 160 3.9%
dossier_tlsrpt Read 156 3.8%

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

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

Grant scopeDefinition costReduction
All 19 tools (no gateway) 4,084 tokens
3 granted tools ~645 tokens −84%
5 granted tools ~1,075 tokens −74%
10 granted tools ~2,149 tokens −47%

Drwho Me developer tools token-cost questions.

How many tokens does the Drwho Me developer tools MCP server use?+

Its 19 tool definitions total 4,084 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 Drwho Me developer tools 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 Drwho Me developer tools's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Drwho Me developer tools 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 645 tokens, a 84% 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 19 catalogued Drwho Me developer tools tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Drwho Me developer tools 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.