README: context-cost badge (1,052 tokens, measured) - #3146
Open
athakur3 wants to merge 1 commit into
Open
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
This adds one badge to the README: what Context7's MCP server (
@upstash/context7-mcp)'s tool schemas cost in context tokens — 1,052 tokens across 2 tools (o200k_base over the canonicaltools/listbytes), which is the "light" band, i.e. good news for your users.Where it comes from: it is one of 106 MCP servers measured on a rotation in credential-free Docker. Every number is backed by the raw capture, its SHA-256 and the exact launch command; your page has the per-tool breakdown and the history line: https://athakur3.github.io/mcp-context-cost/servers/context7.html · method: https://github.com/athakur3/mcp-context-cost/blob/main/docs/METHODOLOGY.md
The badge JSON is regenerated each time the server is re-measured (about every six weeks), so it follows your releases, and it links to the measurement rather than to a landing page. Anyone can re-derive the number:
It is appended to the existing badge line. If you'd rather host the badge JSON yourselves, that's a one-line change here. Happy to adjust the placement or close this if it isn't wanted. Disclosure: I maintain mcp-context-cost.