Productivity · Local MCP server
Waxseal
Ed25519 identity for AI agents. Verify seals, sign documents, gate actions with approvals.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.degenlegion-com/waxseal- Version
- 1.0.2
- Status
- Active
- Category
- productivity
- Transport
- stdio (local process)
- Package
- npm
- Published
- 2026-06-28
- Updated
- 2026-06-28
- Publisher
- degenlegion-com (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/degenlegion-com) · how
- Repository
- github.com/degenlegion-com/waxseal-sdk
- Source
- Registry API entry
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @waxseal/mcp | 1.0.2 | stdio |
How to connect Waxseal
Waxseal runs locally from a Node.js package published to the npm registry: @waxseal/mcp version 1.0.2. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @waxseal/mcp@1.0.2. It reads the environment variable WAXSEAL_PRIVATE_KEY_PEM (secret); set it in the client's configuration for this server.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"waxseal": {
"command": "npx",
"args": [
"-y",
"@waxseal/mcp@1.0.2"
],
"env": {
"WAXSEAL_PRIVATE_KEY_PEM": "<secret>"
}
}
}
}Derived from the registry entry, not tested here. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| WarpLinkLink infrastructure for mobile teams: deep links, install attribution, and real-time analytics. | Remote · HTTPLive check: sign-in required |
| WASync - WhatsApp Platform APIWhatsApp for your app or AI agent over OAuth2 - the same connections WASync runs inside your CRM. | Remote · HTTPLive check: ✗ no handshake |
| waterr.aiList WaterrAI scenarios, fetch AI-run meetings, and pull rubric-scored analyses. | Remote · HTTPLive check: sign-in required |
| WavedashWavedash docs and workflow guidance for building and publishing browser games. | Remote · HTTPLive check: ✓ handshake |
| waymark.networkQuery 17,000+ verified task routes with known gotchas and API drift alerts. Free keyless reads. | Remote · HTTPLive check: ✓ handshake |
| waystation.aiToolbox to connect your LLM to popular productivity tools such as Monday, AirTable, Slack. | Remote · HTTP, SSELive check: ✗ no handshake |
| WazapiOperate WhatsApp Business: conversations, contacts, chatbot flows, templates, CRM and store. | Remote · HTTPLive check: sign-in required |
| wazionapps MCP-SERVER244 WhatsApp Business AI tools for messaging, automation, marketing, CRM and Shopify. | Local · stdio |