Knox Anchor

not graded

Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.

About this server

com.bonissystems/knox-anchor is a Bitcoin-anchored tamper-evident audit-permanence layer for AI agents shaped for FRE 902(13)/(14). It uses streamable-http transport. Tools include get_descriptor, get_chain_health, list_event_types, verify_anchor, anchor_event, anchor_mcp_tool_call, anchor_file_hash and verify_agent_trip.

Categories: crypto

Remote URL: https://bonissystems.com/api/knox/mcp

Repository:

Transport: streamable-http

First seen: 2026-10-17T23:06:01 Last seen: 2026-10-18T08:40:05

30-day uptime: 1.0%

Verified data

Not yet checked — owners can claim this listing to enable price-accuracy checks

Tools

Name	Description	Input keys
get_descriptor	Return the Knox MCP server self-description: operator, USPTO patent reference, jurisdiction, available tools, and links to the public AAM (Agent Audit and Management) documentation surface.
get_chain_health	Return Knox service health: process uptime, database latency, total anchors written, latest anchor timestamp, and the Bitcoin anchor SLA target (OpenTimestamps interval, 1-6 hour confirmation window). Mirrors the public /api/knox/health endpoint under the MCP envelope.
list_event_types	Return the canonical Knox event-type taxonomy. Each event type is a citation token for federal-grade audit; the registry expands monotonically and is itself anchored on every expansion.
verify_anchor	Given a SHA-256 anchor hash (64 hex chars), return the anchor record, chain link validity (predecessor present and matched), event type, sequence number, and verify URL. Public — no authentication required.	hash
anchor_event	Anchor a generic agent action to the Knox chain. Accepts any event_type from the canonical taxonomy plus a payload object. Returns the anchor sequence, payload hash, predecessor hash, timestamp, and verify URL. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are re	event_type, payload
anchor_mcp_tool_call	Convenience anchor for the AAM Model Context Protocol theater. Records an `agent_mcp_tool_call` event with structured tool-call metadata (server URL, tool name, argument digest, asserted agent identity, response digest). The record is sealed with a commitment to the authenticated principal that made	agent_identity, arguments_digest, outcome, response_digest, server_url, tool_name
anchor_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 transmitted — the caller computes the hash and only the digest + filename + size + MIME type are anchored. Admissibility in any matter remains a determination of	filename, hash, mime_type, size_bytes
verify_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 verdict (LINES_UP or MISMATCH), the finding classes, the door head, when it was sealed, and the Bitcoin status of its hourly batch. Public, no key. The witness is	hash, trip_id
return_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 trip nonce and the agent's report. The trip's departure must already be sealed under the same key as agent_trip_departed. Knox checks the plan and nonce against th	departure_seal, door_head, flow, nonce, observations, plan, report

Issues

No issues found

Install

claude mcp add --transport http knox-anchor https://bonissystems.com/api/knox/mcp

{
  "mcpServers": {
    "knox-anchor": {
      "type": "http",
      "url": "https://bonissystems.com/api/knox/mcp"
    }
  }
}

[![FinzData Hub](https://data.finzdata.com/directory/badge/com-bonissystems-knox-anchor.svg)](https://data.finzdata.com/directory/com-bonissystems-knox-anchor)