Home / Token cost / Browserous - Instant Browser for Your Agent

The Browserous - Instant Browser for Your Agent MCP server costs 2,554 tokens before the first call.

Connect Browserous - Instant Browser for Your Agent and its 26 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 Browserous - Instant Browser for Your Agent MCP server's tool definitions consume 2,554 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 26 tools · 2,554 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: Browserous - Instant Browser for Your Agent ranks #1404 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,554 tokens go.

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

ToolCategoryTokens% of server
list_network_requests Read 212 8.3%
take_screenshot Read 212 8.3%
list_console_messages Read 208 8.1%
evaluate_script Write 188 7.4%
take_snapshot Read 147 5.8%
emulate Execute 133 5.2%
navigate_page Execute 125 4.9%
performance_analyze_insight Execute 116 4.5%
performance_start_trace Execute 111 4.3%
press_key Write 100 3.9%
fill_form Write 94 3.7%
upload_file Write 77 3.0%
get_network_request Read 75 2.9%
handle_dialog Write 75 2.9%
wait_for Execute 74 2.9%
fill Write 73 2.9%
new_page Execute 68 2.7%
click Write 67 2.6%
get_console_message Read 63 2.5%
drag Write 60 2.3%
close_page Write 59 2.3%
resize_page Write 56 2.2%
select_page Write 54 2.1%
hover Write 45 1.8%
performance_stop_trace Execute 32 1.3%
list_pages Read 30 1.2%

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

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

Grant scopeDefinition costReduction
All 26 tools (no gateway) 2,554 tokens
3 granted tools ~295 tokens −88%
5 granted tools ~491 tokens −81%
10 granted tools ~982 tokens −62%

Browserous - Instant Browser for Your Agent token-cost questions.

How many tokens does the Browserous - Instant Browser for Your Agent MCP server use?+

Its 26 tool definitions total 2,554 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 Browserous - Instant Browser for Your Agent 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 Browserous - Instant Browser for Your Agent's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Browserous - Instant Browser for Your Agent 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 295 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 26 catalogued Browserous - Instant Browser for Your Agent tools. Counts refresh with every site build.

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

A PolicyLayer grant scopes Browserous - Instant Browser for Your Agent 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.