Eval Engine API vs VerifyAX
Eval Engine API is an MCP server published by invertedhoologan. Marketplaces we read that list it: 1 (Official MCP Registry). VerifyAX is an MCP server published by verifyax. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  VerifyAX | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.0 No figure published Not marked · First seen |
Listed Version: 0.4.0 Downloads/month (npm): 599 Downloads/week (npm): 32 Forks (GitHub): 0 Stars (GitHub): 1 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 | Eval Engine API | VerifyAX |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (eval.zuluworksai.com/mcp) | Remote server (mcp.verifyax.com/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/verifyax/verifyax-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-16 | Answered with HTTP 400 (38 h ago) |
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
Eval Engine API
Pay-per-call AI evaluation MCP server. Score LLM outputs against benchmark rubrics via Workers AI.
VerifyAX
Evaluate, benchmark, and simulate AI agents on the VerifyAX agent-evaluation platform.
How to run each
Eval Engine API As a remote MCP server
claude mcp add --transport http eval-engine-mcp https://eval.zuluworksai.com/mcpVerifyAX As a remote MCP server
claude mcp add --transport http verifyax https://mcp.verifyax.com/mcpRequires: VERIFYAX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Neither endpoint responded at the last daily 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 Eval Engine API publish no settings it asks for, so we do not compare settings.
What it can do: Eval Engine API · What it can do: VerifyAX · 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.