Ext Ops Panel
Open dashboard
Comparison

Astro Docs vs hypervibe

Astro Docs is an MCP server published by docker. Marketplaces we read that list it: 1 (Docker MCP Catalog). hypervibe is a plugin bundle for AI coding tools published by Flavien Chervet. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-26. 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
MarketplaceAstro Docshypervibe
Docker MCP Catalog Listed
Version: not stated
Forks (GitHub): 11
Stars (GitHub): 67
Not marked · First seen
Not listed
Community marketplace flavien-ia/hypervibe-harness Not listed Listed
Version: 3.4.16
Forks (GitHub): 8
Stars (GitHub): 48
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

Astro Docs vs hypervibe
FactAstro Docshypervibe
Marketplaces that list it11
Stars (GitHub) (differs)67 (better)48 (worse)
Forks (GitHub) (differs)11 (better)8 (worse)
Last release (differs)Not published2026-10-23
Where it runs (differs)Remote server (mcp.docs.astro.build/mcp)Remote server (mcp.context7.com/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)Not published2
Parts of the bundle (differs)Not a bundle93
LicenceApache-2.0Apache-2.0
Repository (differs)github.com/withastro/docs-mcpgithub.com/flavien-ia/hypervibe-harness
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-10-18
Endpoint at the last checkResponded 6 days agoResponded 6 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

Astro Docs

In its own words, on Docker MCP Catalog:

Access the latest Astro web framework documentation, guides, and API references.

hypervibe

In its own words, on Community GitHub marketplaces:

Bootstrap a full-stack T3 project (Next.js + tRPC + Drizzle + Tailwind + shadcn/ui) with modular addons for database, auth, payments, email, storage, i18n, analytics, domain, and SEO. Deploys to Vercel with GitHub integration.

How to run each

Astro Docs As a remote MCP server

Claude Code
claude mcp add --transport http astro-docs https://mcp.docs.astro.build/mcp

hypervibe As a Claude Code plugin

Claude Code
/plugin marketplace add flavien-ia/hypervibe-harness
/plugin install hypervibe@hypervibe-harness

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

Both endpoints responded at the last daily check. How we check endpoints

Tools each declares

The marketplaces of hypervibe publish no list of 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: Astro Docs · What it can do: hypervibe · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. 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