# degenlegion-com/waxseal-sdk [Health: Active]

**Category:** 🔑 Cryptography  
**Repository:** https://github.com/degenlegion-com/waxseal-sdk  
**GitHub Stars:** 1  
**npm Downloads (last month):** 600  
**Views:** 3  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/degenlegion-com-waxseal-sdk

## Description
On-chain Ed25519 identity for AI agents — verify seals by fingerprint, validate document signatures, and gate irreversible actions behind human-signed approval tokens. Hosted at api.waxseal.id/mcp; local install (npx @waxseal/mcp) for signing.

## Claude Desktop Quick Installation
Install path detected from listing signals. Uses `npx` (confidence: high):

```json
"mcpServers": {
  "waxseal-sdk": {
    "command": "npx",
    "args": ["-y","@waxseal/mcp"],
    "env": {
      "WAXSEAL_PRIVATE_KEY_PEM": ""
    }
  }
}
```

**Requires environment variables:** `WAXSEAL_PRIVATE_KEY_PEM` — the values above are empty placeholders; fill in real credentials before running (see the repository for what each one is for).

## Documentation

## What degenlegion-com/waxseal-sdk MCP server does

The degenlegion-com/waxseal-sdk MCP server gives compatible AI clients access to WaxSeal’s Ed25519 identity and signature functions. A WaxSeal identity is represented by a 64-character fingerprint and has an on-chain record. Agents can use the server to look up an identity, check document signatures, validate approval tokens, sign content, and create approval tokens.

The server is aimed at workflows where an agent needs cryptographic evidence before proceeding. For example, an agent can verify who controls a fingerprint, confirm that a document was signed by the corresponding on-chain key, or check a human approval token before executing an irreversible operation.

## How it works

The server exposes six MCP tools:

- `waxseal.info` returns platform, tier, and tool information.
- `waxseal.identity.verify` resolves a fingerprint to identity details such as name, chain, wallet, and status.
- `waxseal.signature.verify` checks an Ed25519 signature against an on-chain key.
- `waxseal.approval.verify` validates a human approval token.
- `waxseal.document.sign` signs content with the configured WaxSeal private key.
- `waxseal.approval.create` creates a signed approval token with a time limit.

The first four tools are verification or information operations and work without local key configuration. The two signing tools use the private key supplied through `WAXSEAL_PRIVATE_KEY_PEM`. The hosted MCP endpoint is available at `https://api.waxseal.id/mcp` for HTTP-capable clients.

## Setup and configuration

For a local process, run the package with `npx -y @waxseal/mcp`. An MCP client configuration can set `WAXSEAL_PRIVATE_KEY_PEM` to a PEM-encoded private key when document signing or approval creation is needed. Keep this value private; verification-only use does not need it.

The README identifies Claude, Cursor, Windsurf, and VS Code Copilot as supported client environments. Alternatively, configure the client to connect to the hosted endpoint instead of starting a local process. The hosted option is intended for clients that support HTTP-based MCP connections.

## Tools and capabilities

The degenlegion-com/waxseal-sdk MCP server covers two related jobs. First, it supports identity and signature verification using a fingerprint, signed content, or an approval token. Second, it lets an agent act as a WaxSeal holder by signing content and producing approval tokens, provided the local private key is available.

These operations can support passwordless identity checks, document approval flows, verified-agent workflows, and action gates that require a human-signed authorization. The material specifically describes approval tokens as time-limited, so consumers should validate them before carrying out the protected action.

## Limitations and notes

Signing is not available without a WaxSeal private key, while verification tools do not require that key. The README does not document additional local configuration variables, client-specific setup details, or the precise request and response schemas for each MCP tool. The repository also contains the separate `@waxseal/verify` browser and Node SDK, but that package is distinct from the MCP server package.

The degenlegion-com/waxseal-sdk MCP server is released under the MIT license. The provided material does not describe paid requirements for the MCP endpoint or local package, and it states that the related REST API requires no key.

_Full upstream README: https://allmcps.com/mcp/degenlegion-com-waxseal-sdk/readme_