Agent tooling
MCP servers, model routers, and approval gates for people running coding agents on TypeSafe Jev.
This hub is for teams on Claude Code, Pi, Hermes, or a custom agent who need a fast route, allow, or compact decision on the hot path. Each tool sends Choice, Noul, or Score questions to Jev instead of parsing yes or no out of a chat reply. Prefer READMEs that state a latency budget and fail closed when the API errors.
Who it is for: Teams running Claude Code, Pi, Hermes, or custom agents who need fast, thresholdable decisions on the hot path instead of parsing YES/NO from chat completions.
How to choose: Start with the integration surface you already use (MCP vs npm plugin vs HTTP sidecar). Prefer repos that document latency budgets, failure modes, and which Jev primitives they send (Choice for routing, Noul for allow/deny, Score for severity). If the tool auto-approves tool calls, read how it fails closed when the API errors.
122 listings in this bucket · Learn Jev
See Jev alternatives compared, Kev vs Jev and Mapika Decider vs Jev.
Guide
What counts as agent tooling here
This hub lists routers, MCP servers, compaction helpers, review gates, and guardrails where System One sits between your agent and side effects. The pattern is the same: serialize the risky moment (shell command, tool call, diff hunk) into structured state, ask a typed question, threshold probabilities in code. Chat models may still write code or prose elsewhere; Jev is the judge on the narrow decision.
Primitives you will see most often
Choice picks one label from a small catalog (model name, browser action, approval verdict). Noul answers yes/no with a calibrated probability, perfect for allow/block gates. Score ranks ordered levels (blast radius, severity, compaction keep/drop). Many tools fan out several questions in one API call, then compose answers with policy text you control.
Highlights
Hand-picked listings with extra detail on this directory. Star counts and demos still live on each card.
- hermes-jev-approvals
Hermes smart approvals via typed Choice instead of a one-token chat completion. Strong fit if you search for hermes jev or jev hermes.
- typesafe-mcp
Single-binary MCP server and Go CLI (typesafe-mcp) for evaluate setup across Claude Code, Desktop, Codex, and Pi.
- pi-jev-auto-mode
Pi plugin that auto-approves safe bash/write/edit calls using Jev thresholds (pi-jev / pi jev queries).
- pi-warden
Pi supervisor that steers the agent back on track with Jev judging rules, risky tools, and stuck loops.
- jev-shield
Semantic MCP firewall: calibrated screening on tool calls, results, and poisoned descriptions.
- fast-jev-compaction
Compaction gate: Noul on whether a tool result deserves to stay verbatim in context.
FAQ
- What is Hermes Jev?
Short answer: see the Hermes Agent + Jev guide for the full setup, or the hermes-jev-approvals listing for just the approval plugin.
- MCP or npm plugin for Pi?
MCP (typesafe-mcp) exposes evaluate tools to any MCP host. Pi-specific packages like pi-jev-auto-mode and pi-warden hook Pi's extension API directly. Pick MCP when you want one server for multiple clients; pick Pi packages when you live entirely inside Pi.
- How fast should agent tooling feel?
Sub-second per gate is the design target for tool approvals. Published benchmarks in individual READMEs vary by model route and hardware; always measure on your network before you enable auto-approve in production.
- Do these tools replace my system prompt?
Rarely. They add a decision layer with explicit thresholds. Policy text still belongs in trusted channels (Hermes smart_policy, pi-warden.md rules, jev-shield JSON policies).
- Where is the official TypeSafe SDK?
Official JavaScript and Python clients live under Official and SDKs. Community MCP and Pi wrappers in this hub are maintained by their authors, not TypeSafe.
All listings
by @0xLogicrw
by @0xLogicrw
by @0xLogicrw
by @0xLogicrw
by @0xLogicrw
by @Kantorcodes
by @zxdubx