// MCP TOKEN COST

The VaultPilot MCP server costs 82,778 tokens before the first call.

Every request your agent makes carries every tool definition this server exposes — context your code, documents and conversation can't use, mostly for tools the agent never calls. You don't need them all in the window, and you don't have to pay for them.

QUICK ANSWER The VaultPilot MCP MCP server's 189 tool definitions consume 82,778 tokens — 41% of a 200k context window, and 44× the median MCP server (1,900 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS tiktoken o200k_base · rank #5 of 3,165 measured servers · refreshed every build Method →

// CONTEXT WINDOW SHARE

What that costs 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 41%

1M WINDOW 8.3%

Corpus context: VaultPilot ranks #5 of 3,165 measured MCP servers by definition cost. The median is 1,900 tokens, p90 is 7,952, and the heaviest (Fusionauth) is 183,337 — 92% of a 200k window on its own. New to this? See MCP token cost and context window in the glossary.

Token cost is one axis. See the risk picture across your whole stack →

// PER-TOOL BREAKDOWN

Where the 82,778 tokens go.

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

Tool	Category	Tokens	% of server
prepare_swap	Destructive	1,909	2.3%
get_swap_quote	Read	1,661	2.0%
prepare_custom_call	Execute	1,451	1.8%
get_portfolio_summary	Read	1,292	1.6%
prepare_curve_swap	Execute	1,212	1.5%
prepare_btc_send	Write	1,085	1.3%
prepare_sunswap_swap	Destructive	1,079	1.3%
send_transaction	Write	1,072	1.3%
prepare_uniswap_v3_mint	Destructive	1,058	1.3%
prepare_tron_lifi_swap	Destructive	982	1.2%
build_incident_report	Execute	915	1.1%
get_nft_portfolio	Read	906	1.1%
prepare_btc_lifi_swap	Destructive	891	1.1%
register_btc_multisig_wallet	Write	876	1.1%
add_contact	Write	861	1.0%
explain_tx	Write	822	1.0%
get_transaction_history	Read	812	1.0%
compare_yields	Read	788	1.0%
get_solana_swap_quote	Read	757	0.9%
prepare_uniswap_swap	Destructive	743	0.9%
prepare_uniswap_v3_increase_liquidity	Execute	742	0.9%
prepare_uniswap_v3_rebalance	Execute	735	0.9%
get_daily_briefing	Read	733	0.9%
prepare_solana_lifi_swap	Execute	730	0.9%
get_portfolio_diff	Read	722	0.9%
get_pnl_summary	Read	718	0.9%
list_solana_validators	Read	709	0.9%
read_contract	Read	702	0.8%
get_transaction_status	Read	698	0.8%
prepare_tron_trc20_approve	Write	695	0.8%
prepare_token_approve	Write	694	0.8%
share_strategy	Read	683	0.8%
prepare_litecoin_native_send	Write	667	0.8%
prepare_curve_add_liquidity	Write	662	0.8%
set_demo_wallet	Write	660	0.8%
get_ledger_status	Read	659	0.8%
prepare_solana_spl_send	Write	651	0.8%
prepare_solana_native_send	Write	644	0.8%
prepare_btc_rbf_bump	Destructive	634	0.8%
generate_readonly_link	Write	624	0.8%
prepare_btc_multisig_send	Write	620	0.7%
get_token_allowances	Read	603	0.7%
get_coin_price	Read	602	0.7%
get_contract_abi	Read	590	0.7%
get_vaultpilot_config_status	Read	590	0.7%
pair_ledger_btc	Read	581	0.7%
get_nft_listings	Read	570	0.7%
sign_message_btc	Destructive	561	0.7%
get_market_incident_status	Read	550	0.7%
prepare_uniswap_v3_decrease_liquidity	Execute	514	0.6%
prepare_marginfi_init	Destructive	507	0.6%
resolve_token	Write	507	0.6%
pair_ledger_ltc	Read	500	0.6%
prepare_marginfi_supply	Execute	495	0.6%
prepare_revoke_approval	Destructive	484	0.6%
prepare_native_stake_delegate	Execute	483	0.6%
exit_demo_mode	Execute	482	0.6%
preview_send	Write	471	0.6%
prepare_morpho_supply	Execute	469	0.6%
request_capability	Destructive	467	0.6%
prepare_safe_tx_propose	Read	466	0.6%
prepare_tron_token_send	Write	465	0.6%
rescan_ltc_account	Execute	462	0.6%
rescan_btc_account	Execute	461	0.6%
prepare_marginfi_withdraw	Financial	459	0.6%
set_etherscan_api_key	Write	442	0.5%
simulate_transaction	Execute	427	0.5%
prepare_marginfi_repay	Execute	418	0.5%
prepare_tron_vote	Write	417	0.5%
set_helius_api_key	Write	412	0.5%
sign_btc_multisig_psbt	Read	411	0.5%
prepare_compound_supply	Execute	409	0.5%
prepare_jito_stake	Destructive	406	0.5%
prepare_marginfi_borrow	Destructive	406	0.5%
get_token_balance	Read	406	0.5%
prepare_solana_swap	Destructive	404	0.5%
get_demo_wallet	Read	400	0.5%
preview_solana_send	Write	400	0.5%
get_protocol_risk_score	Read	397	0.5%
verify_tx_decode	Read	392	0.5%
prepare_kamino_supply	Execute	390	0.5%
prepare_native_stake_withdraw	Financial	380	0.5%
prepare_morpho_repay	Execute	378	0.5%
prepare_morpho_withdraw_collateral	Financial	376	0.5%
prepare_morpho_supply_collateral	Execute	375	0.5%
get_btc_account_balance	Read	372	0.4%
get_morpho_positions	Read	372	0.4%
list_tron_witnesses	Read	370	0.4%
verify_ledger_live_codesign	Read	367	0.4%
prepare_weth_unwrap	Destructive	352	0.4%
prepare_compound_repay	Execute	351	0.4%
prepare_safe_tx_execute	Execute	351	0.4%
pair_ledger_solana	Read	350	0.4%
pair_ledger_tron	Read	349	0.4%
get_update_command	Read	348	0.4%
prepare_solana_nonce_init	Write	345	0.4%
prepare_tron_freeze	Execute	342	0.4%
get_verification_artifact	Read	342	0.4%
get_health_alerts	Read	340	0.4%
prepare_compound_borrow	Execute	333	0.4%
prepare_marinade_unstake_immediate	Execute	328	0.4%
simulate_position_change	Read	328	0.4%
prepare_aave_repay	Execute	326	0.4%
prepare_marinade_stake	Destructive	325	0.4%
prepare_aave_supply	Execute	324	0.4%
get_token_price	Read	322	0.4%
prepare_kamino_borrow	Execute	318	0.4%
prepare_tron_unfreeze	Execute	317	0.4%
prepare_native_stake_deactivate	Execute	316	0.4%
get_tron_staking	Read	316	0.4%
prepare_uniswap_v3_collect	Execute	313	0.4%
prepare_compound_withdraw	Financial	309	0.4%
list_contacts	Read	308	0.4%
sign_message_ltc	Destructive	307	0.4%
get_solana_staking_positions	Read	307	0.4%
finalize_btc_psbt	Financial	302	0.4%
get_safe_positions	Read	298	0.4%
get_nft_history	Read	297	0.4%
submit_safe_tx_signature	Write	297	0.4%
prepare_kamino_withdraw	Financial	296	0.4%
prepare_morpho_withdraw	Financial	296	0.4%
combine_btc_psbts	Destructive	294	0.4%
prepare_uniswap_v3_burn	Destructive	294	0.4%
remove_contact	Destructive	292	0.4%
verify_ledger_firmware	Read	292	0.4%
import_strategy	Write	286	0.3%
prepare_kamino_repay	Destructive	283	0.3%
get_solana_setup_status	Read	283	0.3%
prepare_morpho_borrow	Execute	282	0.3%
get_compound_market_info	Read	279	0.3%
prepare_token_send	Write	279	0.3%
check_permission_risks	Read	278	0.3%
get_ledger_device_info	Read	274	0.3%
get_btc_multisig_balance	Read	273	0.3%
prepare_kamino_init_user	Destructive	271	0.3%
check_contract_security	Read	265	0.3%
prepare_tron_native_send	Write	265	0.3%
prepare_lido_wrap	Execute	263	0.3%
prepare_eigenlayer_deposit	Financial	261	0.3%
get_curve_positions	Read	258	0.3%
prepare_safe_tx_approve	Write	257	0.3%
get_kamino_positions	Read	255	0.3%
get_compound_positions	Read	253	0.3%
get_nft_collection	Read	249	0.3%
get_btc_tx_history	Read	247	0.3%
get_marginfi_positions	Read	247	0.3%
prepare_rocketpool_unstake	Execute	245	0.3%
get_ltc_balance	Read	245	0.3%
unregister_btc_multisig_wallet	Destructive	243	0.3%
estimate_staking_yield	Read	242	0.3%
prepare_tron_withdraw_expire_unfreeze	Financial	240	0.3%
get_btc_blocks_recent	Read	239	0.3%
verify_contacts	Read	238	0.3%
prepare_lido_unstake	Execute	234	0.3%
get_btc_block_stats	Read	233	0.3%
import_readonly_token	Write	229	0.3%
get_marginfi_diagnostics	Read	227	0.3%
prepare_solana_nonce_close	Write	225	0.3%
prepare_aave_borrow	Execute	223	0.3%
get_btc_balance	Read	223	0.3%
verify_ledger_attestation	Read	221	0.3%
get_tx_verification	Read	219	0.3%
get_btc_balances	Read	217	0.3%
prepare_aave_withdraw	Financial	216	0.3%
prepare_rocketpool_stake	Execute	214	0.3%
get_btc_multisig_utxos	Read	212	0.3%
prepare_native_send	Write	199	0.2%
revoke_readonly_invite	Destructive	198	0.2%
prepare_tron_claim_rewards	Execute	198	0.2%
get_btc_block_tip	Read	195	0.2%
get_ltc_blocks_recent	Read	193	0.2%
get_staking_positions	Read	191	0.2%
get_ltc_block_tip	Read	173	0.2%
get_ltc_block_stats	Read	172	0.2%
get_staking_rewards	Read	171	0.2%
list_readonly_invites	Read	169	0.2%
prepare_lido_unwrap	Execute	167	0.2%
get_btc_mempool_summary	Read	163	0.2%
get_btc_chain_tips	Read	160	0.2%
get_token_metadata	Read	159	0.2%
get_btc_fee_estimates	Read	150	0.2%
get_ltc_chain_tips	Read	148	0.2%
reverse_resolve_ens	Write	145	0.2%
prepare_lido_stake	Execute	141	0.2%
get_lending_positions	Read	140	0.2%
get_lp_positions	Read	139	0.2%
pair_ledger_live	Read	95	0.1%
get_ltc_mempool_summary	Read	90	0.1%
resolve_ens_name	Write	84	0.1%

// CUT THE COST

Your agent uses a handful of these tools. It pays for all 189.

You don't need all 189 of those definitions in the window. PolicyLayer is an MCP gateway that sits in front of VaultPilot MCP: only the tools you grant are exposed to the agent, the rest never load. A smaller window means a sharper agent — less noise when it picks a tool — and every request costs less:

Grant scope	Definition cost	Reduction
All 189 tools (no gateway)	82,778 tokens	—
3 granted tools	~1,314 tokens	−98%
5 granted tools	~2,190 tokens	−97%
10 granted tools	~4,380 tokens	−95%

The risk dividend: 34 of these 189 tools are critical-risk (destructive or financial) and cost 16,525 tokens (20% of the definition load). Block them — the recommended starter policy — and you reclaim that context before tuning anything else.

Create a free account and register VaultPilot MCP — nothing to install.
Grant only the tools you use — ungranted definitions never enter the context window.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

CUT VAULTPILOT TOKEN COST →

Instant setup, no code required.

Model your own stack in the token-cost calculator, or see the VaultPilot MCP policy for what a sensible grant looks like.

//FAQ

VaultPilot MCP token-cost questions.

How many tokens does the VaultPilot MCP server use?+

Its 189 tool definitions total 82,778 tokens — 41% 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 VaultPilot MCP 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 VaultPilot MCP's token usage?+

Expose fewer tools. A PolicyLayer grant scopes VaultPilot MCP 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 1,314 tokens, a 98% 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.

// METHOD & REVIEW

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 03-07-2026 from the PolicyLayer scan database over all 189 catalogued VaultPilot MCP tools. Counts refresh with every site build.