mcpField
W
Wax Seal

Wax Seal

Local
github.com/degenlegion-comDeveloper Tools2Updated 17w ago

About Wax Seal

Wax Seal provides identity and signature verification for apps and AI agents, with an SDK and an MCP server. Its tools can verify on-chain identities and Ed25519 signatures, and create or validate human approval tokens for gated actions.

Key features

  1. 01Verify on-chain identities
  2. 02Validate Ed25519 signatures
  3. 03Create and verify approval tokens
  4. 04Sign documents
  5. 05Verify webhook signatures

Use cases

  1. 01Check an identity before an agent action
  2. 02Require human approval for high-risk actions
  3. 03Add verified identity badges to content

Configuration

Local server config is the same for every client. Copy it into your client’s MCP config file.

mcp.json · Universal config
{
"mcpServers": {
"waxseal-sdk": {
"command": "npx",
"args": [
"-y",
"@waxseal/mcp"
],
"env": {
"WAXSEAL_PRIVATE_KEY_PEM": "<WAXSEAL_PRIVATE_KEY_PEM>"
}
}
}
}
Run commandnpx -y @waxseal/mcp
Environment variables to set
WAXSEAL_PRIVATE_KEY_PEMSecretEd25519 private key PEM — required only for waxseal.document.sign and waxseal.approval.create. The three verify tools and waxseal.info work without any key.

Local servers need a runtime on your machine (e.g. Node.js 18+). Config file locations differ by client; see your client’s docs.

Packages
npm@waxseal/mcp1.0.2

Tools

6

Saved tool list · updated 3w ago

This tool takes no parameters.

Details

From the project README

WaxSeal SDK

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

PackageWhat it isInstall
@waxseal/verifyBrowser + Node SDK — verify identities, validate signatures, embed badges, verify webhooksnpm install @waxseal/verify
@waxseal/mcpMCP server for Claude, Cursor, Windsurf, and VS Code — verify identities, sign documents, gate AI actions with human approvalsnpx @waxseal/mcp

@waxseal/mcp — for AI agents

Smithery npm

Give Claude, Cursor, Windsurf, or VS Code Copilot a cryptographic identity layer in under two minutes.

{
  "mcpServers": {
    "waxseal": {
      "command": "npx",
      "args": ["-y", "@waxseal/mcp"],
      "env": {
        "WAXSEAL_PRIVATE_KEY_PEM": "-----BEGIN PRIVATE KEY-----\n<your key>\n-----END PRIVATE KEY-----"
      }
    }
  }
}

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:

ToolWhat it doesKey needed?
waxseal.infoPlatform overview, tiers, and tool guideNo
waxseal.identity.verifyLook up fingerprint → name, chain, wallet, statusNo
waxseal.signature.verifyConfirm an Ed25519 signature against an on-chain keyNo
waxseal.approval.verifyValidate a human approval token before executingNo
waxseal.document.signSign any content with your WaxSeal private keyYes
waxseal.approval.createCreate a signed, time-limited approval tokenYes

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
npm install @waxseal/verify

Works in React, Vue, Node.js, n8n, serverless functions, and any runtime with fetch.

WaxSeal examples

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
import { verifySeal } from "@waxseal/verify";

const seal = await verifySeal({ fingerprint: "a1b2c3d4..." });

if (seal.valid && seal.onChain) {
  console.log(seal.displayName, "·", seal.chain);
  // "Ada Lovelace · base"
}

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
const seal = await verifySeal({
  fingerprint: "a1b2c3d4...",
  message:     "I approve this transfer.",
  signature:   "base64url...",
});

if (seal.valid && seal.onChain && seal.signatureValid) {
  // Cryptographic proof — no password, no session token
}

React Badge
import { WaxSealBadge } from "@waxseal/verify/badge";

<WaxSealBadge fingerprint="a1b2c3d4..." />

Or build your own:

import { useEffect, useState } from "react";
import { verifySeal, type VerifyResult } from "@waxseal/verify";

export function SealBadge({ fingerprint }: { fingerprint: string }) {
  const [seal, setSeal] = useState<VerifyResult | null>(null);

  useEffect(() => {
    let active = true;
    verifySeal({ fingerprint }).then((r) => active && setSeal(r));
    return () => { active = false; };
  }, [fingerprint]);

  if (!seal?.valid || !seal.onChain) return null;

  return (
    <a href={`https://waxseal.id/seal/${seal.fingerprint}`} target="_blank" rel="noopener noreferrer">
      ✦ {seal.displayName ?? seal.fingerprint.slice(0, 8)}
    </a>
  );
}

HTML Embed (no build step)
<script src="https://waxseal.id/embed.js"></script>
<span data-wax-seal="YOUR_64_CHAR_FINGERPRINT"></span>

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
import { verifyWebhookSignature, isWaxSealWebhookEvent } from "@waxseal/verify/webhooks";

app.post("/webhook/waxseal", express.raw({ type: "*/*" }), (req, res) => {
  const valid = verifyWebhookSignature({
    body:      req.body,
    signature: String(req.headers["x-waxseal-signature"]),
    secret:    process.env.WAXSEAL_WEBHOOK_SECRET,
  });

  if (!valid) return res.status(401).send("Invalid signature");

  const event = JSON.parse(req.body.toString());

  if (isWaxSealWebhookEvent(event, "seal.minted")) {
    console.log("New seal:", event.data.fingerprint, "on", event.data.chain);
  }

  res.sendStatus(200);
});

Webhook events

EventWhen it fires
seal.verifiedA seal was verified via the API
seal.mintedA new seal NFT was minted on-chain
seal.updatedSeal name, avatar, or metadata changed
seal.subscription.startedA seal holder started a paid subscription
seal.subscription.endedA subscription expired or was cancelled
challenge.approvedA login challenge was verified — user authenticated

REST API — no SDK, no key required
POST https://api.waxseal.id/v1/verify
Content-Type: application/json

{
  "fingerprint": "<64-char hex>",
  "message":     "...",
  "signature":   "..."
}
{
  "valid": true,
  "onChain": true,
  "chain": "base",
  "displayName": "Ada Lovelace",
  "walletAddress": "0x…",
  "signatureValid": true,
  "verifiedAt": "2026-01-01T00:00:00Z"
}

Works with everything
StackHow
React / Vue / Sveltenpm install @waxseal/verify
Node.js / ExpressSame package + webhook helper
n8nHTTP Request node → REST API, or npm package in Code node
Make.comHTTP module → REST API
ZapierWebhook by Zapier trigger
PHP / Python / GoPlain HTTP POST to the REST API
Static HTML / CMSTwo-line embed.js snippet
Claude / Cursor / Windsurf / VS Code@waxseal/mcp

VerifyResult type
type VerifyResult = {
  valid: boolean;
  fingerprint: string;
  onChain: boolean;
  chain?: "ethereum" | "base" | "bnb";
  walletAddress?: string;
  displayName?: string;
  publicKeyConfirmed?: boolean;
  signatureValid?: boolean;
  verifiedAt?: string;
  error?: string;
};

MIT © Wax Seal

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.