Loadster vs io.github.HomenShum/nodebench
Loadster is an MCP server published by loadster.com. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). io.github.HomenShum/nodebench is an MCP server published by HomenShum. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-15. 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 |  Loadster |  io.github.HomenShum/nodebench |
|---|---|---|
| Official MCP Registry | Listed Version: 1.2.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 2.31.2 Downloads/month (npm): 594 Downloads/week (npm): 119 Forks (GitHub): 3 Stars (GitHub): 15 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 9d6bf19 Forks (GitHub): 3 Stars (GitHub): 15 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 | Loadster | io.github.HomenShum/nodebench |
|---|---|---|
| Marketplaces that list it | 2 | 2 |
| Stars (GitHub) (differs) | 0 (worse) | 15 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 3 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.loadster.com/mcp) | On your machine (nodebench-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 4 | 5 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/loadster/loadster-mcp | github.com/homenshum/nodebench-ai |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | not checked yet | 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
Loadster
Load testing and synthetic monitoring platform: test with Playwright, Browser Bot, or Protocol Bots.
io.github.HomenShum/nodebench
260 MCP tools across 49 domains. AI Flywheel, quality gates, research, web scraping.
How to run each
Loadster As a remote MCP server
claude mcp add --transport http loadster-mcp https://api.loadster.com/mcpio.github.HomenShum/nodebench As a local MCP server: npm package
claude mcp add --transport stdio nodebench -- npx -y nodebench-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Loadster · What it can do: io.github.HomenShum/nodebench · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.