Skip to main content
Glama
Syronius

Cryptair MCP Server

by Syronius

submit_attestation

Complete a two-party attestation by submitting the attest_url you received. Verifies document match and records certified or tampered status on Hedera.

Instructions

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

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
emailNoOptional. If supplied and you don't have a Cryptair account yet, one will be auto-provisioned for you and stored locally. Recommended for agents that may want to initiate their own attestations later.
file_pathNoAbsolute path to the file you received. Will be SHA-256 hashed locally. Provide this OR document_hash.
attest_urlYesThe full URL the initiator sent you (e.g. https://www.cryptair.io/attest/<id>?token=<jwt>).
document_hashNo64-character hex SHA-256 of the document, if you already have it. Provide this OR file_path.
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

With no annotations, the description carries the full burden. It discloses that attest_url contains a one-time token, email triggers auto-provisioning with silent API key storage, and return values. Lacks mention of any destructive behavior but covers core behaviors well.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

Description is fairly long but well-structured with bullet points and sections. Information is front-loaded with purpose. Could be slightly more concise but overall efficient.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given 4 parameters, no output schema, and no annotations, the description covers return values, constraints, and behavioral details comprehensively. It provides enough context for an agent to use the tool correctly.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 100%, so baseline 3. The description adds context like the role of attest_url, file_path vs document_hash choice, and email auto-provisioning, but the schema already provides clear descriptions.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states it completes a two-party attestation as the counterparty, using a specific verb and resource. It distinguishes from siblings like initiate_attestation and check_attestation by focusing on the counterparty role.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines5/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description explicitly lists three specific use cases under 'USE WHEN you want to:' and explains that no Cryptair API key is needed, guiding proper tool selection.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/Syronius/cryptair-mcp-server'

If you have feedback or need assistance with the MCP directory API, please join our Discord server