Knox Anchor

com.bonissystemsPublished by bonissystems.comOfficial publisherv1.0.1Updated Oct 24, 2026

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

The publisher's own server: Booking Request

VerifiedStreamable HTTPWeb executableDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

Knox Anchor lets an AI assistant write agent actions, tool calls and file hashes to a Bitcoin-anchored, tamper-evident audit chain and verify the resulting seal

What you can do
Read server self-description, chain health and the canonical event-type taxonomy, and verify an anchor by its SHA-256 hash without a key. Anchor a generic agent action with an event type and payload, returning sequence, payload hash, predecessor hash, timestamp and verify URL. Anchor an MCP tool call with structured metadata such as server URL, tool name, argument and response digests and asserted agent identity. Anchor a SHA-256 file digest with filename, size and MIME type and receive an affidavit shaped for self-authentication. Return and verify customer agent trips, checking the plan and nonce and reporting a verdict of LINES_UP or MISMATCH.
When to use it
Use it when an agent's actions, tool calls or file digests need a durable, independently verifiable audit record, for example for compliance trails or evidence that a file or action existed at a point in time. Read-only verification and health checks are useful for inspecting existing anchors.
Requirements
A remote streamable HTTP endpoint; no local package. Writing anchors (anchor_event, anchor_mcp_tool_call, anchor_file_hash, return_agent_trip) requires a Knox Bearer API key on the Authorization header, which the manifest does not declare. Read tools such as verify_anchor and verify_agent_trip are public. Network access to the provider's service.
Before you install
Writes are permanent audit records on a public chain, so treat anchored payloads and metadata as disclosed and do not include secrets. The API key is a credential; keep it out of shared configurations. Anchoring is not a legal determination of admissibility. File contents are not sent, only the digest and metadata.

Installation

In SourceWeft

  1. Open Knox Anchor in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.bonissystems%2Fknox-anchor/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

Tools

9

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.

Takes no parameters.

get_chain_health

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.

Takes no parameters.

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.

Takes no parameters.

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.

Parametershashrequired

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 rejected. Provision a key by contacting Bonis Systems.

Parameterspayloadrequiredevent_typerequired

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 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.

Parametersoutcomerequiredtool_namerequiredserver_urlrequiredagent_identityrequiredresponse_digestarguments_digestrequired

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 the presiding court. Requires a Knox Bearer API key on the Authorization header — unauthenticated calls are rejected.

Parametershashrequiredfilenamemime_typesize_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 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.

Parametershashtrip_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 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-trip.mjs. Requires a Knox Bearer API key on the Authorization header.

Parametersflowplanrequirednoncerequiredreportrequireddoor_headrequiredobservationsrequireddeparture_sealrequired

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Bonissystems integrations

Booking Request

com.bonissystemsOfficial publisher

A remote MCP server that lets an assistant file booking requests for Bonis Concierge agents and verify the resulting anchored receipt records.

Streamable HTTPWeb executable
Security & Monitoring3 toolsOct 24, 2026

SSTV Decoder

com.bonissystemsOfficial publisher

Remote MCP server that decodes slow-scan television (SSTV) audio into an image and anchors the audio fingerprint and image hash to a Knox event chain.

Streamable HTTPWeb executable
Security & Monitoring2 toolsOct 24, 2026

Registry Expansion Routing

com.bonissystemsOfficial publisher

Lets an assistant look up which public registries the expansion agent would consult for each entity kind.

Streamable HTTPWeb executable
1 toolOct 24, 2026

OFAC SDN Screening

com.bonissystemsOfficial publisher

Lets an assistant screen a name against a dated snapshot of the public U.S. Treasury OFAC SDN list and check the snapshot's provenance and freshness.

Streamable HTTPWeb executable
Finance2 toolsOct 24, 2026

Content Provenance

com.bonissystemsOfficial publisher

A remote MCP server that anchors content-creation events to the Knox event chain and verifies existing provenance records by hash.

Streamable HTTPWeb executable
Knowledge & Memory2 toolsOct 25, 2026