io.github.degenlegion-com/waxseal
NPM · @WAXSEAL/MCP · SCANNED SEP 20
Ed25519 identity for AI agents. Verify seals, sign documents, gate actions with approvals.
Available components
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 → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 34 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 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 Management93
- Stability observed for 28 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.degenlegion-com/waxseal MCP server?
io.github.degenlegion-com/waxseal runs locally as an npm package, launched with npx -y @waxseal/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @waxseal/mcp
claude mcp add degenlegion-com-waxseal -- npx -y @waxseal/mcp
{
"mcpServers": {
"degenlegion-com-waxseal": {
"command": "npx",
"args": [
"-y",
"@waxseal/mcp"
]
}
}
} {
"servers": {
"degenlegion-com-waxseal": {
"command": "npx",
"args": [
"-y",
"@waxseal/mcp"
]
}
}
} codex mcp add degenlegion-com-waxseal -- npx -y @waxseal/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"degenlegion-com-waxseal": {
"type": "local",
"command": [
"npx",
"-y",
"@waxseal/mcp"
],
"enabled": true
}
}
} openclaw mcp add degenlegion-com-waxseal --command npx --arg -y --arg @waxseal/mcp
mcp_servers:
degenlegion-com-waxseal:
command: "npx"
args: ["-y", "@waxseal/mcp"] {
"McpServers": {
"degenlegion-com-waxseal": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@waxseal/mcp"
]
}
}
} assistant mcp add degenlegion-com-waxseal -t stdio -c npx -a -y @waxseal/mcp
{
"mcpServers": {
"degenlegion-com-waxseal": {
"command": "npx",
"args": [
"-y",
"@waxseal/mcp"
]
}
}
} 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.
- 19 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 15 Sept 26 0
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
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 20 Sept 2026 · Analysed npm/@waxseal/mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
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.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Description of the action being approved (e.g. 'Deploy v2.1.0 to production', 'Transfer 500 USDC to vendor wallet 0xabc...'). |
| context | string | – | Additional parameters or context for the action (optional). |
| expires_in_minutes | number | – | Minutes 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.
| Name | Type | Req | Description |
|---|---|---|---|
| approval_token | string | yes | The base64-encoded approval token returned by waxseal.approval.create. |
| expected_fingerprint | string | – | If 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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The document text or data to sign. |
| description | string | – | Human-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.
| Name | Type | Req | Description |
|---|---|---|---|
| fingerprint | string | yes | 64-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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The original document text or data that was signed. |
| fingerprint | string | yes | 64-character hex fingerprint of the signer. |
| signature | string | yes | Base64 Ed25519 signature returned by waxseal.document.sign. |
No output schema declared.
No examples provided.
What is the io.github.degenlegion-com/waxseal MCP server?
io.github.degenlegion-com/waxseal is an MCP server listed in the public MCP registry as io.github.degenlegion-com/waxseal. Ed25519 identity for AI agents. Verify seals, sign documents, gate actions with approvals. This page covers its npm package (@waxseal/mcp).
Is the io.github.degenlegion-com/waxseal MCP server safe to use?
io.github.degenlegion-com/waxseal scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.degenlegion-com/waxseal MCP server expose?
io.github.degenlegion-com/waxseal exposes 6 tools: waxseal.info, waxseal.identity.verify, waxseal.document.sign, waxseal.signature.verify, waxseal.approval.create, waxseal.approval.verify. Their descriptions and schemas cost roughly 637 tokens of context every time the server is loaded.
Is the io.github.degenlegion-com/waxseal MCP server still maintained?
io.github.degenlegion-com/waxseal is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.degenlegion-com/waxseal MCP server under?
io.github.degenlegion-com/waxseal declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.