Skip to main content
Glama
foundryside-dev

heddle

Official
by foundryside-dev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to heddle

No user-submitted related servers found.

    Related Servers

    • hiveecho

      srotzin
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for temporal state queries and cryptographic audit trails. Query historical entity state at any point in time, generate Merkle proofs of past state, and anchor contract snapshots for immutable provenance.
      MIT

    • oprow-continuum

      sanyamChaudhary27
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server that acts as a temporal verification firewall, checking structured assumptions or diffs against immutable version receipts to return allow/block/abstain with cited evidence.
      MIT

    • SYKE

      khalomsky
      A
      license
      Not graded
      quality
      F
      maintenance
      AI code impact analysis MCP server that monitors file changes, maps dependency graphs, detects cascading breakage, and gates builds before damage spreads.
      53 npm
      2
      Elastic 2.0

    • Groundtruth

      ElijahSLimaj
      F
      license
      Not graded
      quality
      B
      maintenance
      MCP server for the governed knowledge layer, enabling agents to query canonical entries, retrieve conflicts, and manage proposals with strict tenant isolation and audit.
      -
    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

    C2.1/5.0

    Scored across 12 tools

    Disambiguation1/5

    The tool set contains exact duplicates (e.g., changed and heddle_change_list, churn and heddle_entity_churn_count_get, etc.) with identical descriptions, making it impossible for an agent to distinguish between them. This severe overlap undermines any ability to reliably select the correct tool.

    Naming Consistency1/5

    Naming is chaotic: half the tools use short names (blast_radius, changed, churn, reverify, timeline) while the other half use a 'heddle_' prefix with different patterns (heddle_change_list, heddle_edge_snapshot_capture, etc.). Verbs are mixed (capture, changed, get) and no consistent verb_noun pattern is followed.

    Tool Count3/5

    The raw count of 12 tools is within a reasonable range, but half are duplicates, effectively reducing the unique tool count to 6. While not extreme, the duplication suggests poor scoping and undermines efficiency.

    Completeness3/5

    The set covers core operations like capturing snapshots, listing changes, getting churn/timeline/impact radius, but lacks update/delete or other lifecycle operations. The duplicates do not add new functionality, so coverage is adequate but not comprehensive.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources