Ext Ops Panel
Open dashboard
Comparison

web3agent vs FortFi Treasury MCP

web3agent is an MCP server published by Apegurus. Marketplaces we read that list it: 1 (Official MCP Registry). FortFi Treasury MCP is an MCP server published by rebelArtists. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. 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
Marketplaceweb3agentFortFi Treasury MCP
Official MCP Registry Listed
Version: 0.6.2
Downloads/month (npm): 199
Downloads/week (npm): 82
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.0.0
No figure published
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

web3agent vs FortFi Treasury MCP
Factweb3agentFortFi Treasury MCP
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (web3agent)Remote server (fortfiapp.com/api/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)7, secrets among them: 4Not published
LicenceNot statedNot stated
Repository (differs)github.com/apegurus/web3agentgithub.com/rebelartists/fortfi
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 39 h ago returned HTTP 402

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

web3agent

In its own words, on Official MCP Registry:

Web3 MCP proxy for AI agents: DeFi swaps, bridges, market data, wallets, and gated writes.

FortFi Treasury MCP

In its own words, on Official MCP Registry:

Policy-gated MCP treasury for AI agents — x402 subscribe, 50+ tools, multi-chain.

How to run each

web3agent As a local MCP server: npm package

Claude Code
claude mcp add --env "COINGECKO_API_KEY=<YOUR_COINGECKO_API_KEY>" --env "ETHERSCAN_API_KEY=<YOUR_ETHERSCAN_API_KEY>" --env "OWS_PASSPHRASE=<YOUR_OWS_PASSPHRASE>" --env "ZEROX_API_KEY=<YOUR_ZEROX_API_KEY>" --transport stdio web3agent -- npx -y web3agent web3agent

Requires: COINGECKO_API_KEY (secret), ETHERSCAN_API_KEY (secret), OWS_PASSPHRASE (secret), ZEROX_API_KEY (secret)

FortFi Treasury MCP As a remote MCP server

Claude Code
claude mcp add --transport http fortfi-treasury-mcp https://fortfiapp.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>"

Requires: Authorization header

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

Only FortFi Treasury MCP 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 FortFi Treasury MCP publish no settings it asks for, so we do not compare settings.

What it can do: web3agent · What it can do: FortFi Treasury MCP · Compare two other plugins

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