Standing schema
674,249 B → 27,401 B
Measure first, then install
See how much MCP schema your model is carrying on every turn
Paste a tool-schema JSON payload from your own setup. The page stays local, computes exact UTF-8 bytes, compares it with MCP Lens's fixed two-tool surface, and shows whether you are paying a real catalog tax before you install anything.
Tested completion
3/3 vs 3/3
Pilot cost
$0.03072 → $0.00347
No upload. No API call. Parsing and rendering happen in your browser only.
Accepted shapes: an array of tool objects, or an object with
tools, schemas, or
header.tools / request.header.tools.
Ready. Paste your current model-visible tool schemas and run the local calculation.
Detected tools
0
Exact UTF-8 bytes
0 B
MCP Lens surface
2 tools / 1,114 B
Reduction
0%
Your current surface
0 tools / 0 B
MCP Lens component benchmark
2 tools / 1,114 B
Shareable claim boundary
Schema bytes only
Shareable card preview
Share links, Markdown, and exported cards contain only bounded numeric fields and a fixed self-reported label; they never include the schemas you pasted. The numeric check catches accidental edits—it is not a signature or proof that a measurement occurred.
What this measures
- Exact UTF-8 bytes of canonical
JSON.stringify(...)output in your browser. - Detected model-visible tool count in the pasted payload.
- Difference versus MCP Lens's checked-in component benchmark at 1,000 tools: 2 tools and 1,114 bytes.
- A schema-free URL fragment that can reconstruct the self-reported result with an empty textarea.
What this does not claim
- Schema bytes are not tokenizer tokens, provider bills, latency, or task quality.
- The live V4 Flash pilot in the repository is a separate three-task measurement with explicit dates and caveats.
- Shared values are self-reported. Their numeric check is not authentication or independent verification.
- This page never uploads your schemas; share only what you are comfortable publishing.