ClaudeMap

Jev Review

A local MCP server that hands Claude Code (and Codex, Cursor, OpenCode) structured code-quality scores from TypeSafe's Jev — 15 always-on dimensions, no hosted backend, your key stays local.

MCP Serversmcp-servercode-qualityreviewjevscores

Jev Review is a local MCP server (stdio, one focused tool: jev_review) for continuous software-quality checkpoints while an AI coding agent works. Intended rhythm: after a coherent implementation slice, after a score-driven improvement, and before final handoff — establish a baseline, inspect, hypothesize about weak dimensions, improve, re-score. Jev returns typed decisions (Score, Choice, Noul) rather than a prose essay; the server validates and converts them into metric scores, confidence levels, coarse rubric hints, and comparisons with the previous evaluation, while the coding agent stays responsible for diagnosing causes and changing code. Fifteen dimensions are always evaluated when context suffices — correctness and requirement fit, cognitive complexity, readability and intent, modularity and cohesion, coupling and dependency quality, changeability and change amplification, abstraction and API design, project and file structure, duplication and reuse, maintainability, testability and test quality, reliability and error handling, security, consistency and conventions, documentation and explainability — plus four evidence-gated ones: performance and resource efficiency, scalability and flexibility, compatibility and API stability, observability and operability. There is no hosted backend, database, telemetry or author-operated proxy: the only remote request goes directly to the configured Jev API. Node.js 20+, distributed from GitHub (no npm package), MIT.

What it does

  • 15 always-on quality dimensions plus 4 evidence-gated ones — correctness, coupling, testability, security and docs among the always-ons
  • Typed Jev decisions (Score/Choice/Noul), not prose: metric scores, confidence levels, rubric hints and deltas vs the previous review
  • Workflow built for score-driven improvement: baseline, inspect, hypothesize, improve, re-score at focused checkpoints
  • No hosted backend or telemetry — the only remote request goes directly to the Jev API with your key

When to use it

Agent-assisted developers who want a repeatable numeric quality signal at each checkpoint of a change, while keeping diagnosis and the actual code edits with the primary coding agent.

Getting started

export JEV_API_KEY="your-key"              # from the TypeSafe console
npx plugins add NiazMorshed2007/jev-review  # choose your client when prompted
# restart the client, then ask the agent to use jev-review
# requires Node.js 20+; no npm publication — installs from this repo

Things to know

MIT. Jev supplies scalar signals only — no explanation of why a score is low; the coding agent must find the cause itself, and the dimensions are context-dependent ('when the supplied context is sufficient'). Routing reviews through Jev is a paid TypeSafe API. Note the name collision: devagrawal09/jev-review is an unrelated same-named project — a standalone review CLI with a local dashboard, no MCP or Claude Code integration.

Repository

NiazMorshed2007/jev-review

Charted

Related on the map

  • Blitz Strike

    MCP Server

    A penetration-testing methodology delivered as one MCP server: BLITZ maps the attack surface, EAGLE-EYE traces source-to-sink, STRIKE live-verifies every finding before it is reported.

    • mcp-server
    • security
    • pentest
    • methodology
  • Ripwire

    MCP Server

    Red Hat's "ripgrep for AI context" — a C++23 zero-dependency CLI that also speaks MCP.

    • mcp
    • code-context
    • cli
    • red-hat
  • Deja Vu

    MCP Server

    One shared session memory for 25+ coding agents — Claude Code, Codex, and Cursor finally remember the same project.

    • mcp
    • memory
    • cross-agent
    • context