io.github.Syronius/cryptair-mcp-server
Tamper-evident attestation tools for AI agents — on-chain receipts on Hedera Hashgraph mainnet.
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
@cryptair/mcp-serverclaude mcp add cryptair-mcp-server -e 'CRYPTAIR_API_KEY=<your cryptair_api_key>' -e 'CRYPTAIR_EMAIL=<CRYPTAIR_EMAIL>' -e 'CRYPTAIR_BASE_URL=https://www.cryptair.io' -- npx -y @cryptair/mcp-server@0.1.1
{
"mcpServers": {
"cryptair-mcp-server": {
"command": "npx",
"args": [
"-y",
"@cryptair/mcp-server@0.1.1"
],
"env": {
"CRYPTAIR_API_KEY": "<your cryptair_api_key>",
"CRYPTAIR_EMAIL": "<CRYPTAIR_EMAIL>",
"CRYPTAIR_BASE_URL": "https://www.cryptair.io"
}
}
}
}
Variables d'environnement
CRYPTAIR_API_KEYsecret Optional. Pre-configured Cryptair API key. If unset, the agent can call register_agent at runtime to self-register and the key is silently stored at ~/.cryptair/credentials.json.CRYPTAIR_EMAILOptional. Email used as fallback when submit_attestation auto-provisions a counterparty account.CRYPTAIR_BASE_URLOptional. Override the API base URL for self-hosted or staging environments. Defaults to https://www.cryptair.io.
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
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." |
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.pdfso we have a timestamped receipt."
"Send
~/Documents/contract.pdfto 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.pdfmatches 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)
- The MCP server hashes the file locally with SHA-256.
- The hash is sent to Cryptair, which writes it to a Hedera Consensus Service topic.
- You get back a Hedera transaction ID, consensus timestamp, and a public certificate URL.
- 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)
- Agent A initiates with a document hash and counterparty name. Cryptair returns a shareable URL.
- Agent A sends the URL to Agent B via any channel (email, Slack, etc.).
- Agent B opens the URL and submits the file they have. Their MCP server hashes it locally.
- 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
Questions fréquentes
Qu'est-ce que io.github.Syronius/cryptair-mcp-server ?
Tamper-evident attestation tools for AI agents — on-chain receipts on Hedera Hashgraph mainnet.
Comment installer io.github.Syronius/cryptair-mcp-server ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add cryptair-mcp-server -e 'CRYPTAIR_API_KEY=<your cryptair_api_key>' -e 'CRYPTAIR_EMAIL=<CRYPTAIR_EMAIL>' -e 'CRYPTAIR_BASE_URL=https://www.cryptair.io' -- npx -y @cryptair/mcp-server@0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.Syronius/cryptair-mcp-server ?
Oui. Il attend CRYPTAIR_API_KEY, à renseigner dans sa configuration.
io.github.Syronius/cryptair-mcp-server est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.Syronius/cryptair-mcp-server ?
Il est publié par Syronius. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.