Home / Token cost / Contracts

The Contracts MCP server costs 15,964 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 25 tools · 15,964 tokens · 8.0% of 200k · 1.6% 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 8.0%
1M WINDOW 1.6%

Corpus context: Contracts ranks #84 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 15,964 tokens go.

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

ToolCategoryTokens% of server
uniswap-hooks Write 2,270 14.2%
cairo-erc721 Write 925 5.8%
solidity-rwa Write 921 5.8%
solidity-stablecoin Write 921 5.8%
solidity-erc20 Write 880 5.5%
cairo-governor Write 841 5.3%
solidity-account Write 820 5.1%
cairo-erc1155 Write 793 5.0%
cairo-erc20 Write 778 4.9%
solidity-governor Write 679 4.3%
solidity-erc721 Write 659 4.1%
cairo-custom Write 529 3.3%
solidity-erc1155 Write 514 3.2%
stellar-non-fungible Write 507 3.2%
stellar-stablecoin Write 479 3.0%
stellar-governor Write 454 2.8%
cairo-vesting Write 451 2.8%
stellar-fungible Write 428 2.7%
cairo-account Execute 414 2.6%
erc7984 Write 375 2.3%
solidity-custom Write 373 2.3%
cairo-multisig Execute 274 1.7%
stylus-erc20 Write 249 1.6%
stylus-erc721 Write 221 1.4%
stylus-erc1155 Write 209 1.3%

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

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

Grant scopeDefinition costReduction
All 25 tools (no gateway) 15,964 tokens
3 granted tools ~1,916 tokens −88%
5 granted tools ~3,193 tokens −80%
10 granted tools ~6,386 tokens −60%

Contracts token-cost questions.

How many tokens does the Contracts MCP server use?+

Its 25 tool definitions total 15,964 tokens — 8.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 Contracts 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 Contracts's token usage?+

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

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

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