486 tokens across 2 tools — lean (< 1K). Measured 2026-08-16 under methodology v1.0.
| server (self-reported) | airbnb v0.3.0 |
| status | measured |
| tokenizer | tiktoken / o200k_base |
| launch command | npx -y @openbnb/mcp-server-airbnb |
| 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 | 79c3109b4fa4e4735ba1071cacbd98948c6aba20b70c9a4295a78e84850a81e0 |
| category | community |
| source | https://github.com/openbnb-org/mcp-server-airbnb |
| tool | tokens | share | description | schema |
|---|---|---|---|---|
| airbnb_search | 319 | 65.6% | 16 | 291 |
| airbnb_listing_details | 165 | 34.0% | 15 | 137 |
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.
npx -y mcp-context-cost verify results/airbnb/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.