Knox Anchor is answering right now. Last checked 9 min ago. It exposes 9 tools.
Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.
Uptime history
91 days of history · worst day 92%
91 days agonow
100.0%
Uptime 24h
91 of 91 checks
9
Tools
read from the server
301 ms
Response time
average over 24h
open, no key
Access
streamable-http
What changed 6
Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 21 September 2026. No other catalogue keeps this.
2 Nov
a tool changed the parameters it asks for
return_agent_trip
23 Oct
a tool description was rewritten
get_chain_health
18 Oct
2 tools appeared
return_agent_trip, verify_agent_trip
20 Sep
a tool description was rewritten
anchor_mcp_tool_call
20 Sep
a tool changed the parameters it asks for
anchor_mcp_tool_call
Nothing serious here today
Today is the operative word: we check Knox Anchor every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.
run in your terminal
claude mcp add knox-anchor --transport http https://bonissystems.com/api/knox/mcpSettings → Connectors → Add custom connector, then paste this address
https://bonissystems.com/api/knox/mcp~/.codex/config.toml
[mcp_servers.knox-anchor]
url = "https://bonissystems.com/api/knox/mcp".cursor/mcp.json
{
"mcpServers": {
"knox-anchor": {
"url": "https://bonissystems.com/api/knox/mcp"
}
}
}.vscode/mcp.json
{
"servers": {
"knox-anchor": {
"type": "http",
"url": "https://bonissystems.com/api/knox/mcp"
}
}
}Available tools 9
Read directly from the server with tools/list, grouped by what they act on.
If a tool disappears, we record the date.
anchor
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.
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.
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.
verify
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.
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.
chain
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.
descriptor
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.
event
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.
return
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.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://bonissystems.com/api/knox/mcp | streamable-http | answering | 229 ms | 9 min ago |
Alternatives to Knox Anchor
same job, measured the same wayTouchstone
by touchstone
Bitcoin-anchored, tamper-evident audit log for AI agents — record, disclose and verify actions.
Occasio
by occasiolabs
Tamper-evident, Sigstore-signed audit trail for Claude Code agents.
Lians Agent Memory
by ebeirne
Bitemporal memory for AI agents with point-in-time recall and tamper-evident audit history.
AgentLens
by agentkitai
Tamper-evident, SHA-256 hash-chained audit trail and observability for AI agents.
Tradememory Protocol
by mnemox-ai
Tamper-evident decision audit trail and outcome-weighted memory for AI trading agents.
ai-audit-trail
by sundsoffice-tech
Tamper-evident audit trails for AI agents — Ed25519-signed, hash-chained, EU AI Act ready.
Pgmoat
by kitalon-labs-llc
Governed, read-only Postgres access for AI agents: SQL safety, RLS, budgets, tamper-evident audit.
ZizkaDB
by zizka-ai-sl
Causal memory and tamper-evident audit log for AI agents: log, why, search, time travel.
Knox Anchor — questions
Answers built from our own checks of this server.
What can Knox Anchor do?
It exposes 9 tools, read directly from the server on our last check. Among them: anchor_event, anchor_file_hash, anchor_mcp_tool_call, get_chain_health, get_descriptor, list_event_types and 3 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README.
How MCP servers expose tools in the first place →
What is Knox Anchor mostly used for?
Its tools cluster around anchor and verify. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Knox Anchor working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 301 ms. The bar chart above shows every period we have measured.
How do I connect Knox Anchor?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Knox Anchor need an API key?
No. Knox Anchor completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 9 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Knox Anchor?
It answers our handshake in 301 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.