Skip to content

Knox Anchor MCP server

com.bonissystems/knox-anchorbonissystems.comstreamable-httpv1.0.1Scanned

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

9 tools: 6 change things and 3 only read.

Tools: 0 delete, 0 irreversible, 6 write, 3 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

6 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Knox Anchor MCP server can do

The Knox Anchor MCP server is published by bonissystems.com, a domain the MCP Registry verified. It has 9 tools. It can create or change data (6 tools: verify_anchor, anchor_event, anchor_mcp_tool_call, anchor_file_hash and 2 more), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 17, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

9 tools

Changes things 6Claude Code: ask
  • anchor_eventAnchor a generic agent action to the Knox chain.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anchor_file_hashAnchor a SHA-256 file digest to Knox and return an affidavit architected for FRE 902(13)/(14) self-authentication.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • anchor_mcp_tool_callConvenience anchor for the AAM Model Context Protocol theater.No findings

    Why it is in this group

    • The name "anchor_mcp_tool_call" says "call": a word for a change.
    Description, as the server wrote it
    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.
  • return_agent_tripTHE TICK.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • verify_agent_tripTHE TICK.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
  • verify_anchorGiven 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.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    Description, as the server wrote it
    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.
Only reads 3Show 3 read-only tools
  • get_chain_healthReturn Knox service status (operational or degraded), total anchors written, the latest anchor timestamp, and the Bitcoin anchoring cadence (OpenTimestamps, 1-6 hour confirmation w…No findings

    Why it is in this group

    • The name "get_chain_health" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • get_descriptorReturn the Knox MCP server self-description: operator, USPTO patent reference, jurisdiction, available tools, and links to the public AAM (Agent Audit and Management) documentation…No findings

    Why it is in this group

    • The name "get_descriptor" says "get": a word for reading.
    Description, as the server wrote it
    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.
  • list_event_typesReturn the canonical Knox event-type taxonomy.No findings

    Why it is in this group

    • The name "list_event_types" says "list": a word for reading.
    Description, as the server wrote it
    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.

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 19:22 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
6
Protocol version
2025-03-26
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 6 tools that change things (6 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://bonissystems.com/api/knox/mcp: tools/list returned 9 tools to an anonymous client, including verify_anchor (write), anchor_event (write), anchor_mcp_tool_call (write), anchor_file_hash (write), verify_agent_trip (write) and 1 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__knox-anchor__get_descriptor",
      "mcp__knox-anchor__get_chain_health",
      "mcp__knox-anchor__list_event_types"
    ],
    "ask": [
      "mcp__knox-anchor__verify_anchor",
      "mcp__knox-anchor__anchor_event",
      "mcp__knox-anchor__anchor_mcp_tool_call",
      "mcp__knox-anchor__anchor_file_hash",
      "mcp__knox-anchor__verify_agent_trip",
      "mcp__knox-anchor__return_agent_trip"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as knox-anchor. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.bonissystems/knox-anchor/verify?hash=7cd9e634ee90aef7fff65d39002de1ac2b3754dca2f3f9ad3f87be2a3671b216" | jq -e '.changed == false'

Pinned hash 7cd9e634ee90, from Nov 17, 2026, 02:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.bonissystems/knox-anchor/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.bonissystems/knox-anchor
[![Anlyon Radar](https://radar.anlyon.com/badge/com.bonissystems/knox-anchor.svg)](https://radar.anlyon.com/servers/com.bonissystems/knox-anchor)

Source: MCP Registry. Synced Oct 21, 2026, 17:52 UTC.

Knox Anchor MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Knox Anchor MCP server safe?

No scan can promise that. What its definitions show: 9 tools, 6 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Knox Anchor MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Knox Anchor MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Knox Anchor MCP server have?

9 tools: 6 write, 3 read. verify_anchor, anchor_event, anchor_mcp_tool_call, anchor_file_hash, verify_agent_trip, return_agent_trip, get_descriptor, get_chain_health and 1 more.

Does the Knox Anchor MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Knox Anchor MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Knox Anchor MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.