Content Provenance vs Fetch SCITT receipts and on-chain anchors for offline verification
Content Provenance is an MCP server published by bonissystems.com. Marketplaces we read that list it: 1 (Official MCP Registry). Fetch SCITT receipts and on-chain anchors for offline verification is an MCP server published by forestrie.dev. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-29. 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
| Marketplace |  Fetch SCITT receipts and on-chain anchors for offline verification | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published Not marked · First seen |
Listed Version: 0.4.1 Downloads/month (npm): 908 Downloads/week (npm): 328 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 0.4.1 Downloads/month (npm): 908 Downloads/week (npm): 328 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
| Fact | Content Provenance | Fetch SCITT receipts and on-chain anchors for offline verification |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-10-20 |
| Where it runs (differs) | Remote server (bonissystems.com/api/knox/agents/content-provenance/mcp) | On your machine (@forestrie/mcp-resolve) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 0 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/forestrie/mcp-resolve |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-27 | no 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
Content Provenance
Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.
Fetch SCITT receipts and on-chain anchors for offline verification
Fetch a SCITT receipt, its genesis and on-chain accumulator for @forestrie/mcp-verify to verify
How to run each
Content Provenance As a remote MCP server
claude mcp add --transport http content-provenance https://bonissystems.com/api/knox/agents/content-provenance/mcpFetch SCITT receipts and on-chain anchors for offline verification As a local MCP server: npm package
claude mcp add --transport stdio resolve -- npx -y @forestrie/mcp-resolveCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Content Provenance 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 Content Provenance publish no settings it asks for, so we do not compare settings.
What it can do: Content Provenance · What it can do: Fetch SCITT receipts and on-chain anchors for offline verification · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.