io.github.beee003/vynn-mcp vs mcp-debugger
io.github.beee003/vynn-mcp is an MCP server published by beee003. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). mcp-debugger is an MCP server published by debugmcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-17. 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.beee003/vynn-mcp |  mcp-debugger |
|---|---|---|
| Official MCP Registry | Listed Version: 0.1.1 Downloads/month (PyPI): 70 Downloads/week (PyPI): 19 Not marked · First seen |
Listed Version: 0.25.1 Downloads/month (npm): 7 568 Downloads/week (npm): 1 829 Forks (GitHub): 24 Stars (GitHub): 177 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.1.1 Forks (GitHub): 0 Stars (GitHub): 0 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.beee003/vynn-mcp | mcp-debugger |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 0 (worse) | 177 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 24 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (vynn-mcp) | On your machine (@debugmcp/mcp-debugger) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/beee003/vynn-mcp | github.com/debugmcp/mcp-debugger |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 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
io.github.beee003/vynn-mcp
Self-improving AI workflows with backtesting, prompt optimization, and scheduling
mcp-debugger
Step-through debugging for AI agents: breakpoints, stepping and live variables in nine languages
How to run each
io.github.beee003/vynn-mcp As a local MCP server: PyPI package
claude mcp add --transport stdio vynn-mcp -- uvx vynn-mcpmcp-debugger As a local MCP server: npm package
claude mcp add --transport stdio mcp-debugger -- npx -y @debugmcp/mcp-debugger stdioCommands 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: io.github.beee003/vynn-mcp · What it can do: mcp-debugger · 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.