Content Provenance MCP Server

by bonissystems Your server? Claim it

answering

Content Provenance is answering right now. Last checked 1 min ago. It exposes 2 tools.

Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.

Uptime history 47 days of history · worst day 98%

47 days agonow

100.0%

Uptime 24h

92 of 92 checks

Tools

read from the server

277 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 16 September 2026. No other catalogue keeps this.

16 Sep a tool description was rewritten anchor_creation

Content Provenance missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add content-provenance --transport http https://bonissystems.com/api/knox/agents/content-provenance/mcp

~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "content-provenance": {
      "url": "https://bonissystems.com/api/knox/agents/content-provenance/mcp"
    }
  }
}

~/.codex/config.toml

[mcp_servers.content-provenance]
url = "https://bonissystems.com/api/knox/agents/content-provenance/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "content-provenance": {
      "url": "https://bonissystems.com/api/knox/agents/content-provenance/mcp"
    }
  }
}

.vscode/mcp.json

{
  "mcpServers": {
    "content-provenance": {
      "url": "https://bonissystems.com/api/knox/agents/content-provenance/mcp"
    }
  }
}

Available tools 2

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

anchor

anchor_creation

Anchor any creation event to the Knox event chain and return a provenance bundle. Three creation modes are supported: human_original (camera capture, original writing, recording), ai_generated (model + prompt + parameters anchored), and ai_assisted_hybrid (human-AI collaboration with edit chain). Returns the Knox anchor record, a C2PA-aligned envelope, and an FRE 902(13)/(14)-shape affidavit. Bonis Systems anchors what creators present; it does not adjudicate authorship, does not grant copyright, and does not enforce any IP claim. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are rejected.

verify

verify_provenance

Verify an anchored content-provenance record. Given a SHA-256 anchor hash (the payload_hash from a prior anchor_creation call), return the anchor record, predecessor hash, sequence number, and timestamp. Public — no authentication required. The verification path itself is also accessible at GET /api/knox/verify?hash=<hash>.

Endpoints

URL	Transport	State	Latency	Checked
https://bonissystems.com/api/knox/agents/content-provenance/mcp	streamable-http	answering	302 ms	1 min ago

Alternatives to Content Provenance

same job, measured the same way

Knox Anchor

by bonissystems

Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.

7 tools answering

Proof Layer

by world-999-labs

Signed, hash-chained provenance receipts for AI agent actions.

22 installs/wk local only

Srbryant86

by srbryant86

Sign AI output for EU AI Act + FRE 902 compliance, verify content authenticity provenance

30 installs/wk local only

SSTV Decoder

by bonissystems

Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.

2 tools answering

Booking Request

by bonissystems

Self-authenticating booking-request receipt anchored to the Knox chain; never represents a person.

3 tools answering

Agent Receipts

by dropwatchhq

Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.

3 tools answering

three.ws Provenance

by nirholas

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

194 installs/wk local only

Chronoverify

by beeswaxpat

Verify a photo's capture time and provenance: C2PA validation, EXIF/XMP, and pixel forensics.

66 installs/wk local only

Content Provenance — questions

Answers built from our own checks of this server.

What can Content Provenance do?

It exposes 2 tools, read directly from the server on our last check. Among them: anchor_creation, verify_provenance. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Content Provenance working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 277 ms. The bar chart above shows every period we have measured.

How do I connect Content Provenance?

Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Content Provenance need an API key?

No. Content Provenance completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 2 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Content Provenance?

It answers our handshake in 277 ms on average, which is faster than 53% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.