Community · E2 · artifact verified
Expose typed Jev judgments to MCP agents
An MCP server gives compatible agents tools for classification, scoring, checking, matching, screening, and custom typed Jev questions.
01 · Role in the system
What Jev does here
Jev provides the bounded Choice, Score, and Noul answers behind six MCP tools. The server validates requests, applies configurable budgets and retry policy, adds abstention to matching, and returns a stable structured envelope. Agent clients receive typed values rather than prose, while consequential authorization decisions remain outside this screening layer.
02 · Control boundary
Where Jev sits
MCP tool calls become validated Jev requests; the server returns stable structured results and keeps policy in code.
Code owns the loop, permissions, thresholds, validation, and side effects. Jev owns only the bounded judgments described above.
03 · Known limits
What this evidence does not prove
- Screening is not a security or authorization boundary, and confidence is not correctness.
- Published measurements come from one early-access key and a limited field-service data set.
04 · Attribution
Public sources
This is a Community record: the project was published by a third-party community author.
- blakestone-x ↗Community · github · public · checked 2026-09-18