Knox Anchor
REMOTE · BONISSYSTEMS.COM
Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.
Available components
Last scanned (4 hours ago)
Scores higher than 60% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1499 tokens (~166/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 0
- “return_agent_trip” added an optional parameter “folders” cosmetic
- “return_agent_trip” reworded the description of “report” cosmetic
2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
- Tool “get_chain_health” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://bonissystems.com/api/knox/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=bonissystems.com | CN=YE1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 6d0f95770f49dd11e184ecfd671219da122 |
| SANs: *.bonissystems.com, bonissystems.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of bonissystems.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| bonissystems.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' 'unsafe-eval' https://www.gstatic.com https://images.dmca.com https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data: blob: https://res.cloudinary.com https://utfs.io https://uploadthing.com https://lh3.googleusercontent.com https://storage.googleapis.com https://blockstream.info https://images.dmca.com https://*.tile.openstreetmap.org; font-src 'self' data: https://fonts.gstatic.com; connect-src 'self' blob: https://api.anthropic.com https://bonissystems.com https://cloudflareinsights.com https://*.cloudinary.com https://*.polyhaven.org https://www.gstatic.com https://storage.googleapis.com https://blockstream.info https://*.livekit.cloud wss://*.livekit.cloud wss: ws:; media-src 'self' blob: https://res.cloudinary.com https://storage.googleapis.com; worker-src 'self' blob:; frame-ancestors 'none'; base-uri 'self'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), gyroscope=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://bonissystems.com/api/knox/mcp | Verified | 200 | |
| http (plaintext) | http://bonissystems.com/api/knox/mcp | HTTPS enforced | 302 | https://bonissystems.com/api/knox/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
anchor_event ~145
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 | Type | Req | Description |
|---|---|---|---|
| event_type | string | yes | Canonical event type (call list_event_types to enumerate). Free-form strings are accepted but not federal-citation-grade. |
| payload | object | yes | JSON-serializable payload describing the agent action. Hashed verbatim into the chain; do not include secrets — the payload is recoverable on verify. |
No output schema declared.
No examples provided.
anchor_file_hash ~155
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 | Type | Req | Description |
|---|---|---|---|
| filename | string | – | Original filename (max 256 chars). |
| hash | string | yes | SHA-256 file digest (64 lowercase hex chars). |
| mime_type | string | – | MIME type (max 128 chars). |
| size_bytes | integer | – | File size in bytes. |
No output schema declared.
No examples provided.
anchor_mcp_tool_call ~259
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 | Type | Req | Description |
|---|---|---|---|
| agent_identity | string | yes | Stable identifier the CALLER asserts for the agent (e.g., agent ID, principal, did:knox:agent-X). Recorded as an assertion attributed to your API key, never as an authenticated subject; the anchored… |
| arguments_digest | string | yes | Caller-computed SHA-256 of the JSON-stringified arguments (64 hex chars). |
| outcome | string | yes | Outcome of the tool call. |
| response_digest | string | – | Caller-computed SHA-256 of the JSON-stringified response (64 hex chars). |
| server_url | string | yes | MCP server endpoint the agent invoked. |
| tool_name | string | yes | Name of the tool invoked. |
No output schema declared.
No examples provided.
get_chain_health ~63
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_descriptor ~44
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_event_types ~42
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
return_agent_trip ~500
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.
| Name | Type | Req | Description |
|---|---|---|---|
| departure_seal | string | yes | The stamp code of the trip's agent_trip_departed, sealed under your key before the agent's first action. |
| door_head | string | yes | The hash of the door's last observation (64 zeros for an empty record). |
| flow | string | – | Optional. "bsa" when the trip ran in a BSA flow; the departure must say the same. Only such trips can enter the examiner pack. |
| folders | array | – | Optional. For each work folder the departure sealed ({label, root, files}): {label, before: [{path, size, sha256}], after: [...]}, made on your own machine (public/legal-kit/knox-folder-manifest.mjs)… |
| nonce | string | yes | The trip nonce held by your door. Knox checks it against the nonce hash sealed at departure; it is not stored. |
| observations | array | yes | The door's record, in order: [{seq, tool, kind, ref, argsCommit, resultCommit, outcome, reason, at, prevHash, hash, mac}]. Targets and keyed commitments, never content. |
| plan | array | yes | The flight plan, as sealed at departure: [{tool, ref, max?, optional?}]. |
| report | object|null | yes | What the agent says it did: {actions?: [{tool, ref}], claimedKinds?: [kind], effects?: [{kind, ref, hash}], files?: [{folder, path, change: added|changed|removed}]}, or null when it never reported ba… |
No output schema declared.
No examples provided.
verify_agent_trip ~158
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 | Type | Req | Description |
|---|---|---|---|
| hash | string | – | The returned seal: the stamp code of the trip's agent_trip_returned (64 hex chars). |
| trip_id | string | – | The trip id the door minted at departure. |
No output schema declared.
No examples provided.
verify_anchor ~69
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 | Type | Req | Description |
|---|---|---|---|
| hash | string | yes | SHA-256 anchor hash (64 lowercase hex chars). |
No output schema declared.
No examples provided.
How do I install the Knox Anchor MCP server?
Knox Anchor is a hosted endpoint at https://bonissystems.com/api/knox/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · bonissystems.com
claude mcp add --transport http com-bonissystems-knox-anchor 'https://bonissystems.com/api/knox/mcp'
What is the Knox Anchor MCP server?
Knox Anchor is an MCP server listed in the public MCP registry as com.bonissystems/knox-anchor. Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped. This page covers its hosted endpoint (https://bonissystems.com/api/knox/mcp).
Is the Knox Anchor MCP server safe to use?
Knox Anchor scores 73 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Knox Anchor MCP server expose?
Knox Anchor exposes 9 tools: get_descriptor, get_chain_health, list_event_types, verify_anchor, anchor_event, and 4 more. Their descriptions and schemas cost roughly 1,435 tokens of context every time the server is loaded.
Does the Knox Anchor MCP server require authentication?
No. We connected to Knox Anchor without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Knox Anchor MCP server still maintained?
Knox Anchor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.