Ext Ops Panel
Open dashboard
Comparison

phantom-connect vs IronWallet

phantom-connect is a plugin bundle for AI coding tools published by phantom. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). IronWallet is an MCP server published by ironwallet.io. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-15. 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
Marketplacephantom-connectIronWallet
Claude Code: claude-plugins-community Listed
Version: 1.1.0
Forks (GitHub): 11
Stars (GitHub): 18
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.2.1
Downloads/month (npm): 515
Downloads/week (npm): 187
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

phantom-connect vs IronWallet
Factphantom-connectIronWallet
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)18 (better)0 (worse)
Forks (GitHub) (differs)11 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (docs.phantom.com/mcp)On your machine (@ironwallet/mcp-server)
Transport (differs)SSEstdio
Tools it declaresNot publishedNot published
Environment variables it asks for1, secrets among them: 01, secrets among them: 0
Parts of the bundle (differs)156
LicenceMITMIT
Repository (differs)github.com/phantom/phantom-connect-cursor-plugingithub.com/ironwallet/ironwallet-agent-kit
Changes in the last 7 days (differs)02
First seen2026-10-112026-10-11
Endpoint at the last check (differs)not checked yetno 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

phantom-connect

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

Phantom wallet integration for Claude Code - skills for Solana blockchain development, wallet operations, token management, and dApp building with Phantom.

IronWallet

In its own words, on Official MCP Registry:

Non-custodial crypto wallet MCP: check balances, sign and send transfers, and swap tokens locally.

How to run each

phantom-connect As a Claude Code plugin

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

IronWallet As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio ironwallet -- npx -y @ironwallet/mcp-server

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

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only phantom-connect asks for

  • PHANTOM_APP_ID

Only IronWallet asks for

  • IW_READ_ONLY

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: phantom-connect · What it can do: IronWallet · 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. 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