chaingpt vs com.fidacy/ai-agent-firewall
chaingpt is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
chaingpt is a plugin bundle for AI coding tools published by ChainGPT. No marketplace we read lists it any more. com.fidacy/ai-agent-firewall is an MCP server published by fidacy.com. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-11-13. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.fidacy/ai-agent-firewall | |
|---|---|---|
| Community marketplace chaingpt-org/chaingpt-claude-skill | Removed on 2026-10-22 Version: 1.22.2 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.7.1 Downloads/month (npm): 5 434 Downloads/week (npm): 1 658 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.24.13 Downloads/month (npm): 5 434 Downloads/week (npm): 1 658 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 | chaingptno longer listed · | com.fidacy/ai-agent-firewall |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 7 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-11-03 |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (@fidacy/mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | 3, secrets among them: 1 |
| Hooks it runs (differs) | 1 | Not published |
| Parts of the bundle (differs) | 29 | Not a bundle |
| Licence (differs) | MIT | Apache-2.0 |
| Repository (differs) | github.com/chaingpt-org/chaingpt-claude-skill | github.com/lucaslubi/fidacy-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of chaingpt
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Specialized agents for blockchain development, smart contracts, and Web3 applications
-
Meta-tools for running Claude Code well: audit your permission allowlist, fix local toolchain gaps, analyze usage costs, and prune stale saved memories.
-
DashClaw governance, integration, and platform intelligence: guard checks, approvals, and audit trails for your agents.
-
Use this skill to build natural-language crypto agents, web3 assistants, trading bots, blockchain MCPs, or Claude/Cowork plugins that read and write EVM chain state. Aomi turns…
-
AI skills for building fullstack Aptos dApps — Move smart contracts, TypeScript SDK, wallet integration, security auditing, and gas optimization.
-
vynn-mcp io.github.beee003/vynn-mcp
Self-improving AI workflows with backtesting, prompt optimization, and scheduling
What each says it does
chaingpt
Turn Claude Code into a Web3 engineering co-pilot. Custody-free signing, mainnet safety gates, agent wallet with admin policy.
com.fidacy/ai-agent-firewall
Every agent action watched, every money-moving one gated, every verdict independently verifiable.
How to run each
chaingpt
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.fidacy/ai-agent-firewall As a local MCP server: npm package
claude mcp add --env "FIDACY_ENGINE_API_KEY=<YOUR_FIDACY_ENGINE_API_KEY>" --transport stdio ai-agent-firewall -- npx -y @fidacy/mcpRequires: FIDACY_ENGINE_API_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
Only chaingpt asks for
CHAINGPT_API_KEY (secret)
Only com.fidacy/ai-agent-firewall asks for
FIDACY_ENGINE_API_KEY (secret)FIDACY_MODEFIDACY_OPERATOR_EMAIL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: chaingpt · What it can do: com.fidacy/ai-agent-firewall · Compare two other plugins
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. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.