vibedasher-mcp vs Vibe Shipped
vibedasher-mcp is an MCP server published by JulienGdnr. Marketplaces we read that list it: 1 (PyPI (MCP servers)). Vibe Shipped is an MCP server published by sorindecu. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  Vibe Shipped | |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.9.62 Downloads/month (PyPI): 7 356 Downloads/week (PyPI): 904 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.11.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
| Fact | vibedasher-mcp | Vibe Shipped |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-11-04 (worse) | 2026-11-06 (better) |
| Where it runs (differs) | On your machine (vibedasher-mcp) | Remote server (vibeshipped.io/api/mcp) |
| Transport (differs) | Not stated | 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/juliengdnr/vibedasher | github.com/sorindecu/vibeshipped-agent |
| Changes in the last 7 days (differs) | 5 | 2 |
| First seen (differs) | 2026-10-13 | 2026-10-16 |
| Endpoint at the last check (differs) | no remote endpoint we check | Status out of date: last check 31 h ago returned HTTP 200 |
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
vibedasher-mcp
MCP server for Vibedasher, the home for the dashboards your AI built: your coding agent creates the datasets, writes the dashboard and publishes it to a URL behind your login.
Vibe Shipped
Find the right AI tool or MCP connector for a task; sourced directory of real AI-built apps.
How to run each
vibedasher-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Vibe Shipped As a remote MCP server
claude mcp add --transport http vibeshipped https://vibeshipped.io/api/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Vibe Shipped has a remote endpoint we check. How we check endpoints
Tools each declares
Neither the marketplaces of vibedasher-mcp nor its endpoint list any tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: vibedasher-mcp · What it can do: Vibe Shipped · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.