Skip to content

README.md

Latest commit

 

History

History
173 lines (138 loc) · 5.69 KB

README.md

File metadata and controls

173 lines (138 loc) · 5.69 KB
Raw

@atrib/verify-mcp

Legacy home. The read-verb implementation moved to @atrib/recall per the attest/recall rename (D164). atrib-verify folds into recall through its verification parameter. This package re-exports the same surface and forwards the atrib-verify binary to @atrib/recall's handlers. Results are JSON-identical. The atrib-verify tool name stays mounted as a permanent alias during the alias window, alongside the new recall tool. @atrib/verify (the verifier library) is NOT renamed. This package keeps a hard dependency on @atrib/verify so the verifier always resolves, independent of @atrib/recall's optional-peer posture toward it.

MCP server exposing the atrib-verify cognitive primitive for atrib's verifiable action layer. It verifies counterparty handoff evidence before a receiving agent signs follow-up work that cites those records through informed_by.

The package is read-only. It accepts caller-supplied evidence, returns accepted and rejected hashes, and leaves the follow-up signing step to atrib-emit or normal wrapped tool calls.

Install

npm install @atrib/verify-mcp

Tool surface

Host-specific tool names vary. The MCP tool itself is named atrib-verify:

mcp__atrib-verify__atrib-verify({
  packet?: unknown,
  records?: unknown[],
  claims?: unknown[],
  required_record_hashes?: string[],
  trusted_creator_keys?: string[],
  allowed_context_ids?: string[],
  require_body?: boolean,
  require_body_commitment?: boolean,
  require_log_inclusion?: boolean,
  log_public_key_b64?: string,
  max_age_ms?: number,
  now_ms?: number,
})

A worked call. Agent B received agent A's records (as a local-mirror envelope or a continuation packet) and wants to cite them in its own follow-up work. Verify them first, then link only the accepted hashes through informed_by:

mcp__atrib-verify__atrib-verify({
  packet: {
    required_record_hashes: ['sha256:<64-hex-of-A-record>'],
    records: [
      {
        record: {
          /* a full signed AtribRecord produced by agent A */
        },
        proof: {
          /* optional inclusion proof from the public log */
        },
      },
    ],
    trusted_creator_keys: ['<agent-A-base64url-creator-key>'],
  },
  require_log_inclusion: true,
})
// The response's accepted hashes are the ones that passed every check.
// Cite only those in the follow-up record's informed_by.

Evidence

packet, records, and claims accept the same evidence shapes as @atrib/verify:

  • D062 local mirror envelopes: { record, proof?, _local?: { content?, args?, result? } }
  • Private continuation packets: { required_record_hashes, records, trusted_creator_keys?, allowed_context_ids? }
  • Bare records for signature-only checks, when body or proof checks are not required

The response returns accepted hashes plus compact per-claim evidence:

{
  "primitive": "atrib-verify",
  "all_accepted": true,
  "accepted_record_hashes": ["sha256:..."],
  "accepted": [
    {
      "record_hash": "sha256:...",
      "accepted": true,
      "signature_ok": true,
      "signer_trusted": true,
      "context_allowed": true,
      "body": {
        "args_hash_present": true,
        "args_hash_ok": true,
        "result_hash_present": false,
        "result_hash_ok": null
      }
    }
  ],
  "rejected": []
}

Behaviors

  • Read-only: never signs records, submits to the log, or mutates the local mirror.
  • Caller-supplied evidence: does not fetch from the public log or retrieve archive bodies.
  • Verifier-backed: delegates signature, trust, body-commitment, inclusion, freshness, and context checks to @atrib/verify.
  • Handoff-oriented: accepted hashes are the values the receiving agent can cite through informed_by when it signs follow-up work.
  • Explicit rejection: failed claims stay visible in rejected instead of disappearing from the response.

Wire-up

Run it through npx from an MCP host:

{
  "mcpServers": {
    "atrib-verify": {
      "command": "npx",
      "args": ["-y", "@atrib/verify-mcp"]
    }
  }
}

Or install it globally. The package exposes the atrib-verify binary:

npm install -g @atrib/verify-mcp
atrib-verify

Local Development

From a checkout of the atrib monorepo:

pnpm --filter @atrib/verify-mcp build
pnpm --filter @atrib/verify-mcp test
pnpm --filter @atrib/verify-mcp start

For local MCP host testing without npm:

{
  "mcpServers": {
    "atrib-verify": {
      "command": "node",
      "args": ["/absolute/path/to/atrib/services/atrib-verify/dist/main.js"]
    }
  }
}

Relationship to @atrib/verify

@atrib/verify-mcp depends on @atrib/verify for verifier semantics. The MCP package owns the agent-facing schema, stdio transport, and compact response shape.

Status

Deprecated on npm; superseded by the recall verification parameter in @atrib/recall, with the atrib-verify tool name mounted as a permanent alias. Historically cognitive primitive #7. It depends on @atrib/verify for verifier semantics and keeps the MCP surface read-only.

License

Apache-2.0.

Part of atrib

atrib is an open protocol for verifiable agent actions. Every action becomes a signed, chain-linked record that anyone can verify against a public Merkle log, with no operator to trust. This package is one entrypoint. See the full package family and the protocol spec.