Ext Ops Panel
Open dashboard
Comparison

io.github.beee003/vynn-mcp vs io.github.timbassler88/snapstate

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). io.github.timbassler88/snapstate is an MCP server published by timbassler88. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-14. 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

Where each is published
Marketplaceio.github.beee003/vynn-mcpio.github.timbassler88/snapstate
Official MCP Registry Listed
Version: 0.1.1
Downloads/month (PyPI): 70
Downloads/week (PyPI): 19
Not marked · First seen
Listed
Version: 1.0.2
Downloads/month (npm): 76
Downloads/week (npm): 36
Forks (GitHub): 0
Stars (GitHub): 7
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

io.github.beee003/vynn-mcp vs io.github.timbassler88/snapstate
Factio.github.beee003/vynn-mcpio.github.timbassler88/snapstate
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)0 (worse)7 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)On your machine (vynn-mcp)On your machine (snapstate-sdk)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/beee003/vynn-mcpgithub.com/timbassler88/snapstate
Changes in the last 7 days00
First seen2026-10-112026-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

In its own words, on Official MCP Registry:

Self-improving AI workflows with backtesting, prompt optimization, and scheduling

io.github.timbassler88/snapstate

In its own words, on Official MCP Registry:

Persistent state for AI agent workflows. Save, resume, and replay multi-step workflows.

How to run each

io.github.beee003/vynn-mcp As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio vynn-mcp -- uvx vynn-mcp

io.github.timbassler88/snapstate As a local MCP server: npm package

Claude Code
claude mcp add --env "SNAPSTATE_API_KEY=<YOUR_SNAPSTATE_API_KEY>" --env "SNAPSTATE_API_URL=<YOUR_SNAPSTATE_API_URL>" --transport stdio snapstate -- npx -y snapstate-sdk

Requires: SNAPSTATE_API_KEY (secret), SNAPSTATE_API_URL

Commands 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

The marketplaces of io.github.beee003/vynn-mcp publish no settings it asks for, so we do not compare settings.

What it can do: io.github.beee003/vynn-mcp · What it can do: io.github.timbassler88/snapstate · 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.

Where the data comes from: how the catalog is built