degenlegion-com/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
---
Packages
| Package | What it is | Install |
|---------|-----------|---------|
| @waxseal/verify | Browser + Node SDK — verify identities, validate signatures, embed badges, verify webhooks | npm install @waxseal/verify |
| @waxseal/mcp | MCP server for Claude, Cursor, Windsurf, and VS Code — verify identities, sign documents, gate AI actions with human approvals | npx @waxseal/mcp |
---
@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:**
| Tool | What it does | Key needed? |
|------|-------------|:-----------:|
| waxseal.info | Platform overview, tiers, and tool guide | No |
| waxseal.identity.verify | Look up fingerprint → name, chain, wallet, status | No |
| waxseal.signature.verify | Confirm an Ed25519 signature against an on-chain key | No |
| waxseal.approval.verify | Validate a human approval token before executing | No |
| waxseal.document.sign | Sign any content with your WaxSeal private key | **Yes** |
| waxseal.approval.create | Create a signed, time-limited approval token | **Yes** |
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}
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:
> Verify my Wax Seal
---
Webhook Verification
**Webhook events**
| Event | When it fires |