Ext Ops Panel
Open dashboard
Comparison

Volcano Guide – volcano alert levels vs DBHub

Volcano Guide – volcano alert levels is an MCP server published by volcano-guide.com. Marketplaces we read that list it: 1 (Official MCP Registry). DBHub is an MCP server published by bytebase. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-23. 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
MarketplaceVolcano Guide – volcano alert levelsDBHub
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 1.5.0
Downloads/month (npm): 178 238
Downloads/week (npm): 40 078
Forks (GitHub): 322
Stars (GitHub): 3 705
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

Volcano Guide – volcano alert levels vs DBHub
FactVolcano Guide – volcano alert levelsDBHub
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub3 705
Forks (GitHub) (differs)No figure on GitHub322
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.volcano-guide.com/mcp)On your machine (@bytebase/dbhub)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published17, secrets among them: 4
Parts of the bundle (differs)Not a bundle3
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/bytebase/dbhub
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)Not responding since 2026-10-21no 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

Volcano Guide – volcano alert levels

In its own words, on Official MCP Registry:

Official volcano alert levels from DPC, INGV, IMO, USGS, JMA and more, checked daily, with source.

DBHub

In its own words, on Official MCP Registry:

Token-efficient database MCP server for PostgreSQL, MySQL, MariaDB, SQL Server, Oracle, SQLite

How to run each

Volcano Guide – volcano alert levels As a remote MCP server

Claude Code
claude mcp add --transport http alert-levels https://mcp.volcano-guide.com/mcp

DBHub As a local MCP server: npm package

Claude Code
claude mcp add --env "DB_PASSWORD=<YOUR_DB_PASSWORD>" --env "DSN=<YOUR_DSN>" --env "SSH_PASSPHRASE=<YOUR_SSH_PASSPHRASE>" --env "SSH_PASSWORD=<YOUR_SSH_PASSWORD>" --transport stdio dbhub -- npx -y @bytebase/dbhub

Requires: DB_PASSWORD (secret), DSN (secret), SSH_PASSPHRASE (secret), SSH_PASSWORD (secret)

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

Only Volcano Guide – volcano alert levels 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

The marketplaces of Volcano Guide – volcano alert levels publish no settings it asks for, so we do not compare settings.

What it can do: Volcano Guide – volcano alert levels · What it can do: DBHub · Compare two other plugins

Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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