yf-decide-mcp
Related Servers
Alternatives to yf-decide-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceLets MCP clients ask typed questions — yes/no, choice, or score — about structured state, including images, and receive calibrated probabilities from System One decision models such as TypeSafe Jev and Cloudflare Clef. Supports TypeSafe, OpenRouter, and local providers selectable per request, with input validation and cost reporting.6223 npmMIT
- AlicenseNot gradedqualityBmaintenanceProvides an MCP interface to the Laya decision model, enabling typed queries (yes/no, multiple choice, score) with preflight token-budget reporting, honest confidence calibration, and structured error handling.31 PyPI5Apache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables structured yes/no, multiple-choice, and ordered-score judgments from supplied text and criteria, returning typed probabilities, selected labels, scores, and confidence. It exposes bounded decision tools without search, chat generation, arbitrary HTTP requests, or action execution.223 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables agents and services to ask small decision models typed questions about text, JSON, images, or video, returning labels, scores, or yes/no answers over MCP tools or a Jev-compatible HTTP API.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables typed decisions (yes/no, choice, score) with transparent preflight checks, honest confidence reporting, and health monitoring.116 npmApache 2.0
- AlicenseAqualityCmaintenanceEnables coding agents to ask typed yes/no, choice, score, and bounding-box questions about code, diffs, logs, and screenshots, returning structured decisions with calibrated confidence, caching, and cost controls.3223 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another tool. Its purpose is clearly stated as a typed decision endpoint rather than a chat model.
The single tool name 'decide' is a clear, concise verb that matches the server's decision-making purpose. With only one tool, there are no inconsistent naming conventions to conflict.
A single tool is appropriate for wrapping one focused decision endpoint, and the rich question-type schema keeps it from being trivial. However, the surface is very thin, with no separate discovery or utility tools.
The tool covers the core decision operations: choice, score, noul, box, and batching independent questions. Minor gaps exist around endpoint discovery, health checks, or model metadata, but the main decision workflow is complete.