Home / Token cost / Name Whisper

The Name Whisper MCP server costs 8,423 tokens before the first call.

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

QUICK ANSWER The Name Whisper MCP server's tool definitions consume 8,423 tokens — 4.4× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 34 tools · 8,423 tokens · 4.2% of 200k · 0.8% 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 4.2%
1M WINDOW 0.8%

Corpus context: Name Whisper ranks #226 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 8,423 tokens go.

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

ToolCategoryTokens% of server
set_ens_records Write 552 6.6%
manage_fuses Destructive 544 6.5%
bulk_set_records Write 508 6.0%
provision_agent_identity Read 459 5.4%
approve_operator Write 434 5.2%
purchase_name Read 349 4.1%
bulk_transfer_ens_names Financial 339 4.0%
renew_ens_name Read 334 4.0%
wrap_name Destructive 331 3.9%
find_alpha Read 298 3.5%
search_agent_directory Read 297 3.5%
mint_subnames Write 296 3.5%
bulk_register Write 242 2.9%
set_resolver Write 239 2.8%
make_offer Execute 223 2.6%
search_knowledge Read 223 2.6%
transfer_ens_name Financial 206 2.4%
extend_subname_expiry Write 206 2.4%
set_primary_name Write 196 2.3%
search_ens_names Read 192 2.3%
unwrap_name Read 189 2.2%
reclaim_name Write 187 2.2%
wash_check Read 182 2.2%
manage_ens_name Write 175 2.1%
get_primary_name Read 174 2.1%
get_market_activity Read 167 2.0%
get_agent_reputation Read 162 1.9%
get_wallet_portfolio Read 142 1.7%
get_similar_names Read 125 1.5%
get_valuation Read 115 1.4%
check_availability Read 108 1.3%
get_name_details Read 95 1.1%
get_caller_identity Read 92 1.1%
get_usage_stats Read 42 0.5%

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

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

Grant scopeDefinition costReduction
All 34 tools (no gateway) 8,423 tokens
3 granted tools ~743 tokens −91%
5 granted tools ~1,239 tokens −85%
10 granted tools ~2,477 tokens −71%

Name Whisper token-cost questions.

How many tokens does the Name Whisper MCP server use?+

Its 34 tool definitions total 8,423 tokens — 4.2% 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 Name Whisper 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 Name Whisper's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Name Whisper 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 743 tokens, a 91% 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 34 catalogued Name Whisper tools. Counts refresh with every site build.

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

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