mcp-context-cost

postgres-mcp — context cost

8,632 tokens across 9 tools — moderate (5–15K). Measured 2026-08-18 under methodology v1.0.

   
server (self-reported) postgres-mcp v1.29.0
status measured
tokenizer tiktoken / o200k_base
launch command uvx --with "mcp\<2" postgres-mcp --access-mode=restricted
isolation docker · ghcr.io/astral-sh/uv:python3.12-bookworm-slim · network bridge · network enabled for package fetch; clean FS, no host credentials
env vars supplied DATABASE_URI
canonical SHA-256 9bb1e5d26dd377de9dbfac88ffe77663a1169cddf66c6b1f52f57d3a740b0e54
category community
source https://github.com/crystaldba/postgres-mcp

Where the tokens are

tool tokens share description schema
explain_query 1,147 13.3% 23 285
analyze_db_health 1,026 11.9% 128 56
analyze_query_indexes 968 11.2% 16 110
get_top_queries 957 11.1% 21 97
get_object_details 942 10.9% 7 95
analyze_workload_indexes 934 10.8% 11 79
list_objects 916 10.6% 5 73
execute_sql 878 10.2% 6 34
list_schemas 862 10.0% 6 16

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/postgres-mcp/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