jev-kit
Related Servers
Alternatives to jev-kit
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceEnables coding agents to run bounded local profiling, tracing, benchmarking, and capture operations from explicit artifacts or commands, then inspect typed evidence, provenance, coverage, limitations, and preserved replay sources through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to run bounded analysis and capture operations against explicit artifacts or commands, returning typed evidence, provenance, coverage, limitations, and optional preserved evidence through MCP tools.-
- FlicenseNot gradedqualityAmaintenanceEnables coding agents to coordinate local profilers, benchmark tools, trace processors, and explicit targets into bounded runtime evidence, including observed inputs, execution provenance, typed findings, coverage, and limitations. It supports analysis and capture through named MCP tools without workspace setup or project configuration.-
- FlicenseNot gradedqualityAmaintenanceEnables MCP-enabled editors to run thesis–antithesis–synthesis reasoning workflows and player-coach code verification loops, including session persistence and independent coach review.-
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to query repository structure, symbols, dependencies, Git history, architecture, memory, impact, and guarded edits through a stable MCP interface, returning ranked task-specific evidence within a context budget.48 PyPI8Apache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables proof-backed code audit via MCP tools for AST-based code maps, symbol lookup, callers, audit commands, and persistent verdict memory.MIT
TDQS
Scored across 13 tools
Several tools occupy overlapping 'select/judge without executing' territory (jev_step vs jev_tool_route vs jev_route_skills; jev_review vs jev_gate; jev_evaluate vs jev_verify). The caveats in the descriptions help, but the boundaries are subtle and an agent would need to read closely to avoid misselection.
All tools share the jev_ prefix and mostly follow a snake_case verb_noun pattern like jev_prepare_work and jev_route_skills. A few outliers such as jev_coding_loop, jev_tool_route, and jev_step break the verb-first pattern, but the naming is still predictable and readable.
13 tools is a reasonable size for a workflow-oriented kit and each tool has a distinct stage in the process. It is slightly heavy because some tools are narrowly scoped variants of similar actions, but none feel redundant enough to remove.
The tool surface covers preparation, routing, evaluation, review, verification, screening, ranking, gating, code brief generation, and evidence collection, which matches the stated host-advisory role. Execution is deliberately left to the host, so major workflows do not dead-end. Missing task/state management seems out of scope for this kit.