mcpbeat

Content Provenance MCP Server

com.bonissystems/content-provenance
answering

Content Provenance is answering right now. Last checked 4 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 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
2
Tools
read from the server
262 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

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 self-authenticating 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

URLTransportStateLatencyChecked
https://bonissystems.com/api/knox/agents/content-provenance/mcp streamable-http answering 301 ms 4 min ago

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 91 of 91 checks got a reply (100.0%), average response time 262 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 262 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.