Skip to main content
Glama
Cryptair MCP Server

Cryptair MCP Server

by Syronius

Cryptair MCP Server

Cryptographic attestation for AI agents, exposed as native MCP tools.

Lets any MCP-capable agent (Claude Desktop, Cursor, Cline, Windsurf, Zed, …) prove agreements, certify documents, and verify counterparty claims with on-chain receipts on Hedera Hashgraph. Works zero-config out of the box: agents can self-register and start using attestation immediately, with no email verification or human-in-the-loop signup.

What It Does

Cryptair lets two agents (or an agent and a human) prove they agreed on the same digital artifact at a specific moment. Every confirmed agreement is written as a SHA-256 hash to Hedera Hashgraph, producing a permanent, third-party-verifiable receipt.

This MCP server exposes six tools that map cleanly to how agents think:

Tool

When to call

certify_document

"I want to prove this file existed at this moment."

verify_document

"Has this document been attested before? Is it tampered?"

initiate_attestation

"I want my counterparty to confirm they have the same document I do."

submit_attestation

"I received an attestation link from someone — confirm I have the matching file."

check_attestation

"What's the status of this attestation session?"

register_agent

"Create a Cryptair account for me so I can authenticate."

Related MCP server: DocImprint

Install

npm install -g @cryptair/mcp-server

Or run directly via npx (no install needed):

npx -y @cryptair/mcp-server

Configuration

Claude Desktop

Edit ~/Library/Application Support/Claude/claude_desktop_config.json (macOS) or %APPDATA%\Claude\claude_desktop_config.json (Windows):

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

Cursor

Edit ~/.cursor/mcp.json:

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

Cline / Windsurf / Zed

All MCP-capable clients use the same config shape. Point them at npx -y @cryptair/mcp-server.

Optional: Pre-configure Credentials

If you already have a Cryptair API key, you can supply it via env so the agent skips registration:

{
  "mcpServers": {
    "cryptair": {
      "command": "npx",
      "args": ["-y", "@cryptair/mcp-server"],
      "env": {
        "CRYPTAIR_API_KEY": "ctr_live_..."
      }
    }
  }
}

Otherwise, the agent will call register_agent the first time it needs authentication, and the API key is silently stored at ~/.cryptair/credentials.json for future use.

Example Agent Prompts

After installing, try prompts like:

"Certify the contents of ~/Documents/proposal-v3.pdf so we have a timestamped receipt."

"Send ~/Documents/contract.pdf to Acme Corp and get them to formally acknowledge receipt — generate the link."

"Acme sent me this Cryptair link: https://www.cryptair.io/attest/abc...?token=xyz. Confirm ~/Downloads/contract.pdf matches what they sent."

"What's the status of attestation session abc-123?"

The agent will pick the right tool and handle credential bootstrapping automatically.

How Attestation Works

Single-party (certify_document)

  1. The MCP server hashes the file locally with SHA-256.

  2. The hash is sent to Cryptair, which writes it to a Hedera Consensus Service topic.

  3. You get back a Hedera transaction ID, consensus timestamp, and a public certificate URL.

  4. Anyone can verify by re-hashing the file and calling verify_document — the file content never has to leave your machine.

Two-party (initiate_attestation + submit_attestation)

  1. Agent A initiates with a document hash and counterparty name. Cryptair returns a shareable URL.

  2. Agent A sends the URL to Agent B via any channel (email, Slack, etc.).

  3. Agent B opens the URL and submits the file they have. Their MCP server hashes it locally.

  4. Cryptair compares hashes server-side:

    • Match → both parties' agreement is written to Hedera. Permanent record.

    • Mismatch → tamper event is written to Hedera. Both parties are notified.

Agent B does not need a Cryptair account to participate. If Agent B supplies an email when submitting, an account is auto-provisioned for them and the API key is silently persisted by their MCP server — so they can initiate their own attestations later without any signup friction.

Why MCP, Not Skills

This server is cross-vendor by design. Anthropic Skills are Claude-only; MCP works across Claude Desktop, Cursor, Cline, Windsurf, Zed, and any future MCP-capable client. One install, every agent ecosystem.

Environment Variables

Variable

Purpose

Default

CRYPTAIR_API_KEY

Pre-configured API key. Skips register_agent.

(none)

CRYPTAIR_EMAIL

Email used for submit_attestation auto-provisioning if omitted from the call.

(none)

CRYPTAIR_BASE_URL

API base URL. Override for self-hosted or staging.

https://www.cryptair.io

Development

git clone https://github.com/Syronius/cryptair-mcp-server
cd mcp-server
npm install
npm run build
npm start

The server speaks JSON-RPC over stdio. To test manually, send tools/list to confirm all six tools are registered.

Free Tier & Pricing

The Cryptair free tier currently lets every account originate a small number of attestations per month. Counterparty completion (submit_attestation) is always free. Heavy users can top up with prepaid credits — see cryptair.io/pricing for details.

License

MIT

Available Tools

6 tools
certify_documentA

Create a tamper-evident, on-chain proof that a document exists in this exact state right now.

USE WHEN you want to:

  • Lock in a contract, proposal, or agreement at a specific moment

  • Prove a deliverable existed before a deadline

  • Anchor a code commit, report, or any digital artifact to an immutable timestamp

  • Generate a receipt that anyone can verify (no Cryptair account required to verify)

This is a SINGLE-PARTY operation. It writes a SHA-256 hash of the file to Hedera Hashgraph. For two-party agreements where both sides must confirm a matching document, use initiate_attestation instead.

Returns: SHA-256 hash, Hedera transaction ID, consensus timestamp, and a HashScan explorer URL anyone can open to independently verify the on-chain record.

Requires a Cryptair API key. If none is configured, call register_agent first.

Inputs: file_path (required), notify_email.

check_attestationA

Look up the current status of an attestation session.

USE WHEN you want to:

  • Poll whether the counterparty has completed an attestation you initiated

  • Retrieve the certificate URL after certification

  • Check whether a session has expired or been tampered

Returns: { status: 'pending' | 'certified' | 'tampered', hedera_tx, certificate_url, expires_at, ... }

This endpoint is public — no API key required.

Inputs: session_id (required).

initiate_attestationA

Start a TWO-PARTY attestation. Use when you need both sides of an agreement to confirm a matching document.

USE WHEN you want to:

  • Get a counterparty (another agent or a human) to formally acknowledge receipt of a contract, proposal, or deliverable

  • Lock in a mutual agreement that's only valid if both sides see the same content

  • Create an audit-grade record that two parties agreed on this exact document

How it works:

  1. You initiate with a document hash. Cryptair returns a shareable URL.

  2. You send the URL to your counterparty (out of band — email, Slack, etc.).

  3. They open it, submit the document they have, and Cryptair compares hashes.

  4. If hashes match: certified on Hedera. If not: tamper recorded on Hedera.

  5. The counterparty does NOT need a Cryptair account. They can complete for free.

Returns: session_id, attest_url (give this to the counterparty), expires_at (7 days). Poll with check_attestation to see when the counterparty completes.

Requires a Cryptair API key. Call register_agent first if you don't have one.

Inputs: document_hash (required), counterparty_name (required), metadata.

register_agentA

Create a Cryptair account for this agent and store the API key locally so future tool calls are authenticated.

USE WHEN:

  • You're about to call certify_document or initiate_attestation and there is no API key configured

  • The user installed the Cryptair MCP server and wants to start using it without manually creating an account

Self-service: no email verification, no magic link, no human-in-the-loop. The API key is generated immediately and persisted to ~/.cryptair/credentials.json. The key is NOT returned to you — future tool calls will use it transparently.

Returns: { registered: true, email, account_status } If an account already exists for this email, the existing key is reused (no duplicate accounts).

Inputs: email (required), company, framework, planned_use, +1 more.

submit_attestationA

Complete a two-party attestation as the COUNTERPARTY. You received an attest_url from someone who initiated.

USE WHEN you want to:

  • Confirm that you have the same document an initiator claimed to send you

  • Acknowledge an agreement, proposal, or deliverable on-chain

  • Detect tampering — if the document you received differs from what was initiated, this records a tamper event

You do NOT need a Cryptair API key to submit. The attest_url contains a one-time token that authorizes you.

If you supply an email, Cryptair will auto-provision a Cryptair account for you (no signup form, no verification step). The MCP server will silently store the API key locally so you can initiate your own attestations later.

Returns: { status: 'certified' | 'tampered', hedera_transaction_id, certificate_url }

  • 'certified' = hashes matched, agreement recorded on Hedera

  • 'tampered' = hashes did not match, tamper event recorded on Hedera

Inputs: attest_url (required), email, file_path, document_hash.

verify_documentA

Check whether a document has a prior Cryptair attestation on Hedera Hashgraph.

USE WHEN you want to:

  • Confirm a counterparty's claim that a document was certified

  • Detect whether a file has been altered since it was attested

  • Look up the original Hedera transaction for a given file

This is PUBLIC — no API key required. Anyone can verify any document.

Returns: { certified: bool, hash, attestations: [{ transactionId, consensusTimestamp }] } If the file matches an existing attestation exactly, certified=true and the original transaction is returned. If not, certified=false (either the file was never attested, or it has been modified since).

Inputs: file_path (required).

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a unique, well-defined purpose: single-party certification, two-party initiation, counterparty submission, status polling, public verification, and account registration. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (e.g., certify_document, initiate_attestation), making the API predictable and easy to navigate.

    Tool Count5/5

    With 6 tools, the surface is lean and focused. Each tool serves a distinct step in the attestation workflow, and there are no extraneous or redundant tools.

    Completeness4/5

    The tool set covers the full lifecycle of document attestation: registration, single-party certification, two-party attestation (initiate, submit, poll), and public verification. Minor gaps like bulk listing or revocation are absent but not critical for the core workflow.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to sign decisions with post-quantum cryptographic proofs and maintain secure audit trails for compliance. It provides tools for stamping events, verifying chain integrity, and exporting audit data across industries like finance and healthcare.
      4
      55 npm
      MIT
    • F
      license
      Not graded
      quality
      A
      maintenance
      Verifiable document intelligence for AI agents. Extract, summarize, claim-check, and notarize PDFs & URLs with cryptographic proofs, cross-document search, and on-chain attestation via Base L2.
      -