Who it is forA developer or researcher deciding which Slim Guard mode suits a large tool catalog and wants local numbers instead of published claims.
The problemChoosing a mode without measurements means guessing how much context each mode saves on a real catalog.
The outcomeLocally generated reports for the task comparison, compression, and stress fixtures that reflect the current build.
What you need first
- A reviewed checkout of the lennney/mcp-slim-guard repository (0.1.1-alpha.2 is not yet published to npm)
- npm to run ci, build, and link the package
- A project directory that already has an MCP configuration
- An upstream MCP server definition you are authorized to use
Steps
- Run
npm ci, thennpm run build, in the reviewed checkout. - Run
npm run bench:task, thennpm run bench:compression. - Run
npm run bench:stressto exercise the 100-tool and 8,000-row fixture. - Run
npm run bench:compression:verifyand read the mode-specific reports it generates.
Prompt for your agent
In the lennney/mcp-slim-guard repo, run the build and the bench:task, bench:compression, and bench:stress scripts, then summarize the generated reports by mode. Verify that the report is produced locally and that you do not cite the older alpha figures as results.
Caveat. The README says the benchmark reports are generated locally and older alpha figures should not be treated as claims for this product line.
Use this in your AI agent
Ask your agent
Using the Deduped MCP, get the setup steps for lennney/mcp-slim-guard and "Measure mode trade-offs on your own MCP setup"
Add Deduped to Claude Code once
claude mcp add --transport http deduped https://dedupedai.com/mcp
Every Monday: the 5 hottest repos and exactly how to use them. Free, one email a week, unsubscribe anytime.
Get them freeShare: X LinkedIn Hacker News Email Copy link
Third-party repos we don't own. AI-written use cases can be wrong. Disclaimer