jev-harness
Related Servers
Alternatives to jev-harness
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceMartinLoop is the independent governance and financial control layer for AI coding agents. Set hard spend limits, prevent runaway loops, enforce verification, trigger rollback on failure, and generate auditable receipts showing what changed, what it cost, and whether the work passed.24981 npm409Apache 2.0
- AlicenseNot gradedqualityAmaintenanceA runtime gate for coding agents. Blocks the tool calls that wreck a repo (force-push main, rm -rf, secret exfiltration, CI wipe) and lets normal build and commit work through. Machine-checked git-branch core (z3); the rest is high-precision heuristics. Tested on 3,790 real CI commands, 0 false blocks.1MIT

aperion-shieldofficial
FlicenseAqualityAmaintenanceLocal guardrail proxy for AI coding agents. Wraps any MCP server (stdio or HTTP/SSE) and blocks destructive tool calls before they execute, with TOFU catalog pinning against rug pulls and tool-poisoning/result-injection scanning. Single Rust binary, Apache-2.0.1411-- AlicenseNot gradedqualityDmaintenanceRuntime safety guardrails for AI coding agents. Checks file access, validates shell commands, and scores your repo's AI safety — all via MCP.6 npm8MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI coding agents to verify code patches locally with sub-50ms neuro-symbolic analysis, detecting structural issues like dependency cycles and interface drift without consuming output tokens.1Apache 2.0
- AlicenseBqualityAmaintenanceEnables AI coding agents in Cursor, Claude Code, Cline, and similar editors to halt repetitive failed edits after two consecutive attempts and instead gather falsifiable evidence such as git status, dirty diffs, and locked-port checks before writing more code. It also supervises wrapped shell commands, terminating hung prompts and orphaned process trees so agents can restore a clean, testable baseline.321 npm1ISC
TDQS
Scored across 6 tools
Each tool targets a distinct decision point in the agent workflow: triage failure, check abort, route task, verify completion, modulate reasoning, and evaluate nudge. The only potential overlap between route_task and modulate_reasoning_effort is well-clarified by descriptions that distinguish tier selection from per-call reasoning parameter mapping.
All tool names follow a consistent jev_ prefix with snake_case verb_noun or verb_noun_noun structure (e.g., jev_triage_test_failure, jev_route_task). No deviations in style or convention.
Six tools is well-scoped for an agent harness, with each tool addressing a unique decision point without redundancy. The set is neither too thin nor too heavy for the purpose.
The tools cover the core agent lifecycle decisions: model routing, reasoning effort, failure triage, abort detection, completion verification, and nudge evaluation. A minor gap exists in explicit state or attempt history management, but agents can work around this externally.