Hashproof vs Sequesign
A side-by-side look at the Hashproof and Sequesign MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Hashproof for cryptography work as a local process; choose Sequesign for cryptography as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose Hashproof when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
get_template_requirements, preview_template, issue_credential.
Choose Sequesign when
- You need dedicated capabilities in the Cryptography domain.
- You prefer a local stdio subprocess transport.
- You want tools like
sequesign_start_session, sequesign_record_action, sequesign_record_approval.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | Cryptography | Cryptography |
| Quality signal | 60/100 · Good | 53/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | 1 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | 4 | 8 |
| Full listing | View Hashproof | View Sequesign |
Tools & capabilities
Hashproof tools 4
get_template_requirementsGet the required field keys and layout definition of an existing HashProof template. Free, no auth. Always call this before issuing with a template_slug you didn't create in this session.preview_templateRender a watermarked preview PDF from an INLINE template definition — free, nothing stored, no payment. Use this to iterate field positions (x, y, width, font_size) until the layout is right, then show the final PDF to the human for approval before issuing. page_width/page_height MUST match the background image's pixel dimensions. The PDF is written to a local file; if you can read PDFs, inspect it and adjust yourself.issue_credentialIssue a verifiable credential — COSTS $0.10 USDC (x402) or 1 API-key credit per call. Get explicit human approval before calling. Requires HASHPROOF_API_KEY or HASHPROOF_WALLET_PRIVATE_KEY in the MCP server env (if neither is set, the error explains both routes). With an API key the credential issues as the key's own entity: `issuer.slug` must match that entity or the call is rejected, so you cannot issue on behalf of another organization. The body follows the HashProof issueCredential schema: issuer{display_name,slug}, platform{display_name,slug}, holder{full_name}, context{type,title}, credential_type, title, values{...}, and optionally template_slug OR an inline template{...} (send only one). Returns id, verification_url, tx_hash and ipfs_cid. Full reference: https://hashproof.dev/skill.mdverify_credentialVerify an issued credential against three independent sources (database, IPFS, blockchain). Free, no auth. Returns status (active/revoked/expired/not_found), issuer verification and the credential data.
Sequesign tools 8
sequesign_start_sessionOpen a recording session (one signed action chain). Returns a `sessionId` (the receipt id) used by every other tool. Pass a `policyContext` object to bind the receipt to a policy (reaches `L3_POLICY_BOUND`). Optional `mode` (`direct`/`managed`) overrides the server default per session.sequesign_record_actionAppend a signed action to the chain. `evidence` is hashed and signed. Returns the `actionId`.sequesign_record_approvalAttach a locally signed approval for a recorded action (e.g. a human or agent reviewer signing off).sequesign_record_counterparty_attestationAttach a counterparty's signed confirmation of a recorded action (e.g. a vendor confirming an amount). The SDK derives the content binding from the attested action.sequesign_approve_receiptAttach an independently-witnessed **approval** to an *already-sealed* receipt (a deferred satellite). For a reviewer — human or another agent — signing off after the fact. The approver must be distinct from the recording agent.sequesign_countersign_receiptAttach an independently-witnessed **counterparty confirmation** to an *already-sealed* receipt (a deferred satellite), bound to a specific action.sequesign_finalizeSeal + witness the receipt and run the SDK's own verification. Closes the session.sequesign_verifyVerify a sealed receipt offline. Three modes: integrity self-check of the local package (default); third-party `external` check when you pass the witness's published keys; or pass `receiptUrl` to verify the broker-**stored** receipt (the authoritative copy carrying the registered identity), auto-fe…
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
Hashproof
{
"mcpServers": {
"hashproof": {
"command": "npx",
"args": [
"-y",
"hashproof-mcp"
]
}
}
}
Sequesign
{
"mcpServers": {
"sequesign": {
"command": "npx",
"args": [
"-y",
"@sequesign/mcp"
]
}
}
}
Frequently asked questions
Hashproof is categorized under Cryptography and uses a local stdio subprocess. Sequesign belongs to Cryptography and uses a local stdio subprocess. Pick Hashproof for cryptography work and Sequesign for cryptography.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
Hashproof has no declared pricing — check the project's own site. Sequesign has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add hashproof and sequesign as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Hashproof has a quality signal of 60/100 (Good) with 1 views, 0 installs and 1 GitHub stars. Sequesign has 53/100 (Good) with 0 views, 0 installs and 0 GitHub stars.