jev-harness
Related Servers
Alternatives to jev-harness
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceRuntime governance and budget guardrails for Claude Code, Cursor, and autonomous AI agents. Enforces per-session spend caps, verifier safety gates, and runaway loop prevention.24265 npm191Apache 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.4 npm8MIT
- 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.3175 npm1ISC
- AlicenseAqualityBmaintenanceEnables AI coding agents to avoid irreversible mistakes by intercepting risky deletions, overwrites, and commands before execution, applying path, pattern, and blast-radius safeguards with quarantine backups.36 npmMIT
TDQS
Scored across 6 tools
Each tool addresses a distinct decision point in the agent lifecycle: failure triage, abort protection, task routing, completion verification, reasoning effort modulation, and continuation nudging. There is no meaningful overlap; even the related pairs (abort vs. nudge, route vs. modulate) focus on different moments and inputs.
All tools share the 'jev_' prefix and use snake_case with a verb-like leading word, e.g., triage_test_failure, route_task, verify_completion. The only slight deviation is 'jev_should_nudge_continuation', which uses a modal verb phrase rather than a direct imperative, but it remains clear and predictable.
Six tools is a tight, purposeful set for a decision-harness server. Each tool covers a distinct optimization decision without redundancy or bloat, making the count well-scoped for the domain.
The harness covers the main meta-decision points: triage failures, prevent wasted work, route to cost-effective models, verify completion, modulate effort, and decide on nudges. A minor gap might be a tool to record outcomes or update state, but the core lifecycle appears well covered.