Home / Token cost / Chia Health MCP Server

The Chia Health MCP Server MCP server costs 6,631 tokens before the first call.

Connect Chia Health MCP Server and its 34 tool definitions are loaded into the model's context on every request — 3.3% of a 200k window spent before your agent does anything.

QUICK ANSWER The Chia Health MCP Server MCP server's tool definitions consume 6,631 tokens — 3.5× the median MCP server (1,905 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS 34 tools · 6,631 tokens · 3.3% of 200k · 0.7% 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 3.3%
1M WINDOW 0.7%

Corpus context: Chia Health MCP Server ranks #921 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 6,631 tokens go.

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

ToolCategoryTokens% of server
eligibility_check Read 630 9.5%
intake_questions Read 620 9.4%
consent_submit Write 387 5.8%
order_create Write 326 4.9%
medications_details Read 288 4.3%
auth_start Execute 237 3.6%
order_upload Write 220 3.3%
medications_pricing Read 217 3.3%
checkout_create Write 213 3.2%
consent_text Read 200 3.0%
portal_log_side_effects Read 185 2.8%
intake_submit Write 182 2.7%
checkout_complete Write 170 2.6%
consent_list Read 164 2.5%
medications_list Read 160 2.4%
portal_log_weight Read 160 2.4%
checkout_status Write 147 2.2%
medications_availability Read 143 2.2%
portal_message Write 143 2.2%
auth_verify_otp Read 142 2.1%
provider_respond Read 142 2.1%
portal_support Read 141 2.1%
checkout_update Write 135 2.0%
auth_check_payment Read 134 2.0%
consent_status Read 129 1.9%
intake_status Read 129 1.9%
provider_questions Read 127 1.9%
order_status Read 119 1.8%
order_documents Write 114 1.7%
portal_care_plan Write 114 1.7%
medications_categories Read 110 1.7%
portal_refill Read 105 1.6%
checkout_cancel Write 102 1.5%
auth_resend_otp Read 96 1.4%

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

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

Grant scopeDefinition costReduction
All 34 tools (no gateway) 6,631 tokens
3 granted tools ~585 tokens −91%
5 granted tools ~975 tokens −85%
10 granted tools ~1,950 tokens −71%

Chia Health MCP Server token-cost questions.

How many tokens does the Chia Health MCP Server MCP server use?+

Its 34 tool definitions total 6,631 tokens — 3.3% 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 Chia Health MCP Server 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 Chia Health MCP Server's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Chia Health MCP Server 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 585 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 34 catalogued Chia Health MCP Server tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Chia Health MCP Server 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.