ZEAM :: Prism vs web3agent
ZEAM :: Prism is an MCP server published by zeamprism.com. Marketplaces we read that list it: 1 (Official MCP Registry). web3agent is an MCP server published by Apegurus. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
| Marketplace |  ZEAM :: Prism |   web3agent |
|---|---|---|
| Official MCP Registry | Listed Version: 1.4.0 No figure published Not marked · First seen |
Listed Version: 0.6.2 Downloads/month (npm): 237 Downloads/week (npm): 30 Forks (GitHub): 0 Stars (GitHub): 1 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
| Fact | ZEAM :: Prism | web3agent |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 1 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | 2026-10-15 | Not published |
| Where it runs (differs) | Remote server (mcp.zeamprism.com/mcp) | On your machine (web3agent) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 7, secrets among them: 4 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/apegurus/web3agent |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 303 (2 days ago) | no 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
ZEAM :: Prism
A marketplace for AI agents. Tools and data for agents, on one MCP address. No account, no API key.
web3agent
Web3 MCP proxy for AI agents: DeFi swaps, bridges, market data, wallets, and gated writes.
How to run each
ZEAM :: Prism As a remote MCP server
claude mcp add --transport http prism-mcp https://mcp.zeamprism.com/mcpweb3agent As a local MCP server: npm package
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 web3agentRequires: COINGECKO_API_KEY (secret), ETHERSCAN_API_KEY (secret), OWS_PASSPHRASE (secret), ZEROX_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only ZEAM :: Prism 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 ZEAM :: Prism publish no settings it asks for, so we do not compare settings.
What it can do: ZEAM :: Prism · What it can do: web3agent · 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.