Ext Ops Panel
Open dashboard
Comparison

Mirrors vs io.github.hidai25/evalview-mcp

Mirrors is an MCP server published by runmirrors.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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-25. 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

Where each is published
MarketplaceMirrorsio.github.hidai25/evalview-mcp
Official MCP Registry Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.6.0
Downloads/month (PyPI): 2 297
Downloads/week (PyPI): 1 978
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

Mirrors vs io.github.hidai25/evalview-mcp
FactMirrorsio.github.hidai25/evalview-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)0 (worse)140 (better)
Forks (GitHub) (differs)0 (worse)27 (better)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (api.runmirrors.com/mcp)On your machine (evalview)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 2
Parts of the bundle (differs)Not a bundle4
Licence (differs)Not statedApache-2.0
Repository (differs)github.com/ai-singhal/mirrorkit-gogithub.com/hidai25/eval-view
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-14no 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

Mirrors

In its own words, on Official MCP Registry:

AI agent testing: replay real sessions against a rebuilt staging environment to catch regressions.

io.github.hidai25/evalview-mcp

In its own words, on Official MCP Registry:

Regression testing for AI agents. Golden baselines, CI/CD, LangGraph, CrewAI, OpenAI, Claude.

How to run each

Mirrors As a remote MCP server

Claude Code
claude mcp add --transport http mirrors https://api.runmirrors.com/mcp

io.github.hidai25/evalview-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --transport stdio evalview-mcp -- uvx evalview

Requires: OPENAI_API_KEY (secret)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Mirrors has a remote endpoint we check. How we check endpoints

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 Mirrors publish no settings it asks for, so we do not compare settings.

What it can do: Mirrors · What it can do: io.github.hidai25/evalview-mcp · Compare two other plugins

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.

Where the data comes from: how the catalog is built