io.github.dbsectrainer/mcp-eval-runner vs io.github.sudo-ai-git/mcp-benchmark-hygiene
io.github.dbsectrainer/mcp-eval-runner is an MCP server published by dbsectrainer. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.sudo-ai-git/mcp-benchmark-hygiene is an MCP server published by sudo-ai-git. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  io.github.dbsectrainer/mcp-eval-runner |  io.github.sudo-ai-git/mcp-benchmark-hygiene |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Downloads/month (npm): 119 Downloads/week (npm): 12 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (PyPI): 82 Downloads/week (PyPI): 18 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.dbsectrainer/mcp-eval-runner | io.github.sudo-ai-git/mcp-benchmark-hygiene |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) | 0 | 0 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp-eval-runner) | On your machine (mcp-benchmark-hygiene) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/dbsectrainer/mcp-eval-runner | github.com/sudo-ai-git/mcp-benchmark-hygiene |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.dbsectrainer/mcp-eval-runner
A standardized testing harness for MCP servers and agent workflows
io.github.sudo-ai-git/mcp-benchmark-hygiene
Detect pytest config-leakage that corrupts agent-benchmark grading. Deterministic, no-LLM.
How to run each
io.github.dbsectrainer/mcp-eval-runner As a local MCP server: npm package
claude mcp add --env "YOUR_API_KEY=<YOUR_YOUR_API_KEY>" --transport stdio mcp-eval-runner -- npx -y mcp-eval-runnerRequires: YOUR_API_KEY (secret)
io.github.sudo-ai-git/mcp-benchmark-hygiene As a local MCP server: PyPI package
claude mcp add --transport stdio mcp-benchmark-hygiene -- uvx mcp-benchmark-hygieneCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.sudo-ai-git/mcp-benchmark-hygiene publish no settings it asks for, so we do not compare settings.
What it can do: io.github.dbsectrainer/mcp-eval-runner · What it can do: io.github.sudo-ai-git/mcp-benchmark-hygiene · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.