Bounty Operator vs Solana Security Standard
Bounty Operator is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
Bounty Operator is a plugin bundle for AI coding tools published by Tradi3. No marketplace we read lists it any more. Solana Security Standard is an MCP server published by Copenhagen0x. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-22. 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 |  Solana Security Standard | |
|---|---|---|
| Community marketplace bountyoperator/bounty-operator | Removed on 2026-10-19 Version: 0.9.18 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.5.0 Downloads/month (npm): 253 Downloads/week (npm): 79 Forks (GitHub): 4 Stars (GitHub): 38 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 | Bounty Operatorno longer listed · | Solana Security Standard |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 4 | 38 |
| Forks (GitHub) (differs) | 1 | 4 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (bountyoperator.com/api/mcp) | On your machine (@jelleo/solana-security-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 6 | 2 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/bountyoperator/bounty-operator | github.com/copenhagen0x/solana-security-standard |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-13 | 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 Bounty Operator
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
AI security scanner for Solidity + free CC0 dataset of Sherlock audit-competition acceptance rates.
-
AI-powered smart contract security auditor for Claude Code — vuln detection, exploit PoCs, mainnet-fork sims, audit cards, on-chain certificates.
-
Smart-contract security audits for EVM chains and DAML: quote, run and fetch reports.
-
Script-backed, out-of-box auditing workflow for Solidity/EVM repositories. Covers environment bootstrap, vulnerability detection, patch validation, exploit scaffolding, and…
-
MCP security scanner: detect tool poisoning, prompt injection & rug-pulls - 10 OWASP heuristics.
-
Bug bounty triage workflow for HackenProof programs
What each says it does
Bounty Operator
Challenge a draft report, review Solidity or any code for security bugs on your own model, and run the hosted gauntlet through the Bounty Operator MCP server.
Solana Security Standard
Scan Solana/Anchor code against the Solana Security Standard and serve the ruleset to MCP clients.
How to run each
Bounty Operator
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Solana Security Standard As a local MCP server: npm package
claude mcp add --transport stdio solana-security-mcp -- npx -y @jelleo/solana-security-mcpCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: Bounty Operator · What it can do: Solana Security Standard · 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.