Cryptair Mcp Server

io.github.SyroniusPublished by GitHub account Syroniusv0.1.1Updated Nov 10, 2026

Tamper-evident attestation tools for AI agents — on-chain receipts on Hedera Hashgraph mainnet.

VerifiedSTDIODesktop onlyFinanceSecurity & Monitoring

Overview

AI-generated overview

MCP server that lets an agent certify documents and prove two-party agreements with tamper-evident on-chain receipts on Hedera Hashgraph.

What you can do
  • Certify a document by hashing it locally and writing the hash to Hedera for a timestamped receipt
  • Verify a file against earlier attestations and detect tampering
  • Initiate a two-party attestation and get a shareable link for the counterparty
  • Submit a received attestation link to confirm the counterparty holds the matching file
  • Check the status of an attestation session
  • Register a Cryptair account so the agent can authenticate
When to use it
Useful when an agent or its user needs proof that a document existed at a given time, or that two parties held the same file, with a receipt a third party can check. Suits contract, proposal and hand-off workflows where a verifiable record matters more than the file itself being shared.
Requirements
Runs locally over stdio, typically via npx with Node.js. An optional Cryptair API key can be supplied through CRYPTAIR_API_KEY; otherwise the agent self-registers and the key is saved to a local credentials file. Optional CRYPTAIR_EMAIL and CRYPTAIR_BASE_URL variables exist. Network access to the Cryptair API is required.
Before you install
Without a pre-set key the agent can create an account on its own and store the API key in a local credentials file, with no human signup step. Document hashes, counterparty names and any supplied email are sent to Cryptair and written to a public ledger, so treat that metadata as public. Attestations are permanent and cannot be undone. The free tier limits monthly attestations and extra usage is paid.

Installation

In SourceWeft

  1. Open Cryptair Mcp Server in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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:

ToolWhen 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."

Install

bash
npm install -g @cryptair/mcp-server

Or run directly via npx (no install needed):

bash
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):

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

Cursor

Edit ~/.cursor/mcp.json:

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:

json
{  "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

VariablePurposeDefault
CRYPTAIR_API_KEYPre-configured API key. Skips register_agent.(none)
CRYPTAIR_EMAILEmail used for submit_attestation auto-provisioning if omitted from the call.(none)
CRYPTAIR_BASE_URLAPI base URL. Override for self-hosted or staging.https://www.cryptair.io

Development

bash
git clone https://github.com/Syronius/cryptair-mcp-servercd mcp-servernpm installnpm run buildnpm 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

Source: README.md at commit 6142877

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.1LatestSep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts