Skip to content
mcp/skillhub

Waxseal MCP Server

by degenlegion-comio.github.degenlegion-com/waxsealv1.0.2

On-chain Ed25519 identity for AI agents: verify seals by fingerprint, validate document signatures and gate irreversible actions behind human-signed approvals.

2Node.jsstdioofficial registry

context tax

queued

security

queued

cold start

queued

freshness

Slowing3mo ago

Install Waxseal MCP server

Install in Claude Code

claude mcp add waxseal -e WAXSEAL_PRIVATE_KEY_PEM='<waxseal-private-key-pem>' -- npx -y @waxseal/mcp

Configuration

VariableRequiredSecretDescription
WAXSEAL_PRIVATE_KEY_PEM—yesEd25519 private key PEM — required only for waxseal.document.sign and waxseal.approval.create. The three verify tools and waxseal.info work without any key.

Freshness

Slowing — last maintenance signal 3mo ago. The newest of the signals below sets the band.

  1. Last commit (default branch)

    2026-07-07 · 3mo ago · GitHub

  2. Latest release

    2026-07-05 · 3mo ago · GitHub · v1.0.1

  3. Package published

    no data · npm/PyPI

  4. Registry entry updated

    2026-06-28 · 3mo ago · official registry · v1.0.2

FAQ

›How do I install the Waxseal MCP server in Claude Code?

Run: claude mcp add waxseal -e WAXSEAL_PRIVATE_KEY_PEM='<waxseal-private-key-pem>' -- npx -y @waxseal/mcp. For Cursor, VS Code, Claude Desktop and Windsurf, use the install tabs above.

›Does Waxseal require an API key?

Yes. It expects WAXSEAL_PRIVATE_KEY_PEM, of which 1 is a secret.

›Can I use Waxseal as a remote (hosted) MCP server?

No hosted endpoint is published; it runs locally over stdio.

›Is Waxseal in the official MCP registry?

Yes, as io.github.degenlegion-com/waxseal.