Home / Token cost / Moxis

The Moxis MCP server costs 755 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 Moxis MCP server's 11 tool definitions consume 755 tokens — 0.4% of a 200k context window, and below the median MCP server (2,069 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

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

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 0.4%
1M WINDOW 0.1%

Corpus context: Moxis ranks #2604 of 3,354 measured MCP servers by definition cost. The median is 2,069 tokens, p90 is 11,359, and the heaviest (SmartBear MCP) is 137,725 — 69% of a 200k window on its own. New to this? See MCP token cost and context window in the glossary.

Where the 755 tokens go.

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

ToolCategoryTokens% of server
login-instance Write 125 16.6%
set-alias-instance Write 85 11.3%
upload Write 80 10.6%
logout-instance Write 76 10.1%
inbox-count-instance Read 71 9.4%
inbox-overview Read 68 9.0%
list-all-registered-moxis-instances Read 54 7.2%
hello-moxis Read 54 7.2%
inbox-count-all Read 51 6.8%
moxis-help Read 47 6.2%
logout-all Write 44 5.8%

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

You don't need all 11 of those definitions in the window. PolicyLayer is an MCP gateway that sits in front of Moxis: 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 scopeDefinition costReduction
All 11 tools (no gateway) 755 tokens
3 granted tools ~206 tokens −73%
5 granted tools ~343 tokens −55%
10 granted tools ~686 tokens −9%
  1. Create a free account and register Moxis — nothing to install.
  2. Grant only the tools you use — ungranted definitions never enter the context window.
  3. Point your MCP client (Claude, Cursor, anything) at your gateway URL.
CUT MOXIS TOKEN COST →

Instant setup, no code required.

Moxis token-cost questions.

How many tokens does the Moxis MCP server use?+

Its 11 tool definitions total 755 tokens — 0.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 Moxis 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 Moxis's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Moxis 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 206 tokens, a 73% 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 06-07-2026 from the PolicyLayer scan database over all 11 catalogued Moxis tools. Counts refresh with every site build.

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

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

Instant setup, no code required.

43,000+ MCP servers and 220,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.