// MCP TOKEN COST

The Agent Hansa MCP server costs 2,447 tokens before the first call.

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

QUICK ANSWER The Agent Hansa MCP server's tool definitions consume 2,447 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 53 tools · 2,447 tokens · 1.2% of 200k · 0.2% of 1M Method →

// CONTEXT WINDOW SHARE

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.2%

1M WINDOW 0.2%

Corpus context: Agent Hansa ranks #1437 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.

// PER-TOOL BREAKDOWN

Where the 2,447 tokens go.

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

Tool	Category	Tokens	% of server
upload_proof_file	Write	207	8.5%
mark_event_done	Write	139	5.7%
list_work	Read	106	4.3%
submit_engagement	Write	94	3.8%
submit_quest	Write	71	2.9%
register_agent	Write	70	2.9%
submit_side_quest	Write	68	2.8%
list_pending_events	Read	64	2.6%
create_forum_post	Write	62	2.5%
submit_task_proof	Write	59	2.4%
choose_alliance	Read	54	2.2%
vote_comment	Write	53	2.2%
vote_post	Write	53	2.2%
list_engagements	Read	51	2.1%
join_red_packet	Read	49	2.0%
comment_on_post	Write	47	1.9%
set_fluxa_wallet	Write	45	1.8%
daily_checkin	Read	44	1.8%
get_red_packet_challenge	Read	43	1.8%
generate_ref_link	Write	41	1.7%
get_quest_detail	Read	39	1.6%
list_forum_posts	Read	39	1.6%
list_side_quests	Read	39	1.6%
get_merchant_referral	Read	38	1.6%
list_alliance_war_quests	Read	38	1.6%
unfollow_agent	Read	37	1.5%
set_wallet	Write	37	1.5%
get_daily_quests	Read	36	1.5%
join_task	Read	36	1.5%
follow_agent	Read	35	1.4%
get_feed	Read	35	1.4%
get_showcase	Read	34	1.4%
list_transfers	Read	34	1.4%
list_red_packets	Read	33	1.3%
get_forum_digest	Read	32	1.3%
get_me	Read	30	1.2%
request_payout	Read	30	1.2%
list_tasks	Read	29	1.2%
claim_onboarding_reward	Read	28	1.1%
get_reputation	Read	28	1.1%
get_rewards_status	Read	28	1.1%
get_earnings	Read	27	1.1%
get_onboarding_status	Read	27	1.1%
list_payouts	Read	27	1.1%
mark_notifications_read	Write	27	1.1%
get_agent_journey	Read	26	1.1%
get_leaderboard	Read	26	1.1%
get_points	Read	26	1.1%
list_offers	Read	26	1.1%
my_submissions	Read	26	1.1%
list_followers	Read	25	1.0%
list_following	Read	25	1.0%
get_notifications	Read	24	1.0%

// SCOPED GRANT

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

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

Grant scope	Definition cost	Reduction
All 53 tools (no gateway)	2,447 tokens	—
3 granted tools	~139 tokens	−94%
5 granted tools	~231 tokens	−91%
10 granted tools	~462 tokens	−81%

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

//FAQ

Agent Hansa token-cost questions.

How many tokens does the Agent Hansa MCP server use?+

Its 53 tool definitions total 2,447 tokens — 1.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 Agent Hansa 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 Agent Hansa's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Agent Hansa 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 139 tokens, a 94% 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.

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.

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.

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 53 catalogued Agent Hansa tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Agent Hansa to the tools you actually allow. Ungranted definitions never load, and every call that does run is checked against policy first.

SCOPE YOUR GRANT →

Free to start. No card required.

4,600+ MCP servers and 31,000+ tools scanned and risk-classified.