io.github.Perf-AI/perf-mcp vs retriEVAL
io.github.Perf-AI/perf-mcp is an MCP server published by Perf-AI. Marketplaces we read that list it: 1 (Official MCP Registry). retriEVAL is an MCP server published by hcarrillo001. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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.Perf-AI/perf-mcp |  retriEVAL |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (npm): 130 Downloads/week (npm): 10 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 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.Perf-AI/perf-mcp | retriEVAL |
|---|---|---|
| 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 (perf-mcp) | On your machine (ghcr.io/hcarrillo001/retrieval-mcp:1.0.0) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 4, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/perf-technology/perf-mcp | github.com/hcarrillo001/retrieval-mcp |
| 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.Perf-AI/perf-mcp
Fact-check and fix AI outputs. Hallucination detection, schema validation, auto-repair.
retriEVAL
LLM evals as MCP tools: score outputs for faithfulness, relevancy, and hallucination.
How to run each
io.github.Perf-AI/perf-mcp As a local MCP server: npm package
claude mcp add --env "PERF_API_KEY=<YOUR_PERF_API_KEY>" --transport stdio perf-mcp -- npx -y perf-mcpRequires: PERF_API_KEY (secret)
retriEVAL As a local MCP server: Docker image
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --transport stdio retrieval-mcp -- docker run -i --rm -e ANTHROPIC_API_KEY ghcr.io/hcarrillo001/retrieval-mcp:1.0.0Requires: ANTHROPIC_API_KEY (secret)
Commands 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
Only io.github.Perf-AI/perf-mcp asks for
PERF_API_KEY (secret)
Only retriEVAL asks for
ANTHROPIC_API_KEY (secret)RETRIEVAL_BUDGET_USDRETRIEVAL_JUDGE_BACKENDRETRIEVAL_JUDGE_MODEL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.Perf-AI/perf-mcp · What it can do: retriEVAL · 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.