Home / Token cost / Sshmcp

The Ssh MCP server costs 2,526 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 21 tools · 2,526 tokens · 1.3% of 200k · 0.3% 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 1.3%
1M WINDOW 0.3%

Corpus context: Ssh ranks #1413 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 2,526 tokens go.

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

ToolCategoryTokens% of server
add_server Write 282 11.2%
update_server Write 273 10.8%
upload_file Write 193 7.6%
upload_directory Write 185 7.3%
add_proxy Write 176 7.0%
download_directory Read 148 5.9%
download_file Read 148 5.9%
read_file Read 145 5.7%
quick_connect Write 135 5.3%
execute Execute 110 4.4%
write_file Write 110 4.4%
rename_server Write 81 3.2%
transfer_status Read 77 3.0%
connect Write 70 2.8%
test_connection Read 67 2.7%
get_server Read 61 2.4%
delete_proxy Destructive 60 2.4%
delete_server Destructive 60 2.4%
disconnect Write 59 2.3%
list_proxies Read 43 1.7%
list_servers Read 43 1.7%

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

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

Grant scopeDefinition costReduction
All 21 tools (no gateway) 2,526 tokens
3 granted tools ~361 tokens −86%
5 granted tools ~601 tokens −76%
10 granted tools ~1,203 tokens −52%

Sshmcp token-cost questions.

How many tokens does the Ssh MCP server use?+

Its 21 tool definitions total 2,526 tokens — 1.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 Sshmcp 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 Sshmcp's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Sshmcp 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 361 tokens, a 86% 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 21 catalogued Sshmcp tools. Counts refresh with every site build.

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

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