MCP.so
Sign In

Cronozen Proof

@cronozen

About Cronozen Proof

Cronozen Proof — Tamper-proof audit trail for AI decisions. Open-source core + managed cloud.

Config

Add this server to your MCP-compatible client using the configuration below.

{
  "mcpServers": {
    "cronozen-proof": {
      "url": "https://mcp.cronozen.com/mcp",
      "headers": {
        "Authorization": "Bearer <YOUR_TOKEN>"
      }
    }
  }
}

Tools

7

Records an AI execution as a Decision Proof Unit (DPU). Creates a cryptographically chained proof record with SHA-256 hash chain. Returns the created DPU with decision_id and chain hash.

Verifies a specific proof record's cryptographic integrity. Checks hash consistency and returns verification status.

Verifies the entire SHA-256 hash chain integrity for a domain. Performs O(n) sequential verification of all Decision Proof Units and reports the first broken index if tampering is detected.

Retrieves a Decision Proof Unit by ID with full details including hash chain position, AI involvement, human control, evidence level, and compliance information.

Exports a Decision Proof Unit as a JSON-LD v2.0 proof document conforming to Cronozen Evidence Ontology. Includes compliance status, 6W extraction (Who/What/Where/When/How/Why), hash chain info, and policy snapshot.

Publicly verifies a DPU's cryptographic integrity without authentication. Checks SHA-256 hash validity, previous/next chain link integrity, and returns verification status. Anyone can verify — no credentials required.

Generates a structured decision report for a DPU. Returns a formatted document with decision details, hash chain verification, and download links (PDF, JSON-LD). Use this after proof_record to provide a downloadable evidence report.

Overview

What is Cronozen Proof?

Cronozen Proof provides a tamper-proof audit trail for AI decisions. It records, verifies, and exports cryptographic proof chains via MCP, SDK, or REST API, using SHA-256 hash chains to create immutable evidence.

How to use Cronozen Proof?

Connect Claude Desktop, Cursor, or any MCP client by adding the server URL and API key to your mcpServers config, or install via Smithery. Alternatively, use the npm SDK (cronozen) to record and verify decisions programmatically. Available MCP tools include proof_record, proof_verify, proof_chain_verify, proof_get, proof_export_jsonld, and proof_public_verify.

Key features of Cronozen Proof

  • Immutable SHA-256 hash chain for every decision
  • Public verification without authentication
  • Audit-ready JSON-LD v2.0 evidence export
  • Three integration paths: MCP, SDK, REST API
  • Self-hosted or Cronozen Cloud options
  • Hash chain links content, previous hash, and timestamp

Use cases of Cronozen Proof

  • Track every AI agent decision in production
  • Auto-generate tamper-proof evidence for SOC2, EU AI Act, Korea AI Basic Act
  • Answer "why did the AI do this?" with cryptographic proof
  • Record human approval/rejection alongside AI decisions
  • Immutable records for financial transactions and approvals

FAQ from Cronozen Proof

How does Cronozen Proof ensure tamper-proof evidence?

Every decision record contains a SHA-256 hash computed from its content, the previous record's hash, and a timestamp. This creates an append-only chain — tampering with any record breaks the chain for all subsequent records.

What integration options are available?

Cronozen Proof offers three paths: an MCP server for AI clients, a high-level Node.js SDK (cronozen), and a self-hosted core library (@cronozen/dpu-core) with zero dependencies. It also provides a REST API.

Can I self-host Cronozen Proof?

Yes. You can run the MCP server via Docker or from source, configure your own API endpoint, and fully control the deployment. The core hash chain library is also self-hosted and free.

Is there a cloud version?

Yes, Cronozen Cloud handles hosting, security, backups, and updates. Plans include Cloud Pro ($99/mo, 1,000 events) and Cloud Business ($299/mo, unlimited events). Enterprise plans with custom SLAs and on-premise managed options are available.

What are the runtime requirements?

The core library (@cronozen/dpu-core) has zero dependencies and runs anywhere. The MCP server requires Node.js and can be containerized with Docker. All integrations require an API key for authenticated operations; public verification does not require authentication.

Frequently asked questions

How does Cronozen Proof ensure tamper-proof evidence?

Every decision record contains a SHA-256 hash computed from its content, the previous record's hash, and a timestamp. This creates an append-only chain — tampering with any record breaks the chain for all subsequent records.

What integration options are available?

Cronozen Proof offers three paths: an MCP server for AI clients, a high-level Node.js SDK (`cronozen`), and a self-hosted core library (`@cronozen/dpu-core`) with zero dependencies. It also provides a REST API.

Can I self-host Cronozen Proof?

Yes. You can run the MCP server via Docker or from source, configure your own API endpoint, and fully control the deployment. The core hash chain library is also self-hosted and free.

Is there a cloud version?

Yes, Cronozen Cloud handles hosting, security, backups, and updates. Plans include Cloud Pro ($99/mo, 1,000 events) and Cloud Business ($299/mo, unlimited events). Enterprise plans with custom SLAs and on-premise managed options are available.

What are the runtime requirements?

The core library (`@cronozen/dpu-core`) has zero dependencies and runs anywhere. The MCP server requires Node.js and can be containerized with Docker. All integrations require an API key for authenticated operations; public verification does not require authentication.

Comments

More Other MCP servers