Ext Ops Panel
Open dashboard
Comparison

Bounty Operator vs Contract Security Scanner

Bounty Operator is a plugin bundle for AI coding tools published by Tradi3. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Contract Security Scanner is an MCP server published by fino-oss. 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
MarketplaceBounty OperatorContract Security Scanner
Community marketplace bountyoperator/bounty-operator Listed
Version: 0.9.12
Forks (GitHub): 1
Stars (GitHub): 4
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.0
Downloads/month (npm): 119
Downloads/week (npm): 16
Forks (GitHub): 0
Stars (GitHub): 0
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

Bounty Operator vs Contract Security Scanner
FactBounty OperatorContract Security Scanner
Marketplaces that list it11
Stars (GitHub) (differs)4 (better)0 (worse)
Forks (GitHub) (differs)1 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Remote server (bountyoperator.com/api/mcp)On your machine (@fino314-oss/contract-scanner-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published1, secrets among them: 1
Parts of the bundle (differs)6Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/bountyoperator/bounty-operatorgithub.com/fino-oss/contract-scanner-mcp
Changes in the last 7 days (differs)20
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)not checked yetno 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

Bounty Operator

In its own words, on Community GitHub marketplaces:

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.

Contract Security Scanner

In its own words, on Official MCP Registry:

Scans Base L2 smart contracts for security risks. Risk score 0-100, detects backdoors & proxies.

How to run each

Bounty Operator As a Claude Code plugin

Claude Code
/plugin marketplace add bountyoperator/bounty-operator
/plugin install bounty-operator@bounty-operator

Contract Security Scanner As a local MCP server: npm package

Claude Code
claude mcp add --env "BASESCAN_API_KEY=<YOUR_BASESCAN_API_KEY>" --transport stdio contract-scanner -- npx -y @fino314-oss/contract-scanner-mcp

Requires: BASESCAN_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

The marketplaces of Bounty Operator publish no settings it asks for, so we do not compare settings.

What it can do: Bounty Operator · What it can do: Contract Security Scanner · 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.

Where the data comes from: how the catalog is built