All servers · Other
Content Provenance
com.bonissystems/content-provenance · v1.0.0
No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-03-26 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 2 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.
Connect
streamable-http · https://bonissystems.com/api/knox/agents/content-provenance/mcp
claude mcp add --transport http content-provenance https://bonissystems.com/api/knox/agents/content-provenance/mcp{
"mcpServers": {
"content-provenance": {
"url": "https://bonissystems.com/api/knox/agents/content-provenance/mcp"
}
}
}Tools as reported by the server
anchor_creationAnchor 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). Reverify_provenanceVerify 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
Website · JSON · Text for agents · Registry updated 2026-06-24