Ext Ops Panel
Open dashboard
Comparison

QuietProof vs three.ws Provenance

QuietProof is an MCP server published by frankjie3-create. Marketplaces we read that list it: 1 (Official MCP Registry). three.ws Provenance is an MCP server published by nirholas. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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
MarketplaceQuietProofthree.ws Provenance
Official MCP Registry Listed
Version: 0.1.0
No figure published
Not marked · First seen
Listed
Version: 0.1.3
Downloads/month (npm): 168
Downloads/week (npm): 38
Forks (GitHub): 76
Stars (GitHub): 273
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

QuietProof vs three.ws Provenance
FactQuietProofthree.ws Provenance
Marketplaces that list it11
Stars (GitHub) (differs)No figure on GitHub273
Forks (GitHub) (differs)No figure on GitHub76
Last releaseNot publishedNot published
Where it runs (differs)Remote server (quietproof-x402.quietproof-x402.workers.dev/mcp)On your machine (@three-ws/provenance-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published4, secrets among them: 2
LicenceNot statedNot stated
Repository (differs)Not statedgithub.com/nirholas/three.ws
Changes in the last 7 days00
First seen (differs)2026-11-012026-10-11
Endpoint at the last check (differs)Responded 9 h 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

QuietProof

In its own words, on Official MCP Registry:

29 deterministic read-only audits + free discovery tools; paid per call in USDC on Base via x402.

three.ws Provenance

In its own words, on Official MCP Registry:

Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.

How to run each

QuietProof As a remote MCP server

Claude Code
claude mcp add --transport http quietproof https://quietproof-x402.quietproof-x402.workers.dev/mcp

three.ws Provenance As a local MCP server: npm package

Claude Code
claude mcp add --env "THREE_WS_SIGNER_KEY=<YOUR_THREE_WS_SIGNER_KEY>" --env "THREE_WS_TOKEN=<YOUR_THREE_WS_TOKEN>" --transport stdio provenance-mcp -- npx -y @three-ws/provenance-mcp

Requires: THREE_WS_SIGNER_KEY (secret), THREE_WS_TOKEN (secret)

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

Only QuietProof 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

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

What it can do: QuietProof · What it can do: three.ws Provenance · 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