Site MCP vs io.github.HomenShum/nodebench
Site MCP is an MCP server published by sitemcp.dev. Marketplaces we read that list it: 1 (Official MCP Registry). 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-18. 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 |  Site MCP |  io.github.HomenShum/nodebench |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published 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 | Site MCP | io.github.HomenShum/nodebench |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 15 |
| Forks (GitHub) (differs) | No figure on GitHub | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (sitemcp.dev/sitemcp.dev) | 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) | Not a bundle | 5 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/homenshum/nodebench-ai |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 4 days ago | 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
Site MCP
Turn any public website into an MCP server for agents to search, read and navigate.
io.github.HomenShum/nodebench
260 MCP tools across 49 domains. AI Flywheel, quality gates, research, web scraping.
How to run each
Site MCP As a remote MCP server
claude mcp add --transport http site-mcp https://sitemcp.dev/sitemcp.devio.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.
Only Site MCP 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Site MCP · 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 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.