Skip to main content
Glama
degenlegion-com

WaxSeal

Official
by degenlegion-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to WaxSeal

Related Servers

  • Finch MCP

    finchagentic
    A
    license
    A
    quality
    B
    maintenance
    Enables AI assistants to retain persistent, searchable memory and versioned vaults, spawn and recall named agents with state and audit history, run automations, monitors, and deep research, and execute on-chain and web tasks across sessions. It can be installed alongside Claude Code, Cursor, Windsurf, Zed, Hermes, and other MCP clients, with vault and memory optionally run entirely on the user's machine.
    45
    21 npm
    MIT

  • mneme-ai

    patsa2561-art
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to operate through a local, signed boundary that blocks prompt injection and secret leakage, verifies outputs, preserves cross-session memory, and provides offline-verifiable receipts. It also exposes 900+ MCP tools for discoverable agent actions.
    7
    MIT

  • swiftsign-mcp

    shahdadk
    A
    license
    Not graded
    quality
    D
    maintenance
    E-signature for AI agents. An MCP server that lets Claude Code, Cursor, Zed, or any MCP-aware agent prepare, send, track, and seal legally binding documents without a human ever touching a mouse.
    6 npm
    MIT

  • AgentLens

    agentkitai
    A
    license
    A
    quality
    C
    maintenance
    AI-agent observability server whose distinguishing feature is a SHA-256 hash-chained, tamper-evident audit log with chain verification and signed export. Works with Claude Desktop, Cursor, and any MCP client.
    22
    2 npm
    23
    MIT
  • Aegis-ZK by aegis-zk

    Aegis-ZKofficial

    aegis-zk
    F
    license
    Not graded
    quality
    D
    maintenance
    On-chain trust verification for AI agent tools. Agents query skill attestations, audit levels, and risk scores before running third-party MCP servers, so you know what's safe before you execute.
    1
    -
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.4/5.0

Scored across 6 tools

Disambiguation5/5

Each tool has a uniquely defined purpose: creating/verifying approval tokens, signing/verifying documents, looking up identities, and returning platform info. No two tools overlap in functionality.

Naming Consistency5/5

All tools follow a strict waxseal.<category>.<action> naming scheme (e.g., waxseal.approval.create, waxseal.identity.verify). Verbs and categories are consistently applied.

Tool Count5/5

6 tools cover the essential operations of a cryptographic trust platform: identity, signatures, approvals, and info. The number is well-balanced and not excessive or insufficient.

Completeness4/5

The tool set covers the core workflow—sign, verify, approve, lookup identity, and get info. A minor gap is the lack of revocation or listing operations, but the primary use cases are addressed.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources