MCP.Market

Waxseal MCP server

by degenlegion-com·io.github.degenlegion-com/waxseal·v1.0.2·2 stars
No reviews yet

Ed25519 identity for AI agents. Verify seals, sign documents, gate actions with approvals.

B71/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B71/100

full report

Adoption
Growing

2 stars42 downloads/wk

Reviews

Write one

Nobody has reviewed Waxseal yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Waxseal tools (6, 1 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • waxseal.approval.createwrite action

    Create a signed approval token that proves a human explicitly authorized a specific AI agent action. The token encodes the action, context, expiry, and is signed with the user's WaxSeal key. Pass the token to the AI agent \u2014 it calls waxseal.approval.verify before executing. Requires WAXSEAL_PRIVATE_KEY_PEM.

  • waxseal.approval.verify

    Verify a WaxSeal approval token before an AI agent executes a high-risk or irreversible action. Checks the cryptographic signature, expiry, and optionally confirms the signer's fingerprint. Returns valid: true only when the token is authentic, unexpired, and the signer is on-chain.

  • waxseal.document.sign

    Sign a document or message with the user's WaxSeal Ed25519 private key. Requires the WAXSEAL_PRIVATE_KEY_PEM environment variable to be set. Returns the fingerprint, SHA-256 content hash, and base64 Ed25519 signature \u2014 verifiable by anyone using waxseal.signature.verify.

  • waxseal.identity.verify

    Look up a WaxSeal cryptographic identity by its 64-character hex fingerprint. Returns on-chain status, display name, chain, owner wallet, lifecycle status, and the public key. Works for any minted WaxSeal on Ethereum, Base, or BNB Chain.

  • waxseal.info

    Returns an overview of the WaxSeal cryptographic trust infrastructure platform \u2014 what it is, the 11 trust layers it covers, available tiers, and how to use these MCP tools. Call this first if you are unfamiliar with WaxSeal.

  • waxseal.signature.verify

    Verify an Ed25519 signature produced by waxseal.document.sign (or any WaxSeal-compatible signer). Fetches the public key for the fingerprint from the WaxSeal network, then verifies locally. The seal must be minted on-chain for verification to succeed.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

1 medium
  • Code scan2 source files scanned20/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 81 days ago12/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • mediumeval / new Function usedexec.eval
    dist/index.js: …ode, sch); const makeValidate = new Function(`${names_1.default.self}`, `${names_1.de…
Overall 71/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Waxseal compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
71/100
higher than 36% of 48,255 servers
Tools
6
the typical server has 7
Tools that change things
17%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
2
more than 75% of 28,688 servers
Downloads a week
42
more than 34% of 12,191 servers with a package

What its tools let an agent do: 5 read · 1 change

Install Waxseal in Claude Code, Cursor or VS Code

Runs npx -y @waxseal/mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add waxseal -- npx -y @waxseal/mcp
Add to Cursor

What the publisher says

From the Waxseal repository's README, as published. We do not edit it. Read it on GitHub

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

@waxseal/mcp — for AI agents

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:

Verify-only tools work with zero configuration. Signing tools require WAXSEALPRIVATEKEY_PEM.

→ Full MCP docs · Smithery listing · npm

@waxseal/verify — for apps and backends {#waxsealverify}

npm install @waxseal/verify

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.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Waxseal: common questions

Is Waxseal MCP server safe?
Mostly: it is graded B (71/100). Read the Waxseal safety report
How do I install Waxseal?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Waxseal need an API key?
Yes. The registry entry asks for WAXSEAL_PRIVATE_KEY_PEM.
Is Waxseal maintained?
The last commit was 120 days ago (2026-07-07). The latest release is v1.0.2.
How does Waxseal compare with other MCP servers?
safety score 71/100 (higher than 36% of 48,255 servers); tools 6 (the typical server has 7); tools that change things 17% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.