All servers · Crypto & blockchain · Health & fitness
Knox Anchor
com.bonissystems/knox-anchor · v1.0.1
Tools changed (7 days)No registry update 90+ days
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-03-26 |
| Rank score | — |
| Declared risk | Not declared (tools carry no read/destructive hints) |
| Capabilities declared | tools |
| Tool definitions | 9 tools · with description 100% · input schema is an object 100% · read/destructive hints 0% |
Description written by the publisher, not verified
Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped.
Connect
streamable-http · https://bonissystems.com/api/knox/mcp
claude mcp add --transport http knox-anchor https://bonissystems.com/api/knox/mcp{
"mcpServers": {
"knox-anchor": {
"url": "https://bonissystems.com/api/knox/mcp"
}
}
}Tools as reported by the server
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 surface.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 window). Mirrors the public /api/knox/health endpoint under the MCP envelope.list_event_typesReturn 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.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. Public — no authentication required.anchor_eventAnchor 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 reanchor_mcp_tool_callConvenience 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 madeanchor_file_hashAnchor 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 ofverify_agent_tripTHE 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 isreturn_agent_tripTHE 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 th
Tool changes
- 2026-10-23: get_descriptor, get_chain_health, list_event_types, verify_anchor, anchor_event, anchor_mcp_tool_call, anchor_file_hash, verify_agent_trip, return_agent_trip
- 2026-10-18: get_descriptor, get_chain_health, list_event_types, verify_anchor, anchor_event, anchor_mcp_tool_call, anchor_file_hash, verify_agent_trip, return_agent_trip
- 2026-10-16: get_descriptor, get_chain_health, list_event_types, verify_anchor, anchor_event, anchor_mcp_tool_call, anchor_file_hash
Website · JSON · Text for agents · Registry updated 2026-05-01