evokit (dsh-evokit)
Related Servers
Alternatives to evokit (dsh-evokit)
No user-submitted related servers found.
Related Servers
- AlicenseBqualityBmaintenanceUniversal skills framework and MCP server with deterministic TDD reproduction, adversarial red-team fuzzing, AST context compression, and git worktree isolation.91MIT
- AlicenseAqualityCmaintenanceSelf-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.1594MIT
- AlicenseAqualityBmaintenanceEnables 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.247MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to initialize, run, monitor, promote, and distill autonomous research experiments through isolated staging, adversarial verification, and persistent skill generation.MIT
- AlicenseNot gradedqualityBmaintenanceLocal MCP server enabling voice-controlled terminal coding agents with verified action receipts, distinguishing proven acceptance from unconfirmed writes.111 PyPI7MIT
- AlicenseAqualityBmaintenanceFeynman'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.665 npmApache 2.0
TDQS
Scored across 16 tools
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.
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.
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.
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.