Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

io.github.degenlegion-com/waxseal

NPM · @WAXSEAL/MCP · SCANNED AUG 3

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

Available components

+23 this week 69 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security86
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 637 tokens (~106/item across 6 items; 6 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @waxseal/mcp

# add to Claude Code
claude mcp add degenlegion-com-waxseal -- npx -y @waxseal/mcp
# add to Codex CLI
codex mcp add degenlegion-com-waxseal -- npx -y @waxseal/mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "degenlegion-com-waxseal": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@waxseal/mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add degenlegion-com-waxseal --command npx --arg -y --arg @waxseal/mcp
# ~/.hermes/config.yaml
mcp_servers:
  degenlegion-com-waxseal:
    command: "npx"
    args: ["-y", "@waxseal/mcp"]
// mcp.json
{
  "mcpServers": {
    "degenlegion-com-waxseal": {
      "command": "npx",
      "args": [
        "-y",
        "@waxseal/mcp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 2 Aug 26 +64
    • Provenance: unverified → fail security
    • Install scripts: unverified → pass security
    • Known CVEs: unverified → partial security
    • Malware scan: unverified → pass security
    • Security disclosure: fail → unverified functional
    • Tool coverage: unverified → 100 functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Stability: unverified → 0.23 functional
    • Schema quality: unverified → excellent functional
    • Licence: MIT functional
  • 1 Aug 26 −23
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 46

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 3 Aug 2026 · Analysed npm/@waxseal/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~637 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.

Tool Tokens
waxseal.approval.create ~156

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 — it calls waxseal.approval.verify before executing. Requires WAXSEAL_PRIVATE_KEY_PEM.

NameTypeReqDescription
actionstringyesDescription of the action being approved (e.g. 'Deploy v2.1.0 to production', 'Transfer 500 USDC to vendor wallet 0xabc...').
contextstringAdditional parameters or context for the action (optional).
expires_in_minutesnumberMinutes until the approval expires. Defaults to 10.

No output schema declared.

No examples provided.

waxseal.approval.verify ~114

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.

NameTypeReqDescription
approval_tokenstringyesThe base64-encoded approval token returned by waxseal.approval.create.
expected_fingerprintstringIf provided, the verification also confirms the token was signed by this specific fingerprint.

No output schema declared.

No examples provided.

waxseal.document.sign ~104

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 — verifiable by anyone using waxseal.signature.verify.

NameTypeReqDescription
contentstringyesThe document text or data to sign.
descriptionstringHuman-readable label for what is being signed (optional, informational only).

No output schema declared.

No examples provided.

waxseal.identity.verify ~97

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.

NameTypeReqDescription
fingerprintstringyes64-character hex fingerprint — the SHA-256 of the raw Ed25519 public key. Also accepted with a 0x prefix.

No output schema declared.

No examples provided.

waxseal.info ~56

Returns an overview of the WaxSeal cryptographic trust infrastructure platform — 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

waxseal.signature.verify ~110

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.

NameTypeReqDescription
contentstringyesThe original document text or data that was signed.
fingerprintstringyes64-character hex fingerprint of the signer.
signaturestringyesBase64 Ed25519 signature returned by waxseal.document.sign.

No output schema declared.

No examples provided.