iFixAi vs io.github.hidai25/evalview-mcp
iFixAi is a plugin bundle for AI coding tools published by iFixAi. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.hidai25/evalview-mcp is an MCP server published by hidai25. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). 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.hidai25/evalview-mcp | |
|---|---|---|
| Community marketplace ifixai-ai/ifixai-plugin | Listed Version: 0.4.12 No figure published Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.6.0 Downloads/month (PyPI): 2 297 Downloads/week (PyPI): 1 750 Forks (GitHub): 27 Stars (GitHub): 140 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.6.1 Forks (GitHub): 27 Stars (GitHub): 140 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 | iFixAi | io.github.hidai25/evalview-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 140 |
| Forks (GitHub) (differs) | No figure on GitHub | 27 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.ifixai.ai/mcp) | On your machine (evalview) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 2 |
| Parts of the bundle (differs) | 2 | 4 |
| Licence (differs) | Not stated | Apache-2.0 |
| Repository (differs) | github.com/ifixai-ai/ifixai-plugin | github.com/hidai25/eval-view |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-21 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | no remote endpoint we check |
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
iFixAi
Third-party auditing for AI agents. Run by a human or by the agent itself, to answer the most crucial question in the AI Agent Economy. Is the agent doing its actual job?
io.github.hidai25/evalview-mcp
Regression testing for AI agents. Golden baselines, CI/CD, LangGraph, CrewAI, OpenAI, Claude.
How to run each
iFixAi As a Claude Code plugin
/plugin marketplace add ifixai-ai/ifixai-plugin
/plugin install ifixai@ifixaiio.github.hidai25/evalview-mcp As a local MCP server: PyPI package
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio evalview-mcp -- uvx evalviewRequires: OPENAI_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
The marketplaces of iFixAi publish no settings it asks for, so we do not compare settings.
What it can do: iFixAi · What it can do: io.github.hidai25/evalview-mcp · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.