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
      48 npm
      MIT

    • 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

    • 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
      57 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

    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

    ActivitySlowing
    ResponsivenessNo issues

    Resources