Home / Token cost / Invinoveritas

The Invinoveritas MCP server costs 4,004 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 26 tools · 4,004 tokens · 2.0% of 200k · 0.4% 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.0%
1M WINDOW 0.4%

Corpus context: Invinoveritas ranks #1149 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,004 tokens go.

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

ToolCategoryTokens% of server
review Destructive 530 13.2%
execute Execute 309 7.7%
bounty_submit Write 273 6.8%
browse Read 255 6.4%
decision Read 241 6.0%
markets_act Read 216 5.4%
memory_store Execute 205 5.1%
ledger Read 171 4.3%
signals Read 158 3.9%
message_post Write 155 3.9%
reason Read 125 3.1%
feedback_submit Write 125 3.1%
marketplace_buy Read 116 2.9%
memory_search Read 113 2.8%
memory_get Read 107 2.7%
prove Read 99 2.5%
workspace_list Read 97 2.4%
feedback_vote Write 97 2.4%
feedback_list Read 95 2.4%
memory_delete Destructive 86 2.1%
residence_me Execute 77 1.9%
agent_economy_brief Read 75 1.9%
memory_list Read 73 1.8%
workspace_delete Destructive 71 1.8%
bounty_get Read 71 1.8%
workspace_status Read 64 1.6%

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

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

Grant scopeDefinition costReduction
All 26 tools (no gateway) 4,004 tokens
3 granted tools ~462 tokens −88%
5 granted tools ~770 tokens −81%
10 granted tools ~1,540 tokens −62%

Invinoveritas token-cost questions.

How many tokens does the Invinoveritas MCP server use?+

Its 26 tool definitions total 4,004 tokens — 2.0% 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 Invinoveritas 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 Invinoveritas's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Invinoveritas 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 462 tokens, a 88% 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 26 catalogued Invinoveritas tools. Counts refresh with every site build.

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

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