Jev Checkpoint
Related Servers
Alternatives to Jev Checkpoint
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables agents to delegate decisions to a configurable model, returning recommended choices with percentage scores and profile-based routing.MIT

@quirna/mcpofficial
AlicenseNot gradedqualityCmaintenanceEnables AI agents to request human approval before consequential actions, with policy-based routing, phone-based approver decisions, and signed audit evidence.MIT- FlicenseNot gradedqualityBmaintenanceEnables low-latency geo-distributed request routing for AI agents, providing deterministic, zero-dependency edge request governance with sub-millisecond execution overhead.8-
- AlicenseNot gradedqualityCmaintenanceEnables agents to evaluate single records or batches with dynamically authored typed questions, returning structured decisions and probabilities.MIT
- AlicenseAqualityCmaintenanceEnables agents to perform typed judgments—classify, score, check, match, and screen—over closed answer sets with confidence scores, without text generation.74MIT

DriftOS MCP Serverofficial
FlicenseAqualityDmaintenanceEnables intelligent semantic conversation routing that automatically branches, maintains, and routes between conversation topics instead of relying on entire conversation histories for context.62-
TDQS
Scored across 1 tool
With only a single tool, there is no possibility of confusion between tools. The tool's purpose is clearly described and distinct from any other potential operation.
The tool name follows a clean verb_noun pattern (classify_decision). Even though there is only one tool, the name is conventional and consistent with common MCP naming styles.
A single tool feels thin for most servers, and this one is no exception. However, the narrow scope of 'advisory classification only' makes the low count somewhat reasonable, but it remains on the borderline.
The tool fully covers its stated purpose of returning an advisory, confidence-gated route for a bounded decision. The explicit note that it never executes the route defines the boundary clearly, so there are no obvious missing operations within that scope.