New Your team’s decisions, in one playbook every coding agent works from. Never answer your agent twice
Home / Token cost / 402cron

The 402cron MCP server costs 2,480 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 402cron MCP server's 16 tool definitions consume 2,480 tokens — 1.2% of a 200k context window, and around the median MCP server (1,728 tokens). A scoped grant exposing only the tools you use cuts that roughly in proportion.

MEASURED FROM SCHEMAS tiktoken o200k_base · rank #6394 of 16,009 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 1.2%
1M WINDOW 0.2%

Corpus context: 402cron ranks #6394 of 16,009 measured MCP servers by definition cost. The median is 1,728 tokens, p90 is 12,557, and the heaviest (AstroWay Astrology API (full catalogue)) is 547,756 — 274% of a 200k window on its own. New to this? See MCP token cost and context window in the glossary.

Where the 2,480 tokens go.

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

ToolCategoryTokens% of server
update_task Write 525 21.2%
create_task Write 490 19.8%
register_destination Write 301 12.1%
verify_destination Read 253 10.2%
run_task_now Execute 104 4.2%
list_tasks Read 101 4.1%
get_docs Read 97 3.9%
delete_task Destructive 90 3.6%
get_task Read 74 3.0%
restore_task Write 74 3.0%
resume_task Write 70 2.8%
delete_destination Destructive 66 2.7%
pause_task Read 66 2.7%
get_pricing Read 65 2.6%
get_service_status Read 60 2.4%
list_destinations Read 44 1.8%

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

You don't need all 16 of those definitions in the window. PolicyLayer is an MCP gateway that sits in front of 402cron: 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 16 tools (no gateway) 2,480 tokens —
3 granted tools ~465 tokens −81%
5 granted tools ~775 tokens −69%
10 granted tools ~1,550 tokens −38%

The risk dividend: 2 of these 16 tools are critical-risk (destructive or financial) and cost 156 tokens (6% of the definition load). Block them — the recommended starter policy — and you reclaim that context before tuning anything else.

  1. Create a free account and register 402cron — 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 402CRON TOKEN COST →

Instant setup, no code required.

402cron token-cost questions.

How many tokens does the 402cron MCP server use?+

Its 16 tool definitions total 2,480 tokens — 1.2% 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 402cron 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 402cron's token usage?+

Expose fewer tools. A PolicyLayer grant scopes 402cron 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 465 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 09-11-2026 from the PolicyLayer scan database over all 16 catalogued 402cron tools. Counts refresh with every site build.

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

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

46,500+ MCP servers and 515,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.