com.bonissystems/knox-anchor

Est-ce que com.bonissystems/knox-anchor est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.bonissystems/knox-anchor » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 9 outils

• anchor_event≈ 222 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • payload · object · requis
    JSON-serializable payload describing the agent action. Hashed verbatim into the chain; do not include secrets — the payload is recoverable on verify.
  • event_type · string · requis
    Canonical event type (call list_event_types to enumerate). Free-form strings are accepted but not federal-citation-grade.

  Exemple d'appel

  {"name": "anchor_event", "arguments": {"payload": {}, "event_type": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• anchor_file_hash≈ 236 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • hash · string · requis
    SHA-256 file digest (64 lowercase hex chars).
  • filename · string · optionnel
    Original filename (max 256 chars).
  • mime_type · string · optionnel
    MIME type (max 128 chars).
  • size_bytes · integer · optionnel
    File size in bytes.

  Exemple d'appel

  {"name": "anchor_file_hash", "arguments": {"hash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• anchor_mcp_tool_call≈ 431 tokens

  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.

  Paramètres, retour & exemple (6)

  Paramètres

  • outcome · string · requis · success | error | timeout | rejected
    Outcome of the tool call.
  • tool_name · string · requis
    Name of the tool invoked.
  • server_url · string · requis
    MCP server endpoint the agent invoked.
  • agent_identity · string · requis
    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.
  • response_digest · string · optionnel
    Caller-computed SHA-256 of the JSON-stringified response (64 hex chars).
  • arguments_digest · string · requis
    Caller-computed SHA-256 of the JSON-stringified arguments (64 hex chars).

  Exemple d'appel

  {"name": "anchor_mcp_tool_call", "arguments": {"outcome": "success", "tool_name": "texte", "server_url": "texte", "agent_identity": "texte", "arguments_digest": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_chain_health≈ 100 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_chain_health", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_descriptor≈ 80 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "get_descriptor", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• list_event_types≈ 79 tokens

  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.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "list_event_types", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• return_agent_trip≈ 548 tokens

  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.

  Paramètres, retour & exemple (7)

  Paramètres

  • flow · string · optionnel · bsa
    Optional. "bsa" when the trip ran in a BSA flow; the departure must say the same. Only such trips can enter the examiner pack.
  • plan · array · requis
    The flight plan, as sealed at departure: [{tool, ref, max?, optional?}].
  • nonce · string · requis
    The trip nonce held by your door. Knox checks it against the nonce hash sealed at departure; it is not stored.
  • report · object|null · requis
    What the agent says it did: {actions?: [{tool, ref}], claimedKinds?: [kind], effects?: [{kind, ref, hash}]}, or null when it never reported back.
  • door_head · string · requis
    The hash of the door's last observation (64 zeros for an empty record).
  • observations · array · requis
    The door's record, in order: [{seq, tool, kind, ref, argsCommit, resultCommit, outcome, reason, at, prevHash, hash, mac}]. Targets and keyed commitments, never content.
  • departure_seal · string · requis
    The stamp code of the trip's agent_trip_departed, sealed under your key before the agent's first action.

  Exemple d'appel

  {"name": "return_agent_trip", "arguments": {"plan": [], "nonce": "texte", "report": {}, "door_head": "texte", "observations": [], "departure_seal": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_agent_trip≈ 221 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • hash · string · optionnel
    The returned seal: the stamp code of the trip's agent_trip_returned (64 hex chars).
  • trip_id · string · optionnel
    The trip id the door minted at departure.

  Exemple d'appel

  {"name": "verify_agent_trip", "arguments": {"hash": "texte", "trip_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_anchor≈ 120 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • hash · string · requis
    SHA-256 anchor hash (64 lowercase hex chars).

  Exemple d'appel

  {"name": "verify_anchor", "arguments": {"hash": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://bonissystems.com/api/knox/mcp