Ext Ops Panel
Open dashboard
Comparison

DejaBars vs io.github.beee003/vynn-mcp

DejaBars is an MCP server published by dejabars.com. Marketplaces we read that list it: 1 (Official MCP Registry). 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). As of our marketplace pass on 2026-11-08. 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
MarketplaceDejaBarsio.github.beee003/vynn-mcp
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 0.1.1
Downloads/month (PyPI): 70
Downloads/week (PyPI): 19
Not marked · First seen
Claude Code: claude-plugins-community Not listed Listed
Version: 0.1.1
Forks (GitHub): 0
Stars (GitHub): 0
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

DejaBars vs io.github.beee003/vynn-mcp
FactDejaBarsio.github.beee003/vynn-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub0
Forks (GitHub) (differs)No figure on GitHub0
Last releaseNot publishedNot published
Where it runs (differs)Remote server (dejabars.com/api/v1/mcp)On your machine (vynn-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)Not a bundle1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/beee003/vynn-mcp
Changes in the last 7 days00
First seen (differs)2026-10-312026-10-11
Endpoint at the last check (differs)Status out of date: last check 2 days ago returned HTTP 406no 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

DejaBars

In its own words, on Official MCP Registry:

Find historical chart-pattern matches across crypto markets from a sketch.

io.github.beee003/vynn-mcp

In its own words, on Official MCP Registry:

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

How to run each

DejaBars As a remote MCP server

Claude Code
claude mcp add --transport http pattern-search https://dejabars.com/api/v1/mcp

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

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

Commands built only from what the marketplaces declare; the full set for every client is on each card.

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