Context7
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Description from the maker (original English)
Detect pytest config-leakage that corrupts agent-benchmark grading. Deterministic, no-LLM.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"benchmark-hygiene": {
"command": "uvx",
"args": [
"mcp-benchmark-hygiene"
]
}
}
}Run this in your terminal
claude mcp add benchmark-hygiene -- uvx mcp-benchmark-hygienePaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"benchmark-hygiene": {
"command": "uvx",
"args": [
"mcp-benchmark-hygiene"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"benchmark-hygiene": {
"type": "stdio",
"command": "uvx",
"args": [
"mcp-benchmark-hygiene"
]
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account sudo-ai-git, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
The registry does not list a required key, though some servers ask you to sign in on first use.
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (1.0.1) reached the registry 2 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Context7, Codebase Memory, Exa
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Feeds AI the latest docs for libraries and frameworks before it answers, so code it writes does not use outdated, removed functions.
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
Connect AI agents to Exa for web search, content fetching, and multi-step research.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
mcp-name: io.github.sudo-ai-git/mcp-benchmark-hygiene
Deterministic detection of pytest config-leakage that silently corrupts agent-benchmark / function grading.
No LLM. No network. One question, answered reliably:
*If I run
python -m pytestinside this workspace, will it inherit a
host coverage/abort gate that mis-scores passing code as failed?*
Automated agent-evaluation harnesses often run python -m pytest inside the target's workspace. If that workspace nests under a repo root carrying pytest addopts — e.g.:
[tool.pytest.ini_options]
addopts = "--cov=harness --cov-report=term-missing:skip-covered --cov-fail-under=80"
...pytest resolves that host pyproject.toml as its rootdir, inherits the addopts, and fails on the host's own coverage gate (harness collected at 0% → below threshold → non-zero exit). The harness then records functionally PASSING code as FAILED.
This is exactly the bug documented in [sudo-ai-git/vulcanbench-findings](https://github.com/sudo-ai-git/vulcanbench-findings): VulcanBench's declarative grader mis-scored every functional task as 0.0 for this reason; with -o addopts= neutralizing the leak, the same workspaces passed 10/10.
When a workspace is flagged CORRUPTED, the tool returns the corrected command:
python -m pytest -o addopts= <tests>
-o addopts= strips inherited coverage/abort gates. (Or run the grader from outside the repo root.)
| tool | purpose |
|---|---|
inspect_workspace(path) | full analysis: ini chain, effective addopts, CLEAN/CORRUPTED/UNKNOWN verdict + corrected command |
check_addopts(path) | thin boolean: corrupted + reasons |
summarize(analysis) | one-line actionable summary string |
The analysis walks the workspace directory up to filesystem root, reading pyproject.toml / pytest.ini / tox.ini / setup.cfg in pytest's first-found order, and extracts addopts. Flags:
--cov, --cov-fail-under, --cov-report, --cov-config--maxfail, -x, --strict, --strict-markers, --pdb, --ffOnly gates that change exit codes / abort grading are flagged. A harmless addopts is reported CLEAN with the exact string.
One command (recommended) — installs from the repo, no PyPI token needed:
uv tool install git+https://github.com/sudo-ai-git/mcp-benchmark-hygiene
mcp-benchmark-hygiene # run stdio server mcp-benchmark-hygiene --http --port 8137 # or Streamable HTTP
Or with pipx: pipx install git+https://github.com/sudo-ai-git/mcp-benchmark-hygiene
Direct from source (fallback):
{ "mcpServers": {
"benchmark-hygiene": { "command": "python3", "args": ["/abs/path/to/mcp_server.py"] } }}
Requires the official mcp python package (pip install mcp). The deterministic core (inspect_workspace / check_addopts / summarize) imports and runs with zero dependencies — the mcp package is only needed for the stdio server.
python3 mcp_server.py --http --port 8137 # serves on http://<host>:8137/mcp/
Run with --http to serve over Streamable HTTP (a remote MCP endpoint) instead of stdio. This is the transport smithery mcp publish expects for URL-based publishing — so once a Smithery service token exists, the server deploys as-is.
inspect_workspace(path="/home/runner/vulcanbench/workspace/task-1")
→ { "ok": true, "workspace": "/home/runner/vulcanbench/workspace/task-1", "ini_chain": [{"file": "/home/runner/vulcanbench/pyproject.toml", "addopts": "--cov=harness ... --cov-fail-under=80"}], "effective_addopts": "--cov=harness ... --cov-fail-under=80", "will_corrupt_grading": true, "verdict": "CORRUPTED", "fixed_command": ["python3", "-m", "pytest", "-o", "addopts=", " "], "reasons": ["coverage gate(s) present: ['--cov', '--cov-fail-under']"] }
python3 test_detector.py — 5/5 core detection checks (root gate, nested inheritance, clean, abort gate, pyproject-no-pytest)python3 test_e2e.py — drives the real MCP stdio transport (initialize → tools/call) and asserts CORRUPTED / CLEAN thread through the wireThis is one of three deterministic, no-LLM agent-trust MCP servers by sudo-ai-git:
mcp-skill-sec — pre-install skill/security auditmcp-verify-claim — evidence-gated, honestly-tiered claim reportingmcp-benchmark-hygiene — pytest config-leakage / eval-honesty detection (this repo)Sibling product: mcp-token-saver — token-cost proxy + analyzer for agent conversations (dedupes redundant tokens before they're billed; live-proven 74% cut). Discussion
Also in the family (a free CLI, not an MCP server): harness-audit — deterministic agent-eval / benchmark-grading hygiene audit that catches the same silent config-leakage mis-scoring class. Free lead-magnet; the same verification discipline, zero dependencies, auditable line-by-line.
MIT. Independently derived from the documented VulcanBench #79 finding; no endorsement by or affiliation with morganlinton/VulcanBench implied.
Need this connected to *your* internal system (auth, logging, security-scan pass, hosted)? Open a custom-build request. MIT reference assets are free to use either way.