Home / Token cost / Axiora

The Axiora MCP server costs 4,798 tokens before the first call.

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

QUICK ANSWER The Axiora MCP server's tool definitions consume 4,798 tokens — 2.5× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 33 tools · 4,798 tokens · 2.4% of 200k · 0.5% 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.4%
1M WINDOW 0.5%

Corpus context: Axiora ranks #1049 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,798 tokens go.

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

ToolCategoryTokens% of server
get_ownership_signals Read 366 7.6%
screen_companies Read 277 5.8%
get_voting_results Read 228 4.8%
get_sections Read 209 4.4%
get_ranking Read 204 4.3%
get_ownership_trajectories Read 184 3.8%
get_timeseries Read 183 3.8%
list_filings Read 175 3.6%
get_capital_allocation_ranking Read 171 3.6%
search_translations Read 171 3.6%
search_companies Read 169 3.5%
get_ownership_movers Read 160 3.3%
get_buybacks Read 144 3.0%
get_shareholdings Read 143 3.0%
get_health_ranking Read 142 3.0%
get_translations Read 134 2.8%
get_board_composition Read 132 2.8%
compare_companies Read 129 2.7%
get_cross_holdings Read 129 2.7%
get_growth Read 124 2.6%
get_financials Read 115 2.4%
get_peers Read 111 2.3%
get_sector_overview Read 110 2.3%
search_companies_batch Read 109 2.3%
get_unwinding_scoreboard Read 102 2.1%
get_capital_allocation Read 100 2.1%
get_health_score Read 100 2.1%
get_company Read 94 2.0%
get_probability_table Read 91 1.9%
get_activist_campaigns Read 86 1.8%
get_filing_calendar Read 76 1.6%
get_coverage Read 67 1.4%
get_documentation Read 63 1.3%

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

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

Grant scopeDefinition costReduction
All 33 tools (no gateway) 4,798 tokens
3 granted tools ~436 tokens −91%
5 granted tools ~727 tokens −85%
10 granted tools ~1,454 tokens −70%

Axiora token-cost questions.

How many tokens does the Axiora MCP server use?+

Its 33 tool definitions total 4,798 tokens — 2.4% 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 Axiora 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 Axiora's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Axiora 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 436 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 33 catalogued Axiora tools. Counts refresh with every site build.

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

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