io.github.acarchidi/agentforge vs Crypto Tools Registry
io.github.acarchidi/agentforge is an MCP server published by acarchidi. Marketplaces we read that list it: 1 (Official MCP Registry). Crypto Tools Registry 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-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
| Marketplace |  io.github.acarchidi/agentforge |  Crypto Tools Registry |
|---|---|---|
| Official MCP Registry | Listed Version: 1.5.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 4 Stars (GitHub): 26 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 | io.github.acarchidi/agentforge | Crypto Tools Registry |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 26 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 4 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (agentforge-taupe.vercel.app/mcp) | Not stated |
| Transport (differs) | Streamable HTTP | Not stated |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/acarchidi/agentforge | github.com/nirholas/lyra-registry |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 45 h 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
io.github.acarchidi/agentforge
DeFi safety layer for AI agents: wallet safety, token risk, tx decode/simulate. 20 tools.
Crypto Tools Registry
Registry API for 800+ crypto blockchain DeFi NFT trading tools discovery
How to run each
io.github.acarchidi/agentforge As a remote MCP server
claude mcp add --transport http agentforge https://agentforge-taupe.vercel.app/mcpCrypto Tools Registry
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.acarchidi/agentforge 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
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.acarchidi/agentforge · What it can do: Crypto Tools Registry · Compare two other plugins
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.