
Wax Seal
@degenlegion-com
About Wax Seal
Cryptographic identity verification for AI agents — verify on-chain seals, validate Ed25519 signatures, and gate high-risk actions with human-signed approvals.
Config
Add this server to your MCP-compatible client using the configuration below.
{
"mcpServers": {
"waxseal": {
"command": "npx",
"args": [
"-y",
"@waxseal/mcp"
],
"env": {
"WAXSEAL_PRIVATE_KEY_PEM": "<your-ed25519-private-key-pem>"
}
}
}
}Tools
6Returns 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.
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.
Sign a document or message with the user's WaxSeal Ed25519 private key. Requires WAXSEAL_PRIVATE_KEY_PEM (inline PEM) or WAXSEAL_KEY_FILE (path to PEM file) to be set. Returns the fingerprint, SHA-256 content hash, and base64 Ed25519 signature — verifiable by anyone using 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.
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 (inline PEM) or WAXSEAL_KEY_FILE (path to PEM file).
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.
Overview
What is Wax Seal?
Wax Seal is a cryptographic identity infrastructure for AI agents. Each seal is an Ed25519 keypair minted on-chain (Base, Ethereum, or BNB Chain), giving agents a tamper-evident way to verify identity, authenticate documents, and enforce human approval before executing irreversible actions.
How to use Wax Seal?
Use the provided MCP tools: call waxseal.info first, then use waxseal.identity.verify, waxseal.signature.verify, or waxseal.approval.verify. For signing documents or creating approval tokens, set the WAXSEAL_PRIVATE_KEY_PEM environment variable. The verify-only tools require no configuration.
Key features of Wax Seal?
- Ed25519 keypair minted on-chain (Base, Ethereum, BNB Chain)
- Look up any WaxSeal by 64-character hex fingerprint
- Verify Ed25519 signatures against a WaxSeal
- Verify human-signed approval tokens
- Sign content with your WaxSeal key (requires key)
- Create signed approval tokens for agents (requires key)
Use cases of Wax Seal?
- Verifying the identity of an AI agent before interaction
- Authenticating documents generated by an agent
- Enforcing human approval before executing irreversible actions
- Auditing agent actions via on-chain cryptographic proofs
FAQ from Wax Seal
What is a WaxSeal?
A WaxSeal is an Ed25519 keypair minted on a blockchain (Base, Ethereum, or BNB Chain), providing a cryptographic identity for AI agents.
Do I need a private key to use all tools?
No. The first four tools (info, identity.verify, signature.verify, approval.verify) require no private key. Only waxseal.document.sign and waxseal.approval.create need the WAXSEAL_PRIVATE_KEY_PEM environment variable.
How does human-in-the-loop approval work?
The agent creates an approval token via waxseal.approval.create, stores it, and before executing an action calls waxseal.approval.verify with the token. The action proceeds only if verification returns valid.
Where can I get a WaxSeal?
You can create a seal at waxseal.id/create.
What blockchains are supported?
Base
Frequently asked questions
What is a WaxSeal?
A WaxSeal is an Ed25519 keypair minted on a blockchain (Base, Ethereum, or BNB Chain), providing a cryptographic identity for AI agents.
Do I need a private key to use all tools?
No. The first four tools (info, identity.verify, signature.verify, approval.verify) require no private key. Only `waxseal.document.sign` and `waxseal.approval.create` need the `WAXSEAL_PRIVATE_KEY_PEM` environment variable.
How does human-in-the-loop approval work?
The agent creates an approval token via `waxseal.approval.create`, stores it, and before executing an action calls `waxseal.approval.verify` with the token. The action proceeds only if verification returns valid.
Where can I get a WaxSeal?
You can create a seal at [waxseal.id/create](https://waxseal.id/create).
What blockchains are supported?
Base
Basic information
More Developer Tools MCP servers
CodeSentinel
icohangar-opsCodebase health as MCP tools: dead code, circular dependencies, coupling, architectural drift.

Apiosk
obcraftAI-native payments for tools and APIs. Discover, pay for, execute, and publish monetized APIs directly from your agent, settled per call in USDC over x402, through the Model Context Protocol. payments · finance · x402 ·

CircleCI MCP Server
CircleCIManage CI/CD pipelines, debug failed builds, and optimize test suites directly from your AI agents - no terminal required. The CircleCI MCP Server is a remote server hosted by CircleCI that connects AI tools and agents

Codex Pets
astandrikPublic read-only MCP server for discovering, inspecting, installing, and sharing approved Codex-compatible animated pet packs.

discoverGPT
Joe MonastierodiscoverGPT is visualAI's unified MCP gateway for AI commerce, exposing 29 tools across four capabilities on one canonical product catalog: trimodal search (natural-language, precise-color, and image-similarity), AI cata
Comments