blocksign-mcp
Anchors e-signature agreements to the Bitcoin blockchain for cryptographic verification of signed documents.
Enables autonomous payment for agreement services using Stripe shared payment tokens and credit purchases.
Anchors e-signature agreements to the XRP Ledger, providing cryptographically provable audit trails for signed documents.
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
blocksign-mcp
A Model Context Protocol (MCP) server for blocksign.red — blockchain-anchored e-signatures.
Every signature blocksign produces is anchored to the XRP Ledger and Bitcoin, so agreements are cryptographically provable — not just asserted by a database. This MCP server lets AI agents create, send, negotiate, and verify legally binding agreements.
Endpoint
URL:
https://mcp.blocksign.red/mcpTransport: Streamable HTTP (MCP
2025-06-18, negotiates down to2024-11-05)Auth (account mode):
Authorization: Bearer bsk_agent_*— issue an agent-scoped key at https://blocksign.red/settings/api-keys
Related MCP server: swiftsign-mcp
No API key? Guest mode
Agents can drive multi-party signing with no account and no key — payment is
the identity. Call create_agreement with no Authorization header and pass:
payment— a Stripe shared payment token (spt_*)sender—{ "name": "...", "email": "..." }document+ 2+signers
blocksign charges the token, emails each signer a click-to-sign link, and
returns the signing URLs + a check-back status_url + the public
verification_url.
Tools
Tool | Description |
| One call: template + variables, Markdown, or base64 PDF → send to signers (individuals or companies) |
| Unified status: envelope state, per-signer status, verification URL |
| Recent agreements for the calling org |
| Contract templates (org-owned + platform public) |
| Public, no-auth cryptographic verification of the audit chain + anchors |
| Void an envelope before all parties sign |
| Render a template with variables (validate inputs before sending) |
| Upload text/Markdown → PDF, optional AI field detection |
| AI-detected signature/initials/date field positions |
| Plan, credit balance, usage, per-document pricing |
| Buy a credit pack (10/50/200) |
Agents can also pay autonomously — blocksign supports Stripe shared payment
tokens (spt_*) and x402, so a one-call create_agreement can create, pay,
and send with no human in the loop.
Discovery
MCP metadata:
https://api.blocksign.red/.well-known/mcp.jsonMCP server card (SEP-1649):
https://api.blocksign.red/.well-known/mcp/server-card.jsonA2A AgentCard:
https://a2a.blocksign.red/.well-known/agent-card.jsonllms.txt:https://blocksign.red/llms.txt
Quick start
# Point any MCP client at the hosted endpoint
npx @modelcontextprotocol/inspector https://mcp.blocksign.red/mcpAdd to your MCP client
{
"mcpServers": {
"blocksign": {
"type": "http",
"url": "https://mcp.blocksign.red/mcp",
"headers": { "Authorization": "Bearer bsk_agent_YOUR_KEY" }
}
}
}(For guest mode, omit the headers block and pass payment + sender in the
create_agreement call.)
Run it yourself
export BLOCKSIGN_API_URL=http://localhost:8085 # a running blocksign API
export MCP_PUBLIC_URL=http://localhost:8200/mcp
cargo runThen POST /mcp with JSON-RPC, sending your bsk_agent_* key as
Authorization: Bearer <key> (or using guest mode with payment).
About this repo
This is the MCP server component of blocksign.red, published for agent discoverability. The core platform (REST API, anchoring, worker services) remains closed-source.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
Send PDFs for e-signature from AI agents, with a public hash-chained evidence log anyone can verify
Send contracts for e-signature, track signing, get signed PDFs and audit trails, verify any PDF.
Free e-signature for humans and AI agents — zero-document PDF signing from hashes only.
Send AI-created PDFs for signature, track signers, and return verifiable document evidence.
Related MCP Servers
- AlicenseAqualityCmaintenanceDocument signing for AI agents. Send markdown or PDF for two-party e-signing with a single tool call — handles PDF generation, email verification, and SHA-256 certified delivery.217 npmMIT
- AlicenseNot gradedqualityDmaintenanceE-signature for AI agents. One unauthenticated call returns a sandbox API key (no account, no browser), then the agent can send documents for signature, check status, and download the sealed PDF plus Certificate of Completion.4 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage contract templates, draft agreements by filling in template variables and signers, send documents out for legally binding e-signature, and track signer status as signatures come in. It runs as a hosted remote server, so there is nothing to install or self-host.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents and developers to create, send, and follow up on contracts for e-signature, manage signers and templates, retrieve signed PDFs and audit trails, and verify PDF signatures. It keeps signing and declining in the hands of each signer through personal links.1MIT