Lucius MCP vs TestChimp
Lucius MCP is an MCP server published by ivanostanin. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). TestChimp is an MCP server published by testchimp.io. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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 |  Lucius MCP |  TestChimp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.16.6 Downloads/month (PyPI): 1 756 Downloads/week (PyPI): 358 Forks (GitHub): 3 Stars (GitHub): 7 Not marked · First seen |
Listed Version: 0.1.93 Downloads/month (npm): 4 142 Downloads/week (npm): 981 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.16.6 Downloads/month (PyPI): 1 756 Downloads/week (PyPI): 358 Forks (GitHub): 3 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| npm registry (MCP servers) | Not listed | Listed Version: 2.0.2 Downloads/month (npm): 4 142 Downloads/week (npm): 981 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 | Lucius MCP | TestChimp |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 7 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 3 (better) | 0 (worse) |
| Last release (differs) | 2026-10-22 (worse) | 2026-10-23 (better) |
| Where it runs (differs) | On your machine (lucius-mcp) | Remote server or your machine |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 3, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/ivanostanin/lucius-mcp | github.com/testchimp/testchimp-mcp-client |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 7 days 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
Lucius MCP
MCP server for managing Allure TestOps tests, launches, plans, defects, and metadata.
TestChimp
QA platform for agents: coverage signals, in-repo test plans, verified tests and release governance.
How to run each
Lucius MCP As a local MCP server: PyPI package
claude mcp add --env "ALLURE_API_TOKEN=<YOUR_ALLURE_API_TOKEN>" --env "ALLURE_ENDPOINT=<YOUR_ALLURE_ENDPOINT>" --env "ALLURE_PROJECT_ID=<YOUR_ALLURE_PROJECT_ID>" --transport stdio lucius-mcp -- uvx lucius-mcpRequires: ALLURE_API_TOKEN (secret), ALLURE_ENDPOINT, ALLURE_PROJECT_ID
TestChimp As a remote MCP server
claude mcp add --transport http qa https://mcp.testchimp.io/mcpRequires: TESTCHIMP_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only TestChimp 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
Only Lucius MCP asks for
ALLURE_API_TOKEN (secret)ALLURE_ENDPOINTALLURE_PROJECT_ID
Only TestChimp asks for
TESTCHIMP_API_KEY (secret)TESTCHIMP_BACKEND_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Lucius MCP · What it can do: TestChimp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.