Skip to main content
Glama
Legitifier

legitify-mcp

Official
by Legitifier
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Hybrid

Related Servers

Alternatives to legitify-mcp

No user-submitted related servers found.

    Related Servers

    • final-approval

      finalapproval
      A
      license
      A
      quality
      D
      maintenance
      Human-in-the-loop approval gate for AI agents. Your agent calls submit_approval before any irreversible action; a human reviews on a branded page; a signed webhook fires back with the decision.
      1
      1
      MIT

    • Cryptair MCP Server

      Syronius
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to certify documents, prove agreements, and verify counterparty claims with on-chain receipts on Hedera Hashgraph. Provides tools for document certification, two-party attestation, and agent registration with zero-config setup.
      6
      23 npm
      MIT

    • actionproof

      Burakfenerci5
      A
      license
      A
      quality
      B
      maintenance
      Gives AI agents verifiable, tamper-evident receipts for their actions — attest_action signs a cryptographic receipt for what the agent did (email sent, payment made, form filed), verify_receipt checks it offline, get_identity returns the agent's did:key. Sign locally, verify anywhere, zero backend.
      3
      53 npm
      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
      54 npm
      Apache 2.0

    • agenticrail-mcp

      MSMD-RUA
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides tools to evaluate an AI agent's step before execution, returning signed ALLOW/DENY receipts, and to verify receipt chain integrity.
      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

    A3.5/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools have clear boundaries: submit, review, list, and policy are distinct. get_attestation_status and get_pending_request_details both retrieve information by id, but the descriptions separate status lookup from full details reasonably well.

    Naming Consistency4/5

    All tool names use a lowercase snake_case verb_noun pattern, which is consistent. Minor inconsistency exists between attestation_request, pending_request, and request as object names, but the verb pattern keeps the set predictable.

    Tool Count5/5

    Six tools is well-scoped for an attestation workflow. Each tool maps to a meaningful step in the request lifecycle without unnecessary duplication.

    Completeness4/5

    The core submit, review, status, list, and detail flows are covered. Missing capabilities like canceling a request or resubmitting after needs_info are notable but not fatal, since the main workflow is fully represented.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources