mcp-context-cost

netlify — context cost

2,831 tokens across 9 tools — light (1–5K). Measured 2026-08-16 under methodology v1.0.

   
server (self-reported) netlify-mcp v1.15.1
status measured
tokenizer tiktoken / o200k_base
launch command npx -y @netlify/mcp
isolation docker · public.ecr.aws/docker/library/node:22-slim · network bridge · network enabled for package fetch; clean FS, no host credentials
env vars supplied none
canonical SHA-256 be8578ef35da6e632f7cee04f664676c4895a1320868eceec1150a55f6c21440
category vendor-official
source https://github.com/netlify/netlify-mcp

Where the tokens are

tool tokens share description schema
netlify-project-services-updater 896 31.6% 37 827
netlify-project-services-reader 349 12.3% 27 291
netlify-extension-services-updater 302 10.7% 19 251
netlify-extension-services-reader 265 9.4% 23 211
netlify-deploy-services-reader 261 9.2% 24 205
netlify-deploy-services-updater 254 9.0% 13 208
netlify-team-services-reader 231 8.2% 21 179
netlify-user-services-reader 147 5.2% 17 99
netlify-coding-rules 124 4.4% 32 61

Each tool is tokenized on its own, so the parts do not sum exactly to the whole: the array adds its own brackets and commas, and the tokenizer merges tokens across object boundaries. The badge number is always the count of the whole array, never a sum of parts.

Re-derive it

npx -y mcp-context-cost verify results/netlify/measurement.json

That re-tokenizes the published capture and checks the count and the hash. If it disagrees with the badge, the badge is wrong — open an issue and it gets corrected.

Badge JSON · All servers · Leaderboard · Methodology