io.github.mybolide/mcp-probe-kit vs Socketlist
io.github.mybolide/mcp-probe-kit is an MCP server published by mybolide. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Socketlist is an MCP server published by thunderbid. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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.mybolide/mcp-probe-kit |  Socketlist |
|---|---|---|
| Official MCP Registry | Listed Version: 4.0.0 Downloads/month (npm): 1 495 Downloads/week (npm): 181 Forks (GitHub): 5 Stars (GitHub): 39 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 4.1.1 Downloads/month (npm): 1 495 Downloads/week (npm): 181 Forks (GitHub): 5 Stars (GitHub): 39 Not marked · First seen |
Not listed |
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.mybolide/mcp-probe-kit | Socketlist |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 39 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 5 (better) | 0 (worse) |
| Last release (differs) | 2026-10-14 | Not published |
| Where it runs (differs) | On your machine (mcp-probe-kit) | Remote server (socketlist.pages.dev/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/mybolide/mcp-probe-kit | github.com/thunderbid/socketlist-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 3 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
io.github.mybolide/mcp-probe-kit
Spec-driven dev workflow MCP: start_* orchestration, memory, GitNexus, quality gates.
Socketlist
Search a directory of 800+ open-source MCP servers: find, compare and get install configs.
How to run each
io.github.mybolide/mcp-probe-kit As a local MCP server: npm package
claude mcp add --transport stdio mcp-probe-kit -- npx -y mcp-probe-kitSocketlist As a remote MCP server
claude mcp add --transport http socketlist-mcp https://socketlist.pages.dev/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Socketlist 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: io.github.mybolide/mcp-probe-kit · What it can do: Socketlist · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.