549 tokens across 7 tools — lean (< 1K). Measured 2026-08-16 under methodology v1.0.
| server (self-reported) | mcp-server/google-maps v0.1.0 |
| status | measured |
| tokenizer | tiktoken / o200k_base |
| launch command | npx -y @modelcontextprotocol/server-google-maps |
| 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 | GOOGLE_MAPS_API_KEY |
| canonical SHA-256 | a88e204db09aa56954e3e041d6a9814aee9ac888fdfc7d5cb47aec1877441986 |
| category | official-reference |
| source | https://github.com/modelcontextprotocol/servers-archived |
| tool | tokens | share | description | schema |
|---|---|---|---|---|
| maps_distance_matrix | 124 | 22.6% | 10 | 102 |
| maps_directions | 99 | 18.0% | 5 | 82 |
| maps_search_places | 95 | 17.3% | 7 | 76 |
| maps_elevation | 78 | 14.2% | 8 | 58 |
| maps_reverse_geocode | 56 | 10.2% | 5 | 38 |
| maps_place_details | 50 | 9.1% | 7 | 31 |
| maps_geocode | 45 | 8.2% | 6 | 27 |
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/google-maps/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.