
Waxseal
io.github.degenlegion-comPublished by GitHub account degenlegion-comv1.0.2Updated Oct 24, 2026
Ed25519 identity for AI agents. Verify seals, sign documents, gate actions with approvals.
Overview
Waxseal gives an AI assistant an Ed25519 identity layer: verify on-chain seals and signatures, sign documents, and create time-limited approval tokens.
- What you can do
- Look up a seal fingerprint to get its name, chain, wallet and status, and confirm an Ed25519 signature against an on-chain key (waxseal.identity.verify, waxseal.signature.verify). Validate a human approval token before an action is executed (waxseal.approval.verify). Sign arbitrary content with the configured private key (waxseal.document.sign). Create signed, time-limited approval tokens (waxseal.approval.create). Read a platform overview, tiers and tool guide (waxseal.info).
- When to use it
- Use it when an assistant needs to check that a person or seal is genuine before acting, or when you want a cryptographic record that the assistant signed a document or that a human approved a step. The verify tools work without any key, so it is cheap to try for identity checks alone.
- Requirements
- Runs locally over stdio via npx @waxseal/mcp (Node.js), or as a hosted HTTP endpoint. Signing and approval creation need the Ed25519 private key PEM in WAXSEAL_PRIVATE_KEY_PEM; the three verify tools and waxseal.info need no key. Verification relies on the Waxseal service and on-chain data, so network access is required.
Installation
In SourceWeft
- Open Waxseal in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
WaxSeal SDK
Cryptographic identity for the open web and for AI agents.
One Ed25519 keypair. One 64-character fingerprint. Permanent on-chain record.
waxseal.id · Developer Docs · Get your seal
[MIT License] [TypeScript] [REST API] [@waxseal/verify on npm] [@waxseal/mcp on npm] [Glama MCP score]
Packages
@waxseal/mcp — for AI agents
Give Claude, Cursor, Windsurf, or VS Code Copilot a cryptographic identity layer in under two minutes.
No install needed. Use the hosted server in any HTTP-capable MCP client:
https://api.waxseal.id/mcp
What the 6 tools give your agent:
Verify-only tools work with zero configuration. Signing tools require WAXSEAL_PRIVATE_KEY_PEM.
→ Full MCP docs · Smithery listing · npm
@waxseal/verify — for apps and backends {#waxsealverify}
[npm]
Works in React, Vue, Node.js, n8n, serverless functions, and any runtime with fetch.
Two modes, one fingerprint
Mode 1 · Badge Verification
"Does this WaxSeal exist and is it real?"
Confirm a seal is on-chain. No user interaction required — the fingerprint alone is enough.
Use cases
- ✦ Verified author badge on blog posts and articles
- ✦ Contributor identity on GitHub-style tools
- ✦ Publisher verification on CMS platforms
- ✦ Prove you created something before AI did
Mode 2 · Login & Action Approval
"Did this person sign this, right now?"
A signed challenge proves the key holder is present — replaces passwords, OTP, and email loops entirely.
Use cases
- ✦ Passwordless sign-in — no email, no OTP, no credentials to breach
- ✦ Approve a document or high-value transaction
- ✦ Gate a comment, post, or vote behind verified identity
- ✦ Issue an API key only to verified seal holders
- ✦ Automate identity checks in n8n / Make.com / Zapier
React Badge
Or build your own:
HTML Embed (no build step)
Email — script tags are blocked by mail clients. Use a plain link instead:
<a href="https://waxseal.id/seal/YOUR_FINGERPRINT">Verify my Wax Seal</a>
Webhook Verification
Webhook events
REST API — no SDK, no key required
Works with everything
VerifyResult type
MIT © Wax Seal
Source: README.md at commit 5e2e006
Tools
0Version history
1- v1.0.2LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts