io.github.OctoPerf/octoperf vs Testorim
io.github.OctoPerf/octoperf is an MCP server published by OctoPerf. 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-21. 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.OctoPerf/octoperf |  Testorim |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 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 | io.github.OctoPerf/octoperf | Testorim |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.octoperf.com/mcp) | On your machine (@testorim/cli) |
| Transport (differs) | Streamable HTTP | 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/octoperf/octoperf-claude-plugins | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 5 days ago, requires a key | no 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
io.github.OctoPerf/octoperf
Drive OctoPerf load testing from any AI agent: import, edit, validate, run scenarios, read metrics.
Testorim
AI browser tests from your coding agent: a verdict, failing steps, report, video and trace.
How to run each
io.github.OctoPerf/octoperf As a remote MCP server
claude mcp add --transport http octoperf https://api.octoperf.com/mcpTestorim 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.
Only io.github.OctoPerf/octoperf 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 io.github.OctoPerf/octoperf publish no settings it asks for, so we do not compare settings.
What it can do: io.github.OctoPerf/octoperf · 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.