Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle. Connect the official Content Provenance MCP server to Claude, ChatGPT, or Cursor through gate — one gateway URL, no config files, security-checked.
Free to start · No credit card · No hosting needed
Pick your client. Copy, paste, done — or let gate handle sign-ins and policies for you.
claude mcp add --transport http content-provenance https://bonissystems.com/api/knox/agents/content-provenance/mcpRun in your terminal, then restart Claude Code.
Content Provenance · https://bonissystems.com/api/knox/agents/content-provenance/mcp
Real prompts you can type the moment it's connected — no setup, no docs to read.
“Use “anchor_creation”: Anchor any creation event to the Knox event chain and return a self-authenticating provenance bundle. Three creation modes are supported: hu.”
“Use “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 a.”
Every server in the gate directory has to pass the same four checks before your AI can touch it. Here's how Content Provenance holds up.
Operated by Content Provenance (bonissystems.com) at its documented MCP endpoint — not a third-party mirror or community re-host.
This server only exposes public data — no account and no credentials are involved when you connect.
gate checks every tool for prompt injection, hidden instructions, data-exfiltration hints, and over-broad permissions before the server is available through your gateway.
If Content Provenance adds or changes tools later, gate re-scans and alerts you — before your AI acts on the change.
Add one gateway URL to Claude, ChatGPT, or any MCP client. One-time setup, about two minutes.
Choose Content Provenance in the gate directory. No sign-in needed.
Content Provenance's tools are live in every AI client you've connected — with rules and logging built in.
Free to start · No credit card · No hosting needed
Fetched live from the official endpoint and re-checked daily by gate — not marketing copy.
anchor_creation — Anchor any creation event to the Knox event chain and return a self-authenticating provenance bundle. Three creation modes are supported: hu
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 a
https://bonissystems.com/api/knox/agents/content-provenance/mcpYes — Content Provenance operates its own remote MCP server at bonissystems.com. gate connects you to that official endpoint and adds security scanning, per-tool access rules, and an activity log on top.
Add gate's gateway URL to your AI client once, then pick Content Provenance in the directory. No account or sign-in is needed. From then on, Content Provenance's tools are available in every client you've connected to gate.
No. Content Provenance runs the server, and gate is fully managed. You just connect one URL — there's nothing to install, deploy, or maintain.
It's the vendor's official endpoint, and gate scans its tools for prompt injection and hidden instructions before it goes live, re-checks it whenever it changes, and lets you allow, block, or require approval for every single tool.
Yes — you can get started with gate for free and connect Content Provenance in minutes. No credit card required.
Every server below works through the same gateway URL — connect once, add tools anytime.
Set up Content Provenance in: Claude · Claude Code · ChatGPT · Cursor · VS Code
One URL. All MCPs. Full control. Free to start.
Get started free