Knox Anchor
Anchor AI agent audit trails to Bitcoin with tamper-evident permanence when you need defensible logs shaped like FRE 902(13)/(14) evidence.
Overview
com.bonissystems/knox-anchor is a MCP server for the Ship phase that provides Bitcoin-anchored, tamper-evident audit permanence for AI agent activity with FRE 902(13)/(14)-shaped evidence design.
What is this MCP server?
- Bitcoin-anchored audit permanence layer purpose-built for AI agent actions
- Tamper-evident design aligned with FRE 902(13)/(14)-shaped evidence framing
- Hosted remote MCP at bonissystems.com/api/knox/mcp (streamable-http)
- Knox Anchor product v1.0.1 via Bonis Systems AAM MCP offering
- Compliance-oriented MCP bridge, not a general-purpose secrets vault
- Server version 1.0.1
- Remote transport: streamable-http at bonissystems.com/api/knox/mcp
- Product title: Knox Anchor
What problem does it solve?
Agent action logs in your own database are easy to alter later, which weakens trust when investors, regulators, or customers ask what the AI actually did.
Who is it for?
Builders shipping agent products who need a serious audit-trail narrative and are willing to integrate a specialized Knox Anchor MCP remote.
Skip if: Hobby projects with no compliance pressure, or teams that only need debug console logs without external anchoring cost or legal framing.
What do I get? / Deliverables
You can tie agent audit events to an external Bitcoin-anchored permanence layer so tampering is harder to hide and retention story is clearer at launch.
- MCP-linked Knox Anchor audit permanence integration
- Externally anchored agent event records
- Stronger tamper-evidence story for security and launch reviews
Recommended MCP Servers
Journey fit
Audit permanence matters most when you Ship—before production launch and whenever you must prove what an agent did—but it also supports Operate incident review. Security is the primary shelf for tamper-evident logging and evidence-grade retention, not generic app feature work.
How it compares
Bitcoin-anchored audit permanence MCP, not a generic monitoring dashboard or SIEM replacement.
Common Questions / FAQ
Who is com.bonissystems/knox-anchor for?
Solo founders and small teams running AI agents who need tamper-evident, externally anchored audit trails with compliance-oriented positioning.
When should I use com.bonissystems/knox-anchor?
Use it in Ship (security, launch prep) when agent decisions must be recorded with permanence before production or for post-incident defensibility.
How do I add com.bonissystems/knox-anchor to my agent?
Add the remote MCP URL https://bonissystems.com/api/knox/mcp as streamable-http in your MCP client; review Bonis Systems site docs for account or API requirements.