An MCP server exposing ten Jev judgment tools, including verify, screen, find, rerank, classify, review, and gate, each returning typed probabilities in roughly 150 to 500 ms.
Fast, cheap, typed judgments from TypeSafe's Jev model, as MCP tools.
Forks
62
Last pushed
Updated Oct 2026
Repo stats from the GitHub API, cached Oct 2026.
About this project
Fast, cheap, typed judgments from TypeSafe's Jev model, as MCP tools. Give your agent twelve judgment tools: jevscreen judges content before it enters context. jevnoul returns a calibrated probability for a stated proposition. jevfind picks the best candidate by meaning. jevrerank scores and sorts every candidate. jevcompare judges how two passages relate. jevextract pulls field values with regex plus judgment. jevaudit audits extracted values against their source before they are trusted.
Ten tools cover claim verification, content screening, candidate finding, reranking, and classification.
Typical latency is roughly 150 to 500 ms per judgment at a fraction of a cent.
Provider keys can be TypeSafe direct, OpenRouter, or Vercel AI Gateway.
Runs via npx with one-line setup for Claude Code, Codex, Amp, and OpenCode.
Watch out
Early software, and it needs Node 20 or newer plus a TypeSafe or OpenRouter API key.
Questions about this entry
Short answers drawn from the linked project or page.
The point is the mechanical checks an agent otherwise skips because a frontier model is too slow to run on every page or candidate list. jev_screen filters a fetched page for injected instructions before it enters context, jev_find picks the best candidate by meaning with no embeddings or index to maintain, and jev_extract returns verbatim strings the model found but never wrote.
That is the failure mode the shipped agent skill exists for. It teaches when to reach for each tool instead of answering from the agent's own reading, because a registered-but-unused tool list changes nothing about the agent's behavior.
Stdio is the default. HTTP mode listens on HOST, which is 127.0.0.1 unless you change it, and JEV_MCP_AUTH_TOKEN is required to serve beyond loopback. Some clients can only be given a URL, so JEV_MCP_PATH_TOKEN=1 puts the token in the path instead; the README says to treat that whole URL as the secret.
No. Importing @jkudish/jev-mcp never boots a transport; createServer() registers the tools and returns an McpServer you connect yourself. The package now declares exports, so deep imports like @jkudish/jev-mcp/dist/index.js no longer resolve, and the /server alias is the explicit safe entry.
Run npx -y @jkudish/jev-mcp, or register it with your client as an MCP server using that command; it needs Node.js 22 or newer and a Jev provider key such as TYPESAFE_API_KEY.
The README lists twelve, including jev_verify for claims against evidence, jev_screen for content before it enters context, jev_find and jev_rerank for candidates, jev_classify, jev_extract, jev_review and jev_gate.
Yes. The package ships an agent skill under skills/jev/ that teaches coding agents when to reach for each tool; copy it to .claude/skills, .opencode/skills or .agents/skills, and in Amp the server is bundled with the skill.
Reactions & coverage
Posts, threads, and videos about this entry from around the web.
X: jev-review: a local-first score loop for coding agents
Reddit: One command to wire Jev into Claude Code, Claude Desktop, and Codex.
Python MCP server that exposes classify, score, check, match, and screen tools to MCP-compatible agents, returning typed judgments over a closed answer set with token usage and latency. Ships generic triage and routing question examples.
MCP server exposing one evaluate tool for Jev Choice, Noul, and Score questions, plus a separate eval harness that compares Jev against LLMs on shared labeled sets.
A dependency-free MCP server that exposes TypeSafe's Jev to Claude Code, Codex, Cursor, Hermes, and other agents through the ask_jev and list_jev_models tools, so your code gets typed decisions with probabilities instead of prose to parse.
Go MCP server exposing Jev through OpenRouter or TypeSafe as five tools: decide, classify, verify, rerank and list_models. Each tool call is one paid inference request, answers are validated against the question asked, and the unchanged provider response is returned with its usage cost.
Python MCP server exposing Jev System One as five typed tools, including a batched evaluate that runs a map of questions in one call, so agents consume probabilities instead of parsing prose.
MCP server fronting TypeSafe Jev over HTTP for Claude Code and Codex, wrapping six tools with server-side confidence gating, cost caps, caching and a metadata-only decision log.
Community Node.js MCP server exposing Jev as four read-only advisory tools for bounded probabilistic decisions, with the host model keeping final authority over every action.
An MCP server built around measuring questions rather than asking them: jev_ask prototypes wording, jev_eval sweeps thresholds against labeled data, jev_map applies the winner over a workload.
Rust stdio MCP server letting Codex offload bounded judgments to Jev: four tools for yes/no, choice, score, and batch, while Codex keeps investigation, edits, and tests.
An MCP server that exposes TypeSafe's Jev model as twelve judgment tools, including claim verification, injection screening, reranking, classification, extraction, and patch review, each returning typed probabilities in roughly 150 to 500 ms.
An MCP server and agent skill that verifies coding-agent work by driving the real running app and returning pass, fail, or couldn't-tell verdicts with the file:line to fix; its listing frames the approach as Jev-style machine-native runtime perception.
A local SQLite memory layer for CLI agents with an opt-in Jev reranker that batches Noul judgments over the top 40 recalled memories and falls back to a local cross-encoder on errors.
A self-hosted, versioned skills library for AI agents with HTTP MCP, scoped client keys, and opt-in Jev recommendations that rank skills for a task using your own OpenRouter, TypeSafe, or Vercel key.
A router that turns models, subagents, skills, MCP tools, CLIs, and plugins into one candidate set Jev answers with a single typed Choice, while the router code owns availability, permissions, and confirmation.
An MCP server for Antigravity IDE, Cursor, and Claude Code that uses Jev (jev-latest) to locate code semantically and audit git diffs, replacing broad grep sweeps of entire files.
Tool menus can outgrow the context that reads them. The catalog's Jev-based routers and gates narrow the list: benchmarked tool search, per-tool scoring, fail-closed approvals, and WebMCP in the browser.
The fastest-growing corner of the Jev ecosystem is coding agents. A tour of the MCP servers, tool-call gates, context pruners, and skill rankers built for that loop.
How Home Assistant conversation agents, macOS voice pipelines, and an advisory sentinel put a fast typed decision in the loop — one call per utterance, thresholds in code, and a daily token budget.