Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://bonissystems.com/api/knox/agents/content-provenance/mcp2 tools · 314msanchor_creationAnchor 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…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…
| Parameter | Type | Description |
|---|---|---|
| name* | string | Display name for the work (max 256 chars). |
| contentHash* | string | SHA-256 digest of the content as 64 lowercase hex chars. The content itself is not transmitted. |
| contentType | string | MIME type (max 128 chars). |
| sizeBytes | integer | Content size in bytes. |
| source* | string | Creation source. |
| ai | object | AI-generation metadata (required when source = ai_generated). |
| hybrid | object | Hybrid-creation metadata (required when source = ai_assisted_hybrid). |
| human | object | Human-original metadata (optional when source = human_original). |
verify_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 /ap…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 /ap…
| Parameter | Type | Description |
|---|---|---|
| hash* | string | SHA-256 anchor hash (64 lowercase hex chars). |
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Anchor a content-creation event to the Knox chain; returns a C2PA-aligned, FRE 902-shaped bundle.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.