Skip to main content
Glama

Related Servers

Alternatives to evokit (dsh-evokit)

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Self-improving learning engine for Claude Code. Extracts signals from sessions (corrections, successes,confusion), runs periodic reflections, and evolves behavioral frameworks through evidence. 9 MCP tools, automatichooks, local-only.
      15
      94
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables coding agents to make offline, zero-cost decisions using schema-safe Choice/Score/Noul primitives, a confidence gatekeeper, planning, adversarial red-teaming, research, and RLVR-based self-improvement via 21 MCP tools.
      24
      7
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Feynman's twelve-problems method as an MCP server — a persistent set of long-running problems plus an evoke loop that tests each new trick against all of them. Local, TypeScript, no LLM inside, no API key.
      6
      65 npm
      Apache 2.0

    TDQS

    A4.4/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource+action pair, and descriptions explicitly disambiguate near-neighbors (run_launch vs run_interleaved, run_status vs run_results, compare_paired vs noise_estimate vs gate_check, ledger_history vs meta_metrics). The 'use X for… use Y for…' cross-references make selection reliable even in the crowded run/comparison area.

    Naming Consistency4/5

    Names follow a predictable resource-prefix scheme (version_*, run_*, proposal_*, ledger_*, gate_*, compare_*), which is easy to scan and group. A few singular tools (compare_paired, gate_check, meta_metrics, scenario_describe) break the strict prefix family, but the overall convention remains readable and stable.

    Tool Count4/5

    At 16 tools the surface is on the heavy side, but the domain genuinely spans scenario inspection, versioning, execution, analysis, proposal/gating and ledger auditing, and each tool maps to a needed step. Nothing looks redundant or like filler.

    Completeness4/5

    The lifecycle from edit → version_create → run → compare → noise → proposal → gate is well covered, with read-only audit and metrics views. Two gaps: gate_check points to a ledger_adopt tool that is not in this set (adoption is unreachable here), and there is no cancel/abort for a detached run or a general version listing beyond ledger_history.

    Maintenance

    ActivityMaintained
    ResponsivenessOutdated data