Home / Token cost / Boar blockchain MCP (basic)

The Boar blockchain MCP (basic) MCP server costs 3,493 tokens before the first call.

Connect Boar blockchain MCP (basic) and its 37 tool definitions are loaded into the model's context on every request — 1.7% of a 200k window spent before your agent does anything.

QUICK ANSWER The Boar blockchain MCP (basic) MCP server's tool definitions consume 3,493 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 37 tools · 3,493 tokens · 1.7% of 200k · 0.3% 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.7%
1M WINDOW 0.3%

Corpus context: Boar blockchain MCP (basic) ranks #1227 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,493 tokens go.

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

ToolCategoryTokens% of server
eth_get_logs Read 205 5.9%
mezo_get_logs Read 205 5.9%
eth_get_abi Read 128 3.7%
eth_estimate_gas Read 123 3.5%
btc_testnet_get_utxos Read 111 3.2%
btc_testnet_get_fee_estimate Read 109 3.1%
btc_get_utxos Read 108 3.1%
eth_resolve_ens Write 107 3.1%
btc_get_fee_estimate Read 106 3.0%
eth_get_token_balance Read 106 3.0%
mezo_get_token_balance Read 106 3.0%
eth_get_code Read 100 2.9%
mezo_get_code Read 100 2.9%
eth_lookup_selector Read 98 2.8%
eth_get_block Read 92 2.6%
eth_get_transaction_receipt Read 92 2.6%
mezo_get_block Read 92 2.6%
mezo_get_transaction_receipt Read 92 2.6%
btc_testnet_get_balance Read 91 2.6%
btc_testnet_get_history Read 91 2.6%
btc_testnet_get_transaction Read 90 2.6%
btc_get_balance Read 88 2.5%
btc_get_history Read 88 2.5%
btc_get_transaction Read 87 2.5%
eth_get_token_info Read 86 2.5%
mezo_get_token_info Read 86 2.5%
btc_testnet_get_block Read 80 2.3%
btc_get_block Read 77 2.2%
eth_get_transaction Read 77 2.2%
mezo_get_transaction Read 77 2.2%
btc_testnet_get_mempool_info Read 67 1.9%
eth_lookup_address Read 66 1.9%
btc_get_mempool_info Read 64 1.8%
eth_get_balance Read 57 1.6%
mezo_get_balance Read 57 1.6%
eth_gas_price Read 42 1.2%
mezo_gas_price Read 42 1.2%

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

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

Grant scopeDefinition costReduction
All 37 tools (no gateway) 3,493 tokens
3 granted tools ~283 tokens −92%
5 granted tools ~472 tokens −86%
10 granted tools ~944 tokens −73%

Boar blockchain MCP (basic) token-cost questions.

How many tokens does the Boar blockchain MCP (basic) MCP server use?+

Its 37 tool definitions total 3,493 tokens — 1.7% 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 Boar blockchain MCP (basic) 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 Boar blockchain MCP (basic)'s token usage?+

Expose fewer tools. A PolicyLayer grant scopes Boar blockchain MCP (basic) 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 283 tokens, a 92% 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 37 catalogued Boar blockchain MCP (basic) tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Boar blockchain MCP (basic) 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.