Ext Ops Panel
Open dashboard
Comparison

vulcan vs Undertow market liquidity and exit-cost tools

vulcan is a plugin bundle for AI coding tools published by Ellipsis-Labs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). Undertow market liquidity and exit-cost tools is an MCP server published by beepboop2025. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-22. 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
MarketplacevulcanUndertow market liquidity and exit-cost tools
Claude Code: claude-plugins-community Listed
Version: 0.5.0
Forks (GitHub): 6
Stars (GitHub): 20
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.13.0
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

vulcan vs Undertow market liquidity and exit-cost tools
FactvulcanUndertow market liquidity and exit-cost tools
Marketplaces that list it11
Stars (GitHub) (differs)20 (better)0 (worse)
Forks (GitHub) (differs)6 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (api.seiche.info/undertow/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Parts of the bundle (differs)21Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/ellipsis-labs/vulcan-cligithub.com/beepboop2025/undertow-mcp
Changes in the last 7 days00
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 25 h 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

vulcan

In its own words, on Claude Code: claude-plugins-community:

Agent and human-friendly CLI for trading Phoenix perpetual futures on Solana.

Undertow market liquidity and exit-cost tools

In its own words, on Official MCP Registry:

Dated exit evidence, depth, tiers and gold cash scenarios. No executable quotes or trade authority.

How to run each

vulcan As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install vulcan@claude-community

Undertow market liquidity and exit-cost tools As a remote MCP server

Claude Code
claude mcp add --transport http undertow https://api.seiche.info/undertow/mcp

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

Only Undertow market liquidity and exit-cost tools 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 Undertow market liquidity and exit-cost tools publish no settings it asks for, so we do not compare settings.

What it can do: vulcan · What it can do: Undertow market liquidity and exit-cost tools · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built