Home / Token cost / Pubrio

The Pubrio MCP server costs 7,090 tokens before the first call.

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

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

MEASURED FROM SCHEMAS 51 tools · 7,090 tokens · 3.5% 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.5%
1M WINDOW 0.7%

Corpus context: Pubrio ranks #900 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 7,090 tokens go.

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

ToolCategoryTokens% of server
search_companies Read 901 12.7%
find_similar_companies Read 580 8.2%
create_monitor Write 534 7.5%
update_monitor Write 463 6.5%
search_people Read 376 5.3%
search_ads Read 331 4.7%
search_news Read 327 4.6%
search_jobs Read 274 3.9%
reveal_contact Read 123 1.7%
enrich_company Read 120 1.7%
batch_redeem_contacts Read 117 1.7%
list_monitors Read 111 1.6%
lookup_technology Read 111 1.6%
lookup_lookalike Read 108 1.5%
get_monitor_chart Read 106 1.5%
lookup_company Read 101 1.4%
retry_monitor Read 101 1.4%
enrich_person Read 93 1.3%
test_run_monitor Read 91 1.3%
get_monitor_logs Read 89 1.3%
duplicate_monitor Read 82 1.2%
validate_webhook Read 80 1.1%
get_monitor Read 79 1.1%
lookup_person Read 79 1.1%
lookup_person_linkedin Read 79 1.1%
query_batch_redeem Read 79 1.1%
search_vertical_sub_categories Read 77 1.1%
lookup_advertisement Read 73 1.0%
search_technology_categories Read 73 1.0%
lookup_company_linkedin Read 72 1.0%
search_vertical_categories Read 72 1.0%
search_verticals Read 71 1.0%
lookup_job Read 70 1.0%
lookup_monitor_log Read 70 1.0%
lookup_news Read 70 1.0%
search_technologies Read 70 1.0%
reveal_monitor_signature Read 68 1.0%
get_management_levels Read 62 0.9%
delete_monitor Destructive 61 0.9%
get_news_galleries Read 60 0.8%
get_company_sizes Read 59 0.8%
get_department_functions Read 59 0.8%
get_departments Read 59 0.8%
get_news_categories Read 59 0.8%
get_news_languages Read 59 0.8%
get_locations Read 58 0.8%
get_timezones Read 51 0.7%
get_usage Read 48 0.7%
get_profile Read 47 0.7%
get_monitor_stats Read 44 0.6%
get_user Read 43 0.6%

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

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

Grant scopeDefinition costReduction
All 51 tools (no gateway) 7,090 tokens
3 granted tools ~417 tokens −94%
5 granted tools ~695 tokens −90%
10 granted tools ~1,390 tokens −80%

Pubrio token-cost questions.

How many tokens does the Pubrio MCP server use?+

Its 51 tool definitions total 7,090 tokens — 3.5% 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 Pubrio 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 Pubrio's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Pubrio 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 417 tokens, a 94% 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 51 catalogued Pubrio tools. Counts refresh with every site build.

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

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