Home / Token cost / Thrd

The Thrd MCP server costs 1,388 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 16 tools · 1,388 tokens · 0.7% of 200k · 0.1% 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 0.7%
1M WINDOW 0.1%

Corpus context: Thrd ranks #1888 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 1,388 tokens go.

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

ToolCategoryTokens% of server
thrd.send Read 243 17.5%
thrd.reply Read 191 13.8%
thrd.instant_onboarding Read 136 9.8%
thrd.create_security_ack Write 114 8.2%
thrd.poll_events Read 92 6.6%
thrd.list_threads Read 84 6.1%
thrd.billing_checkout_self Write 74 5.3%
thrd.ack_events Read 73 5.3%
thrd.get_thread_messages Read 69 5.0%
thrd.outbound_status Read 66 4.8%
thrd.message_security Read 65 4.7%
thrd.claim_x_start Execute 39 2.8%
thrd.claim_x_status Read 38 2.7%
thrd.health Read 36 2.6%
thrd.usage Read 35 2.5%
thrd.trust_score Read 33 2.4%

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

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

Grant scopeDefinition costReduction
All 16 tools (no gateway) 1,388 tokens
3 granted tools ~260 tokens −81%
5 granted tools ~434 tokens −69%
10 granted tools ~868 tokens −38%

Thrd token-cost questions.

How many tokens does the Thrd MCP server use?+

Its 16 tool definitions total 1,388 tokens — 0.7% 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 Thrd 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 Thrd's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Thrd 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 260 tokens, a 81% 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 16 catalogued Thrd tools. Counts refresh with every site build.

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

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