Ext Ops Panel
Open dashboard
Comparison

Bounty Operator vs HOL Guard

Bounty Operator is an MCP server published by bountyoperator. Marketplaces we read that list it: 1 (Official MCP Registry). HOL Guard is an MCP server published by hashgraph-online. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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 OperatorHOL Guard
Official MCP Registry Listed
Version: 0.9.18
Forks (GitHub): 1
Stars (GitHub): 4
Not marked · First seen
Listed
Version: 3.25.2
Downloads/month (PyPI): 76 527
Downloads/week (PyPI): 10 913
Forks (GitHub): 167
Stars (GitHub): 927
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 HOL Guard
FactBounty OperatorHOL Guard
Marketplaces that list it11
Stars (GitHub) (differs)4 (worse)927 (better)
Forks (GitHub) (differs)1 (worse)167 (better)
Last release (differs)2026-10-15Not published
Where it runs (differs)Remote server (bountyoperator.com/api/mcp)On your machine (hol-guard)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/bountyoperator/bounty-operatorgithub.com/hashgraph-online/hol-guard
Changes in the last 7 days (differs)50
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 3 days 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

Bounty Operator

In its own words, on Official MCP Registry:

Argues against a security finding or a draft bug bounty report before you submit it.

HOL Guard

In its own words, on Official MCP Registry:

Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.

How to run each

Bounty Operator As a remote MCP server

Claude Code
claude mcp add --transport http bounty-operator https://bountyoperator.com/api/mcp --header "Authorization: Bearer <YOUR_TOKEN>" --header "X-Provider-Key: <YOUR_X_PROVIDER_KEY>"

Requires: Authorization header, X-Provider-Key header

HOL Guard As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio hol-guard -- uvx hol-guard mcp serve --stdio

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Bounty Operator 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: Bounty Operator · What it can do: HOL Guard · Compare two other plugins

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