fhevm vs Bug Bounty Intelligence
fhevm is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑16.
fhevm is a plugin bundle for AI coding tools published by 0xE1337. No marketplace we read lists it any more. Bug Bounty Intelligence is an MCP server published by holistis. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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 | ||
|---|---|---|
| Community marketplace 0xe1337/fhevm-skill | Removed on 2026-10-16 Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.3 Forks (GitHub): 3 Stars (GitHub): 9 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 | fhevmno longer listed · | Bug Bounty Intelligence |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 1 | 9 |
| Forks (GitHub) (differs) | 0 | 3 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (wazir-x402.duckdns.org/api/bug-intel) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/0xe1337/fhevm-skill | github.com/holistis/bug-bounty-intelligence-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-15 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (18 h ago) |
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 fhevm
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
AI skills for building fullstack Aptos dApps — Move smart contracts, TypeScript SDK, wallet integration, security auditing, and gas optimization.
-
OpenZeppelin Solidity Contracts
Access to OpenZeppelin Solidity Contracts.
-
Browser Solidity compiler IDE - smart contract development testing deploy
-
Turn Claude Code into a Web3 engineering co-pilot. Custody-free signing, mainnet safety gates, agent wallet with admin policy.
-
Formal verification for Sui Move smart contracts. Write specifications, run the prover, debug verification failures, and understand results.
-
Smart-contract security audits for EVM chains and DAML: quote, run and fetch reports.
What each says it does
fhevm
Grounds AI coding agents in the @fhevm/solidity API surface so they can write confidential smart contracts without hallucinating non-existent functions or producing privacy leaks.
Bug Bounty Intelligence
AI security scanner for Solidity + free CC0 dataset of Sherlock audit-competition acceptance rates.
How to run each
fhevm
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Bug Bounty Intelligence As a remote MCP server
claude mcp add --transport http bug-bounty-intelligence-mcp https://wazir-x402.duckdns.org/api/bug-intel
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Bug Bounty Intelligence 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: fhevm · What it can do: Bug Bounty Intelligence · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.