mcpbeat Sign in

Waxseal MCP Server

by degenlegion-com Your server? Claim it
local only

Waxseal runs on your own machine — the client starts it, so there is no endpoint to ping. 49 installs a week from npm. Last commit 7 Jul 2026.

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

Installs per day peak 28 · avg 9 · +20% w/w
a month agotoday
49
Installs / week
npm · @waxseal/mcp
1
Stars
0 open issues
7 Jul 2026
Last commit
0 releases in 90 days
MIT
License
TypeScript

What the code does

We read the source, 20 h ago · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Package points at a different repository degenlegion-com/waxseal-sdk
пакет @waxseal/mcp ссылается на waxseal/mcp

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.

run in your terminal
claude mcp add waxseal -- npx -y @waxseal/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "waxseal": {
      "args": [
        "-y",
        "@waxseal/mcp"
      ],
      "command": "npx"
    }
  }
}
~/.codex/config.toml
[mcp_servers.waxseal]
command = "npx"
args = ["-y", "@waxseal/mcp"]
.cursor/mcp.json
{
  "mcpServers": {
    "waxseal": {
      "args": [
        "-y",
        "@waxseal/mcp"
      ],
      "command": "npx"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "waxseal": {
      "args": [
        "-y",
        "@waxseal/mcp"
      ],
      "command": "npx"
    }
  }
}

This one needs environment variables set before it will start: WAXSEAL_PRIVATE_KEY_PEM (Ed25519 private key PEM — required only for waxseal.document.sign and waxseal.approval.create. The three verify tools and waxseal.info work without any key.). The author declared them in the registry entry; get the values from the project itself.

Alternatives to Waxseal

same job, measured the same way
Groupdocs Signature MCP
by groupdocs-signature

MCP server for GroupDocs.Signature — sign, search and verify document signatures via AI agents.

local only
MCP Onfido
by codespar

MCP server for Onfido — global identity verification + KYC: applicants, documents, checks, workflows

21 installs/wk local only
Kamy
by kamy

Document API for AI-native software: render PDFs, e-sign, PAdES-seal, and verify.

59 tools answering
MCP Jumio
by codespar

MCP server for Jumio — global identity verification + KYX: documents, liveness, AML screening

22 installs/wk local only
Groupdocs Annotation MCP
by groupdocs-annotation

MCP server for GroupDocs.Annotation — add, list, update, remove document annotations via AI agents.

local only
Signforge
by kumarprobeops

Send documents for e-signature from AI agents. Upload, sign, and download PDFs.

39 installs/wk local only
Verifa
by verifa-solutions

Identity verification, document checks, sanctions/PEP screening and case review as agent tools.

20 installs/wk answering
Grist MCP Server
by gwhthompson

11 tools for managing Grist documents with AI

149 installs/wk local only

Waxseal — questions

Answers built from our own checks of this server.

Why is there no uptime for Waxseal?
Waxseal runs on your own machine over stdio — there is no network address to reach, so uptime cannot be measured for it by anyone. What can be measured is adoption: the npm package @waxseal/mcp was installed 49 times last week.
How do I connect Waxseal?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It runs locally, so the command pulls @waxseal/mcp straight from npm; nothing to host, nothing to sign up for.
How many people use Waxseal?
The npm package @waxseal/mcp was installed 49 times in the last week. Week over week that is +20%. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Waxseal open source?
Yes — it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.