Skip to main content
Glama
SaravananJaichandar

etch

by SaravananJaichandar
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to etch

No user-submitted related servers found.

    Related Servers

    • mcp-audit-gateway

      elang2
      A
      license
      Not graded
      quality
      A
      maintenance
      Tamper-evident audit trail for AI agent tool calls. Cryptographically signed, hash-chained records that prove what your agents did.
      3
      18 npm
      MIT

    • Fabric Verify MCP server

      AugmentEVzero
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to sign action records locally, publish them to a public log, and retrieve tamper-evident proofs that anyone can verify offline.
      44 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.
      7 npm
      MIT

    • DCL Evaluator

      Fronesis-Labs
      F
      license
      Not graded
      quality
      F
      maintenance
      Superseded. Earlier version of the DCL product (MCP endpoint at /sse with API key, plus an offline desktop audit trail). Not the current path for agents. Use the hosted DCL Trust Oracle: https://github.com/Fronesis-Labs/dcl-webhook (MCP endpoint https://mcp.fronesislabs.com/mcp, Streamable HTTP, x402 payment, no API key).
      -

    • PiQrypt MCP Server

      PiQrypt
      A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to sign decisions with post-quantum cryptographic proofs and maintain secure audit trails for compliance. It provides tools for stamping events, verifying chain integrity, and exporting audit data across industries like finance and healthcare.
      4
      25 npm
      MIT
    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

    B3.2/5.0

    Scored across 31 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes (e.g., query_fact vs. search_global, record_decision vs. record_correction). A few pairs like get_constraints/get_agents_md_constraints and simulate_change/validate_change have some overlap, but the descriptions differentiate them sufficiently for an agent to choose correctly.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern in snake_case (get_*, record_*, predict_*, etc.). Even compound names like get_co_edit_suggestions and prove_entry_inclusion maintain the pattern without mixing conventions.

    Tool Count2/5

    With 31 tools, the surface is significantly larger than the typical well-scoped server. While the server covers a broad domain, this count places a heavy burden on agent selection and navigation, likely reducing overall coherence.

    Completeness4/5

    The tool set covers a comprehensive lifecycle: seeding, ingestion, querying, validation, prediction, audit, and export. Minor gaps exist, such as no explicit update/delete for facts or constraints, but these are likely handled internally, so core workflows are supported without dead ends.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources