Ext Ops Panel
Open dashboard
Comparison

tokensafe vs $THREE Token

tokensafe is a plugin bundle for AI coding tools published by ampactor-labs. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). $THREE Token is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-16. 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
Marketplacetokensafe$THREE Token
Claude Code: claude-plugins-community Listed
Version: 1.0.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.3
Downloads/month (npm): 314
Downloads/week (npm): 63
Forks (GitHub): 64
Stars (GitHub): 237
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

tokensafe vs $THREE Token
Facttokensafe$THREE Token
Marketplaces that list it11
Stars (GitHub) (differs)0 (worse)237 (better)
Forks (GitHub) (differs)0 (worse)64 (better)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (@three-ws/three-token-mcp)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published5, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/ampactor-labs/tokensafegithub.com/nirholas/three.ws
Changes in the last 7 days (differs)40
First seen (differs)2026-10-122026-10-11

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

tokensafe

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

Solana token safety scanner behind x402 micropayments. Checks mint/freeze authority, holder concentration, liquidity, LP locks, honeypot detection, metadata mutability, token age, and Token-2022 extensions. Risk score 0-100 where every point traces to on-chain state. $0.008 request in USDC, no API keys, no accounts. Free lite endpoint and MCP tools included.

$THREE Token

In its own words, on Official MCP Registry:

Price, hold, and burn $THREE on Solana — the first MCP server whose actions burn a token.

How to run each

tokensafe As a Claude Code plugin

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

$THREE Token As a local MCP server: npm package

Claude Code
claude mcp add --env "SOLANA_SECRET_KEY=<YOUR_SOLANA_SECRET_KEY>" --transport stdio three-token-mcp -- npx -y @three-ws/three-token-mcp

Requires: SOLANA_SECRET_KEY (secret)

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

The marketplaces of tokensafe publish no settings it asks for, so we do not compare settings.

What it can do: tokensafe · What it can do: $THREE Token · 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 public marketplace files in GitHub repositories of their authors. 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