jev-mcp
Related Servers
Alternatives to jev-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceProvides coding agents with typed classification, yes/no checks, scoring, ranking, and question-answering tools that return calibrated probabilities for fast, reliable decisions.802 npm59MIT

jevbook MCPofficial
AlicenseNot gradedqualityCmaintenanceEnables agents to fact-check claims, conduct verified research, make typed decisions with calibrated probabilities, and scan token risks through a hosted server with no API key required.MIT- AlicenseAqualityCmaintenanceProvides agents with fast, typed, calibrated decision tools for classification, scoring, yes/no checks, and gating risky tool calls.53MIT

Olaverse MCP Serverofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to extract template-shaped JSON from text, images, and PDFs with calibrated per-field confidence, make typed decisions with probabilities, identify languages among 608, restore diacritics, and generate passage-grounded questions.Apache 2.0- AlicenseNot gradedqualityCmaintenanceEnables AI agents to check a drafted answer against supplied sources or a document before stating or acting on it, returning claim-level support status, contradictions, omissions, and a verdict.MIT
- AlicenseAqualityBmaintenanceEnables coding agents to query files, logs, and search results through TypeSafe Jev's typed, probabilistic answers, so they retrieve only the needed conclusion instead of raw context. Supports classification, scoring, yes/no checks, extraction, page ranking, and injection screening.11209 npmMIT
TDQS
Scored across 12 tools
Each tool has a clearly distinct input/output contract (e.g., verify vs. noul vs. audit vs. compare), and descriptions explicitly cross-reference when to use alternatives (gate vs. review, find vs. rerank). Overlaps are mitigated rather than ambiguous.
All tools use consistent snake_case with the jev_ prefix, but jev_noul deviates from the otherwise uniform verb-based operation naming (verify, gate, screen, find, etc.), a minor inconsistency.
12 tools sit well within the 3-15 range and each maps to a distinct reasoning primitive (verification, screening, retrieval, classification, decision, review, etc.), so none feels redundant.
The surface covers a full cognitive toolchain: input screening, extraction, auditing, verification, comparison, retrieval/find/rerank, classification, decision, patch review, and gated completion. No obvious lifecycle gap for the stated Jev reasoning domain.