Content Provenance
Server Details
Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-03-26
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one anchors/creates a provenance record, the other verifies an existing one. There is no overlap or ambiguity between them.
Both names use snake_case, but the pattern differs: anchor_creation is noun+gerund while verify_provenance is verb+noun. A more consistent form would be create_anchor and verify_provenance.
Only two tools is thin and borderline for a server, but the narrow domain of create-and-verify makes the count reasonably justified. It falls at the low end of acceptable scoping.
The core workflow—creating and verifying a provenance anchor—is fully covered. Obvious extensions like listing anchors or retrieving the full provenance bundle are missing, but these are minor gaps for the server's stated purpose.
Available Tools
2 toolsanchor_creationAInspect
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.
Inputs: name (required), source (required), contentHash (required), ai, +4 more.
verify_provenanceAInspect
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=.
Inputs: hash (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Stamp or notarize data into a public witnessed transparency log. Proves timing, not truth.
Pay-and-anchor a hash or AI decision log on Cardano (CIP-0190). Non-custodial. MCP-native. Mainnet.
Decode an SSTV audio recording and anchor its fingerprint and image hash to the Knox event chain.
Sign media with C2PA Content Credentials and verify its declared origin.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenancePost-quantum document anchoring for AI agents. Anchor any SHA-256 hash to Algorand mainnet with ML-DSA-65 (NIST FIPS-204) signatures and receive a self-contained proof bundle verifiable offline — decades from now, without trusting any vendor.13 npm1MIT

markovian-mcpofficial
AlicenseAqualityCmaintenanceBitcoin-anchored provenance for AI outputs; enables stamping, verifying, and tracing outputs with offline-verifiable canonical roots.3Apache 2.0- AlicenseNot gradedqualityBmaintenanceEnables creating and verifying permanent, publicly verifiable content provenance stamps via MCP tools.5 npmMIT
- AlicenseAqualityBmaintenanceAppend-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status. A seal proves a record existed at a time, not that its contents are true. Five tools over stdio with npx -y apex-psi-mcp — no account, no key, verification free forever.5458 npm1MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.