ActSeal MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@ActSeal MCP issue a signed receipt for my deploy with input hash 0xabc and output hash 0xdef"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
ActSeal MCP
stdio MCP server for ActSeal — Ed25519-signed receipts for agent actions.
Tool | Purpose |
|
|
|
|
Honesty: best-effort signed log. Not legal evidence, not SOC2, not custody, not e-sign. Free 100 receipts/API-key/UTC-day; Starter $19/mo in USDC/USDT/ETH at https://actseal.xyz/pay.
Env
Var | Required | Example |
| yes* |
|
| yes* | free key via https://actseal.xyz/get-key |
* Legacy ACTIONRECEIPT_BASE / ACTIONRECEIPT_API_KEY still accepted.
Related MCP server: actionproof
Run
pnpm install
export ACTSEAL_BASE=https://actseal.xyz
export ACTSEAL_API_KEY=as_…
pnpm startCursor / Claude Desktop
{
"mcpServers": {
"actseal": {
"command": "npx",
"args": ["--yes", "tsx", "/ABSOLUTE/PATH/actseal-mcp/src/index.ts"],
"env": {
"ACTSEAL_BASE": "https://actseal.xyz",
"ACTSEAL_API_KEY": "YOUR_KEY"
}
}
}
}Links
Site: https://actseal.xyz
Docs: https://actseal.xyz/docs
OpenAPI: https://actseal.xyz/openapi.json
llms.txt: https://actseal.xyz/llms.txt
Docker / Glama
docker build -t actseal-mcp .
docker run -i --rm \
-e ACTSEAL_BASE=https://actseal.xyz \
-e ACTSEAL_API_KEY=YOUR_KEY \
actseal-mcpGlama listing: https://glama.ai/mcp/servers/arults/actseal-mcp (after submit + score).
glama.json lists maintainer arults.
Available Tools
2 toolsissue_receiptIssue ActSealA
Issue an Ed25519-signed ActSeal receipt for a tool action. Pass SHA-256 hex hashes of inputs/outputs — never raw secrets. Optional Idempotency-Key. Free tier only; x402 not live.
Inputs: action (required), inputs_hash (required), outputs_hash (required), policy_id, +1 more.
verify_receiptVerify ActSealARead-only
Verify a receipt by id (public). Returns valid/invalid, receipt payload, and issuer public key.
Inputs: id (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 2 tools
issue_receipt and verify_receipt have clearly opposite, non-overlapping purposes (creation vs. validation), and the descriptions reinforce the distinction. An agent can select between them with no ambiguity.
Both tools follow the same snake_case verb_noun pattern (issue_receipt, verify_receipt). The naming is fully predictable and symmetric.
Two tools is thin for a general-purpose server, but for the narrow domain of issuing and verifying signed receipts the pair is reasonably scoped. It sits just under the typical comfortable range rather than being an extreme mismatch.
The core lifecycle (issue then verify) is fully covered with no dead ends for the primary workflow. Minor gaps exist, such as listing receipts or revoking/invalidating one, which agents would have to work around.
Related MCP Connectors
Issue & verify signed (ed25519), hash-chained, timestamped provenance receipts for agent actions.
Post-quantum, tamper-evident receipts for agent actions. Ed25519 + ML-DSA-65, offline verify.
Issue signed receipts for AI agent actions; verify any receipt offline - free, no account.
Governed AI actions with signed, verifiable receipts: free keyless reads, human-approved writes.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to sign and verify actions with ML-DSA-65 digital signatures, providing tamper-proof receipts that can be verified offline without any secrets.MIT
- AlicenseAqualityDmaintenanceGives AI agents verifiable, tamper-evident receipts for their actions — attest_action signs a cryptographic receipt for what the agent did (email sent, payment made, form filed), verify_receipt checks it offline, get_identity returns the agent's did:key. Sign locally, verify anywhere, zero backend.3MIT
- AlicenseAqualityCmaintenanceProvides tools to issue, verify, and export cryptographically signed receipts for AI agent actions, enabling tamper-proof audit trails for compliance with regulations like the EU AI Act.446 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to validate deliverables (JSON, ZIP, PDF, DOCX) against signed contracts, generating verifiable receipts with Ed25519 signatures.-