Server definition

Hash: sha256:b2e4d23d03c55872ca2da6f09c58cc233a5912f0b1454df264839bd02ef00e48
What it is: What a remote MCP server returned when asked what it offers: 7 tools

The blob, as servednamed by its sha256

{
  "instructions": "Knox Anchor — audit record layer for AI agents. Call get_descriptor for full server metadata, list_event_types for the canonical taxonomy, anchor_event to record an agent action.",
  "tools": [
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "event_type": {
            "description": "Canonical event type (call list_event_types to enumerate). Free-form strings are accepted but not federal-citation-grade.",
            "type": "string"
          },
          "payload": {
            "description": "JSON-serializable payload describing the agent action. Hashed verbatim into the chain; do not include secrets — the payload is recoverable on verify.",
            "type": "object"
          }
        },
        "required": [
          "event_type",
          "payload"
        ],
        "type": "object"
      },
      "name": "anchor_event",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "filename": {
            "description": "Original filename (max 256 chars).",
            "type": "string"
          },
          "hash": {
            "description": "SHA-256 file digest (64 lowercase hex chars).",
            "pattern": "^[a-fA-F0-9]{64}$",
            "type": "string"
          },
          "mime_type": {
            "description": "MIME type (max 128 chars).",
            "type": "string"
          },
          "size_bytes": {
            "description": "File size in bytes.",
            "minimum": 0,
            "type": "integer"
          }
        },
        "required": [
          "hash"
        ],
        "type": "object"
      },
      "name": "anchor_file_hash",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "agent_identity": {
            "description": "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 payload carries agentIdentityVerified:false and a commitment to the asserting principal.",
            "maxLength": 256,
            "type": "string"
          },
          "arguments_digest": {
            "description": "Caller-computed SHA-256 of the JSON-stringified arguments (64 hex chars).",
            "pattern": "^[a-fA-F0-9]{64}$",
            "type": "string"
          },
          "outcome": {
            "description": "Outcome of the tool call.",
            "enum": [
              "success",
              "error",
              "timeout",
              "rejected"
            ],
            "type": "string"
          },
          "response_digest": {
            "description": "Caller-computed SHA-256 of the JSON-stringified response (64 hex chars).",
            "pattern": "^[a-fA-F0-9]{64}$",
            "type": "string"
          },
          "server_url": {
            "description": "MCP server endpoint the agent invoked.",
            "type": "string"
          },
          "tool_name": {
            "description": "Name of the tool invoked.",
            "type": "string"
          }
        },
        "required": [
          "server_url",
          "tool_name",
          "arguments_digest",
          "agent_identity",
          "outcome"
        ],
        "type": "object"
      },
      "name": "anchor_mcp_tool_call",
      "outputSchema": null
    },
    {
      "description": "Return 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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "get_chain_health",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "get_descriptor",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {},
        "type": "object"
      },
      "name": "list_event_types",
      "outputSchema": null
    },
    {
      "description": "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.",
      "inputSchema": {
        "additionalProperties": false,
        "properties": {
          "hash": {
            "description": "SHA-256 anchor hash (64 lowercase hex chars).",
            "pattern": "^[a-fA-F0-9]{64}$",
            "type": "string"
          }
        },
        "required": [
          "hash"
        ],
        "type": "object"
      },
      "name": "verify_anchor",
      "outputSchema": null
    }
  ]
}

Verify it yourself

curl -s https://api.teppi.xyz/v1/evidence/sha256:b2e4d23d03c55872ca2da6f09c58cc233a5912f0b1454df264839bd02ef00e48 | sha256sum