Skip to content

Jev Toolkit

A small stdio MCP server that exposes three Jev-backed tools to coding agents: structured judgments, ranking supplied candidates by relevance, and checking claims against evidence you provide.

Stars
1
Language
TypeScript
License
MIT
Published by
Community
Author
jbt95
Last verified
Oct 2026

About this project

A small stdio MCP server for TypeSafe/Jev with three tools: typesafeask for structured judgments, typesaferank for ordering supplied candidates by relevance, and typesafeverify for checking claims against supplied evidence. Calls use the TypeSafe System One API and are recorded in a local event log. Built with Effect and TypeSafe's SDK. Bun >= 1.3.14 is required. Register Jev in a user-level harness config with:

Quoted from the project's README. Read the full README.

Highlights

  • Three tools: typesafe_ask for structured judgments, typesafe_rank to order supplied candidates, and typesafe_verify to check claims against evidence.
  • Register it in a user-level harness config with jev install opencode, pi, omp or claude-code, preserving unrelated MCP settings.
  • Install is a clone, bun install --frozen-lockfile and scripts/install.sh, then export TYPESAFE_API_KEY; Bun 1.3.14 or newer is required.
  • Rank rejects common code, diff and transcript patterns and redacts credentials, and verification never writes claim or evidence text to the log.

Watch out

There is no published package: the documented install is a git clone, a frozen-lockfile Bun install and scripts/install.sh. The install commands deliberately do not store TYPESAFE_API_KEY, so the harness process has to provide it to the MCP server, which is an easy thing to get wrong when registering by hand. The pi target installs pi-mcp-adapter and needs the Pi CLI plus network access. The README states its own privacy limits plainly: rank's pattern checks are conservative rather than a complete content classifier, and typesafe_ask state is caller-provided, so you must redact it yourself. Calls go to the TypeSafe System One API and are recorded in a local event log. Tests are offline, using fake transports, temporary files and localhost, and the Oxlint fixture suite needs Node 22.18 or newer even though the application and CLI run on Bun. Copy reviewed against the repository README on 2026-10-04, not from running it.

Questions about this entry

Short answers drawn from the linked project or page.

More Jev resources like this

48GitHub stars
Agent harness for work that outlives one chat, with resumable turns, routed state machines, and observational memory across sessions and processes.
Jev Agents & MCP#community#jevbest#catalog-import
Assistant framework that stores specs, memory, and specialist agents as plain markdown files in your repo for Claude Code, Codex, Opencode, and similar runtimes.
Jev Agents & MCP#community#jevbest#catalog-import
36GitHub stars
Pi extension that strips the full Agent Skills catalog from every request and loads only the skills a Jev ranking call judges relevant.
Jev Agents & MCP#community#jevbest#catalog-import
102GitHub stars
Behavioral code search that asks Jev to score repository fragments for a plain-language question and returns exact excerpts with paths and lines.
Jev Agents & MCP#community#jevbest#catalog-import
18GitHub stars
Local engine with TypeScript and Python SDKs that runs Claude Code and Codex sessions as a warm team with a durable mailbox.
Jev Agents & MCP#community#jevbest#catalog-import
16GitHub stars
Single-command harness that turns a plain-language stack description into synced docs plus blocking hooks for Claude Code, Codex, and Pi, with deterministic presets or one Jev chooser call.
Jev Agents & MCP#community#jevbest#catalog-import
Back to all resources

From the Jev community

Posts from builders shipping with Jev right now.

Follow @typesafeai