io.github.RudrenduPaul/agent-eval vs MCP Task Orchestrator
io.github.RudrenduPaul/agent-eval is an MCP server published by RudrenduPaul. Marketplaces we read that list it: 1 (Official MCP Registry). MCP Task Orchestrator is an MCP server published by jpicklyk. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-23. 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.RudrenduPaul/agent-eval |  MCP Task Orchestrator |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.8 Downloads/month (PyPI): 180 Downloads/week (PyPI): 57 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 3.16.0 Forks (GitHub): 25 Stars (GitHub): 209 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:eab0bb62611a Forks (GitHub): 25 Stars (GitHub): 209 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.RudrenduPaul/agent-eval | MCP Task Orchestrator |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 209 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 25 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (agent-regress-cli) | On your machine (ghcr.io/jpicklyk/task-orchestrator:3.16.0) |
| Transport | stdio | stdio |
| Tools it declares (differs) | Not published | 42 |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/rudrendupaul/agent-eval | github.com/jpicklyk/task-orchestrator |
| 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.RudrenduPaul/agent-eval
Statistical regression testing for LLM agents: p-value, effect size, and CI on behavior change.
MCP Task Orchestrator
Server-enforced workflow discipline for AI agents: work items, dependency graphs, quality gates
How to run each
io.github.RudrenduPaul/agent-eval As a local MCP server: PyPI package
claude mcp add --transport stdio agent-eval -- uvx --from agent-regress-cli agent-regress-cli agent-regress-mcpMCP Task Orchestrator As a local MCP server: Docker image
claude mcp add --transport stdio task-orchestrator -- docker run -i --rm -v mcp-task-data:/app/data ghcr.io/jpicklyk/task-orchestrator:3.16.0Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of io.github.RudrenduPaul/agent-eval publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.RudrenduPaul/agent-eval publish no settings it asks for, so we do not compare settings.
What it can do: io.github.RudrenduPaul/agent-eval · What it can do: MCP Task Orchestrator · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.