Skip to main content
Glama

Related Servers

Alternatives to scar-tissue

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables coding agents to record rejected approaches, decisions, and constraints, with expiring reasons, in a git-tracked Markdown store the agent consults before proposing anything. This makes agents stop re-suggesting options that were already ruled out, and entries quietly drop out of view once they lapse.
      15 npm
      1
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Local-first project memory for AI coding agents. Records failed attempts, fragile files, and decisions per repo, and warns the agent via hooks before it repeats a recorded mistake.
      6
      59 npm
      MIT
    • A
      license
      A
      quality
      A
      maintenance
      Local-first memory layer for AI coding agents — captures issues, attempts, fixes, and decisions, and warns at git commit before you repeat a mistake.
      19
      978 PyPI
      877
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to check proposed actions against a local ledger of previously ruled-out work, receiving graded alerts with prior verdicts to avoid repeating dead ends.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      Enables coding assistants to persist decisions, rules, bugs, to-dos and dead ends from chat sessions into a repository memory file, then automatically recall the relevant ones in later sessions. It also checks pending commands and file edits against those saved rules before they run, flagging possible violations.
      500 npm
      MIT

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools are clearly distinct: record_dead_end writes a new scar, while check_scar_tissue reads historical scars. There is no overlap or ambiguity in their purposes.

    Naming Consistency5/5

    Both names follow a consistent snake_case verb_noun pattern (record_dead_end, check_scar_tissue), making the set predictable and easy to parse.

    Tool Count3/5

    Two tools is thin for a memory system; while record and check cover the core loop, additional operations like listing or deleting scars would be expected for a robust surface.

    Completeness3/5

    Core create and query operations exist, but there is no way to list, update, or delete recorded dead ends, leaving notable management gaps that could cause dead ends to become unmanageable.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues