pepe vs Testorim
pepe is an MCP server published by omarmhaimdat. Marketplaces we read that list it: 1 (Official MCP Registry). Testorim is an MCP server published by sallar-ba. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  pepe |  Testorim |
|---|---|---|
| Official MCP Registry | Listed Version: 0.52.0 Downloads/month (PyPI): 0 Downloads/week (PyPI): 609 Forks (GitHub): 3 Stars (GitHub): 97 Not marked · First seen |
Listed Version: 0.4.1 Downloads/month (npm): 784 Downloads/week (npm): 20 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 | pepe | Testorim |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 97 | No figure on GitHub |
| Forks (GitHub) (differs) | 3 | No figure on GitHub |
| Last release (differs) | 2026-10-20 | Not published |
| Where it runs (differs) | On your machine (pepe-http) | On your machine (@testorim/cli) |
| Transport | stdio | stdio |
| 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) | github.com/omarmhaimdat/pepe | Not stated |
| Changes in the last 7 days (differs) | 14 | 0 |
| First seen (differs) | 2026-10-12 | 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
pepe
Load-test a URL, ping it by phase, ramp to find the capacity, compare runs: JSON reports, guardrails
Testorim
AI browser tests from your coding agent: a verdict, failing steps, report, video and trace.
How to run each
pepe As a local MCP server: PyPI package
claude mcp add --transport stdio pepe -- uvx pepe-http mcp --max-requests 10000 --max-rate 500 --max-concurrency 64Testorim As a local MCP server: npm package
claude mcp add --env "TESTORIM_API_KEY=<YOUR_TESTORIM_API_KEY>" --transport stdio testorim -- npx -y @testorim/cli mcpRequires: TESTORIM_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 pepe publish no settings it asks for, so we do not compare settings.
What it can do: pepe · What it can do: Testorim · 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.