Home / Token cost / Dynamic Feed

The Dynamic Feed MCP server costs 8,917 tokens before the first call.

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

QUICK ANSWER The Dynamic Feed MCP server's tool definitions consume 8,917 tokens — 4.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 50 tools · 8,917 tokens · 4.5% of 200k · 0.9% 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 4.5%
1M WINDOW 0.9%

Corpus context: Dynamic Feed ranks #202 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 8,917 tokens go.

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

ToolCategoryTokens% of server
security_advisories Read 329 3.7%
software_version Read 327 3.7%
ai_models Read 305 3.4%
exploited_vulnerabilities Read 304 3.4%
search_ai_models Read 296 3.3%
global_disasters Read 279 3.1%
shipping_status Read 279 3.1%
satellite_position Read 258 2.9%
sports_pulse Execute 256 2.9%
package_health Read 234 2.6%
transit_status Read 232 2.6%
reality_check Read 213 2.4%
earthquakes Read 212 2.4%
whats_changed_since_your_training Read 211 2.4%
wildfires Read 209 2.3%
check_vulnerability Read 203 2.3%
live_flights Read 198 2.2%
water_levels Read 196 2.2%
detect_drift Read 181 2.0%
china_data Read 179 2.0%
weather_forecast Read 179 2.0%
current_weather Read 168 1.9%
natural_events Read 165 1.9%
air_quality Read 161 1.8%
federal_register Write 159 1.8%
service_status Read 158 1.8%
weather_alerts Read 158 1.8%
market_hours Read 153 1.7%
satellites Read 152 1.7%
convert Write 152 1.7%
world_cup Read 150 1.7%
sec_filings Read 149 1.7%
product_recalls Read 148 1.7%
space_weather Read 146 1.6%
sanctions_screen Read 142 1.6%
ai_provider_latency Read 125 1.4%
airport_delays Read 125 1.4%
orbital_data_centers Read 125 1.4%
cite Read 123 1.4%
github_releases Read 121 1.4%
hacker_news Read 120 1.3%
drug_shortages Read 118 1.3%
current_time Read 115 1.3%
drought Read 115 1.3%
treasury_yields Read 115 1.3%
countdown Read 113 1.3%
dns_lookup Read 108 1.2%
carbon_intensity Read 93 1.0%
world_pulse Read 90 1.0%
interest_rates Read 70 0.8%

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

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

Grant scopeDefinition costReduction
All 50 tools (no gateway) 8,917 tokens
3 granted tools ~535 tokens −94%
5 granted tools ~892 tokens −90%
10 granted tools ~1,783 tokens −80%

Dynamic Feed token-cost questions.

How many tokens does the Dynamic Feed MCP server use?+

Its 50 tool definitions total 8,917 tokens — 4.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 Dynamic Feed 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 Dynamic Feed's token usage?+

Expose fewer tools. A PolicyLayer grant scopes Dynamic Feed 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 535 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 50 catalogued Dynamic Feed tools. Counts refresh with every site build.

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

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