Ext Ops Panel
Open dashboard
Comparison

io.github.acarchidi/agentforge vs io.github.csacanam/hashproof

io.github.acarchidi/agentforge is an MCP server published by acarchidi. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). io.github.csacanam/hashproof is an MCP server published by csacanam. 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

Where each is published
Marketplaceio.github.acarchidi/agentforgeio.github.csacanam/hashproof
Official MCP Registry Listed
Version: 1.5.0
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 0.1.2
Downloads/month (npm): 187
Downloads/week (npm): 44
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

io.github.acarchidi/agentforge vs io.github.csacanam/hashproof
Factio.github.acarchidi/agentforgeio.github.csacanam/hashproof
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)0 (worse)1 (better)
Forks (GitHub)00
Last releaseNot publishedNot published
Where it runs (differs)Remote server (agentforge-taupe.vercel.app/mcp)On your machine (hashproof-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published3, secrets among them: 2
Parts of the bundle (differs)2Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/acarchidi/agentforgegithub.com/csacanam/hashproof
Changes in the last 7 days (differs)20
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 32 h agono 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

In its own words, on Official MCP Registry:

DeFi safety layer for AI agents: wallet safety, token risk, tx decode/simulate. 20 tools.

io.github.csacanam/hashproof

In its own words, on Official MCP Registry:

Issue verifiable credentials from AI agents for $0.10 via x402. On-chain on Celo, IPFS-pinned.

How to run each

io.github.acarchidi/agentforge As a remote MCP server

Claude Code
claude mcp add --transport http agentforge https://agentforge-taupe.vercel.app/mcp

io.github.csacanam/hashproof As a local MCP server: npm package

Claude Code
claude mcp add --env "HASHPROOF_API_KEY=<YOUR_HASHPROOF_API_KEY>" --env "HASHPROOF_WALLET_PRIVATE_KEY=<YOUR_HASHPROOF_WALLET_PRIVATE_KEY>" --transport stdio hashproof -- npx -y hashproof-mcp

Requires: HASHPROOF_API_KEY (secret), HASHPROOF_WALLET_PRIVATE_KEY (secret)

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

The marketplaces of io.github.acarchidi/agentforge publish no settings it asks for, so we do not compare settings.

What it can do: io.github.acarchidi/agentforge · What it can do: io.github.csacanam/hashproof · 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.

Where the data comes from: how the catalog is built