Categories › Security › Secrets & identity
Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.
Remote server: your requests and data go to bonissystems.com. Claude Code: claude mcp add --transport http knox-anchor https://bonissystems.com/api/knox/mcp · Claude app: Settings → Connectors → Add custom connector.
The tools this server listed when we connected to it, in its own words.
get_descriptor — Return the Knox MCP server self-description: operator, USPTO patent reference, jurisdiction, available tools, and links to the public AAM (Aget_chain_health — Return Knox service status (operational or degraded), total anchors written, the latest anchor timestamp, and the Bitcoin anchoring cadence list_event_types — Return the canonical Knox event-type taxonomy. Each event type is a citation token for federal-grade audit; the registry expands monotonicalverify_anchor — Given a SHA-256 anchor hash (64 hex chars), return the anchor record, chain link validity (predecessor present and matched), event type, seqanchor_event — Anchor a generic agent action to the Knox chain. Accepts any event_type from the canonical taxonomy plus a payload object. Returns the anchoanchor_mcp_tool_call — Convenience anchor for the AAM Model Context Protocol theater. Records an `agent_mcp_tool_call` event with structured tool-call metadata (seanchor_file_hash — Anchor a SHA-256 file digest to Knox and return an affidavit architected for FRE 902(13)/(14) self-authentication. The file itself is not trverify_agent_trip — THE TICK. Given the returned seal (64 hex) or the trip id of a customer agent trip, return what Knox sealed when the trip came back: the verreturn_agent_trip — THE TICK. Your own door posts a returned trip: the plan, the door's record (targets and keyed commitments, never content), its head, the triNot tested by KitScout yet. When our harness runs it, pros, cons and the tasks we tried appear here, with the date and evidence.