Home / Token cost / Axint

The Axint MCP server costs 11,766 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 35 tools · 11,766 tokens · 5.9% of 200k · 1.2% 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 5.9%
1M WINDOW 1.2%

Corpus context: Axint ranks #137 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 11,766 tokens go.

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

ToolCategoryTokens% of server
axint.schema.compile Read 1,205 10.2%
axint.workflow.check Execute 831 7.1%
axint.run Execute 818 7.0%
axint.cloud.check Execute 598 5.1%
axint.repair Execute 566 4.8%
axint.feature Write 541 4.6%
axint.suggest Read 492 4.2%
axint.xcode.guard Execute 480 4.1%
axint.feedback.create Write 456 3.9%
axint.xcode.write Write 383 3.3%
axint.scaffold Write 360 3.1%
axint.agent.install Write 313 2.7%
axint.upgrade Execute 310 2.6%
axint.session.start Execute 299 2.5%
axint.compile Read 281 2.4%
axint.agent.advice Execute 267 2.3%
axint.registry.search Write 267 2.3%
axint.project.pack Execute 254 2.2%
axint.agent.claim Execute 250 2.1%
axint.project.index Write 246 2.1%
axint.tokens.ingest Read 230 2.0%
axint.agent.release Execute 222 1.9%
axint.project.syncVersion Write 203 1.7%
axint.fix-packet Execute 201 1.7%
axint.doctor Read 190 1.6%
axint.swift.fix Read 181 1.5%
axint.context.memory Execute 162 1.4%
axint.context.docs Read 161 1.4%
axint.run.status Execute 160 1.4%
axint.status Write 152 1.3%
axint.run.cancel Destructive 149 1.3%
axint.swift.validate Execute 148 1.3%
axint.templates.get Write 145 1.2%
axint.validate Read 143 1.2%
axint.templates.list Read 102 0.9%

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

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

Grant scopeDefinition costReduction
All 35 tools (no gateway) 11,766 tokens
3 granted tools ~1,009 tokens −91%
5 granted tools ~1,681 tokens −86%
10 granted tools ~3,362 tokens −71%

Axint token-cost questions.

How many tokens does the Axint MCP server use?+

Its 35 tool definitions total 11,766 tokens — 5.9% 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 Axint 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 Axint's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Axint 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,009 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 35 catalogued Axint tools. Counts refresh with every site build.

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

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