Skip to main content
Glama
emiliaprotocol

emilia-mcp-server

Official
by emiliaprotocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to emilia-mcp-server

No user-submitted related servers found.

    Related Servers

    • Proof Layer MCP

      World-999-Labs
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides cryptographic governance receipts for AI agents, enabling pre-execution evaluation and signed verdicts (EXECUTE/BLOCK/REVIEW/SHADOW) with offline-verifiable audit trails.
      MIT

    • @sequesign/mcp

      Sequesign
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      64 npm
      Apache 2.0

    • Witnessed

      medtekki
      A
      license
      Not graded
      quality
      D
      maintenance
      Verifiable action receipts for AI agents — agents sign claims locally, an independent witness countersigns and timestamps, anyone can verify offline.
      15 npm
      MIT

    • Trust Gate MCP

      CWNApps
      A
      license
      A
      quality
      A
      maintenance
      Signed receipts for agent actions and a read-only-allowlist decision gate, as an MCP server. Ed25519, plus ML-DSA-65 when the post-quantum backend is available. gate_decision returns ALLOW, DENY or ESCALATE from action names and does not observe or block anything. verify_receipt takes expected_kid to pin which key signed. Seven tools.
      7
      118 PyPI
      Apache 2.0
    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 3 tools

    Disambiguation5/5

    Each tool addresses a distinct phase of the authorization lifecycle: requesting guard approval, polling signoff status, and verifying a stored trust receipt. There is no meaningful overlap because the inputs and outputs are clearly separated.

    Naming Consistency5/5

    All tools share the ep_ prefix and follow a consistent verb_noun pattern: guard_action, check_signoff, verify_receipt. The naming style is uniform and predictable.

    Tool Count5/5

    Three tools is at the lower end of the ideal range but perfectly scoped for this narrow authorization and verification domain. Each tool has a distinct responsibility and none feel redundant or missing.

    Completeness5/5

    The tool surface covers the full declared workflow: request authorization, poll for approval, and verify the trust receipt. Receipt consumption is intentionally outside the MCP server's choke point, so its absence is not a functional gap.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources