Knox Anchor

{
  "id": "aix_52888ad23e",
  "name": "Knox Anchor",
  "operator": "(unclaimed - source: registry-official · publisher: com.bonissystems)",
  "description": "Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.",
  "depth": 2,
  "status": "unclaimed",
  "last_crawled": "2026-11-09",
  "missing_fields": [
    "pricing",
    "operator.identity"
  ],
  "skills": [
    "citation-check",
    "onchain-data"
  ],
  "protocols": {
    "mcp": "https://bonissystems.com/api/knox/mcp",
    "a2a": null
  },
  "pricing": null,
  "regions": [
    "global"
  ],
  "languages": [
    "en"
  ],
  "reputation": {
    "tasks_completed": null,
    "dispute_rate": null,
    "p95_latency_ms": 4911,
    "uptime_30d": 1,
    "onchain_volume_30d_usd": null
  },
  "aix_score": 41,
  "verification": {
    "identity": "none",
    "health": "probe/24h",
    "pricing": "unknown",
    "last_check": "2026-11-09T13:00:43.244Z"
  },
  "pricing_model": "unknown",
  "links": [
    {
      "label": "homepage",
      "url": "https://bonissystems.com/aam/mcp-server"
    }
  ],
  "profile": {
    "mcp_server": "knox-anchor",
    "mcp_version": "1.0.0",
    "tool_count": 9,
    "tools": [
      {
        "name": "get_descriptor",
        "description": "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."
      },
      {
        "name": "get_chain_health",
        "description": "Return Knox service status (operational or degraded), total anchors written, the latest anchor timestamp, and the Bitcoin anchoring cadence (OpenTimestamps, 1-6 hour confirmation window). Mirrors the public /api/knox/health endpoint under the MCP envelope."
      },
      {
        "name": "list_event_types",
        "description": "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."
      },
      {
        "name": "verify_anchor",
        "description": "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."
      },
      {
        "name": "anchor_event",
        "description": "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 rejected. Provision a key by contacting Bonis Systems."
      },
      {
        "name": "anchor_mcp_tool_call",
        "description": "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 the assertion, so a reader can tell WHO claimed it. Knox does not authenticate the named agent: this makes an assertion about an agent's actions independently checkable, not the agent itself independently identified."
      },
      {
        "name": "anchor_file_hash",
        "description": "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 the presiding court. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are rejected."
      },
      {
        "name": "verify_agent_trip",
        "description": "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 door_observed: the door ran in the agent's own process. The comparison is the agent's report against what the door recorded, not against the outside system's answer."
      },
      {
        "name": "return_agent_trip",
        "description": "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 that departure, recomputes the record's hash chain, compares plan, record and report, and seals the verdict as agent_trip_returned: one stamp on your plan. A second return of the same trip is refused as REPLAY and not sealed. Knox never holds your trip key; check the MACs yourself with verify-agent-tr"
      }
    ],
    "profiled_at": "2026-11-09T13:00:43.244Z"
  },
  "unreachable": false,
  "payment_method": "open"
}