protogrid

Search / com.bonissystems/knox-anchor

Knox Anchor

R0· no sign-in

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

v1.0.1 · active · website · descriptor JSON · versions

An agent can connect right now, no human step.Remote endpoint, no authentication, reachable on the last probe.
Quality79good
Trust75of 100
Uptime, 30 days96%
Latency p50341 ms

Connect

8 clients · secrets stay placeholders
{
  "mcpServers": {
    "knox-anchor": {
      "type": "http",
      "url": "https://bonissystems.com/api/knox/mcp"
    }
  }
}
claude mcp add --transport http knox-anchor https://bonissystems.com/api/knox/mcp
[mcp_servers.knox-anchor]
url = "https://bonissystems.com/api/knox/mcp"
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "knox-anchor": {
      "type": "remote",
      "url": "https://bonissystems.com/api/knox/mcp",
      "enabled": true
    }
  }
}
{
  "mcpServers": {
    "knox-anchor": {
      "type": "http",
      "url": "https://bonissystems.com/api/knox/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=knox-anchor&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vYm9uaXNzeXN0ZW1zLmNvbS9hcGkva25veC9tY3AifQ%3D%3D"
}
{
  "servers": {
    "knox-anchor": {
      "type": "http",
      "url": "https://bonissystems.com/api/knox/mcp"
    }
  }
}
{
  "mcpServers": {
    "knox-anchor": {
      "httpUrl": "https://bonissystems.com/api/knox/mcp"
    }
  }
}
extensions:
  "knox-anchor":
    enabled: true
    name: "knox-anchor"
    type: streamable_http
    uri: "https://bonissystems.com/api/knox/mcp"
    timeout: 300

Quality 79 / 100good

protocol75 · weight 25
  • warn
    protocol.modernnewest supported version is 2025-03-26; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
  • n/a
    protocol.statelessonly applies to 2026-07-28 servers
  • pass
    protocol.transportstreamable HTTP
  • n/a
    protocol.list_ttlonly applies to 2026-07-28 servers
authorizationn/a · weight 15
  • n/a
    auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
  • n/a
    auth.secret_in_urlno templated URL
tool hygiene71 · weight 30
  • pass
    tools.descriptionsevery tool has a description
  • pass
    tools.description_lengthdescriptions are concise
  • pass
    tools.schemasevery tool has an object input schema
  • fail
    tools.annotationsno tool declares readOnlyHint or destructiveHint, so clients cannot tell safe calls from risky ones
  • fail
    tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: verify_anchor (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); anchor_event (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); verify_agent_trip (readOnlyHint, destructiveHint, idempotentHint, openWorldHint); …
  • pass
    tools.token_costabout 1,887 tokens to load every tool
  • pass
    tools.api_dumptools are not a one-to-one API dump
stability100 · weight 15
  • pass
    stability.changes2 tool changes in 30 days
  • pass
    stability.rug_pullno tool changed its meaning under the same name
dependenciesn/a · weight 15
  • n/a
    deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

9 tools, about 1,887 tokens to load them all · tool set da8788fde808 · tools last changed 2026-10-18 · checked 2026-10-19 10:52 UTC

Tool changes

  • return_agent_tripadded

    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_tripadded

    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.

Full history: list_changes · trend: quality JSON.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 75 / 100

no-repository
provenance55
liveness99
freshness65
hygiene80

+dns-namespace +website +reachable +uptime-96% ~updated-171d-ago -no-repository

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remoteauthreachableuptime 30dp50protocollast ok
https://bonissystems.com/api/knox/mcp streamable-httpnoneyes96%341 ms2025-03-262026-10-19

Tools (9)

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 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. 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. 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.
get_chain_healthReturn Knox service health: process uptime, database latency, total anchors written, latest anchor timestamp, and the Bitcoin anchor SLA target (OpenTimestamps interval, 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 surface.
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.
return_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 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. 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. Public — no authentication required.

Schemas: list_tools.

Similar MCP servers

More from com.bonissystems

And 1 more from this publisher.

Official server.json
{
  "name": "com.bonissystems/knox-anchor",
  "title": "Knox Anchor",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
  "remotes": [
    {
      "url": "https://bonissystems.com/api/knox/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.1",
  "websiteUrl": "https://bonissystems.com/aam/mcp-server",
  "description": "Bitcoin-anchored, tamper-evident audit-permanence layer for AI agents, FRE 902(13)/(14)-shaped."
}