bounded-calcs-mcp
Related Servers
Alternatives to bounded-calcs-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityAmaintenanceEnables MCP-speaking hosts to ask typed questions (yes/no, choice, score) and receive calibrated probabilities instead of prose, over a stdio transport. Runs offline by default with an explicitly disclosed, opt-in egress contract for live providers.66 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables any MCP host to pose typed yes/no, choice, and score questions and receive calibrated probabilistic judgments instead of prose, over stdio and offline by default.66 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables any MCP-speaking host to pose typed judgment questions (yes/no, choice, score) and receive calibrated probabilities rather than prose, over a stdio transport. Runs fully offline against a mock provider by default, requiring an explicit live credential and opt-in gates before any state is transmitted.66 npmApache 2.0
- AlicenseNot gradedqualityAmaintenanceEnables MCP hosts to pose typed questions — yes/no, choice, and score — and receive calibrated probabilities instead of prose, over a stdio transport. Runs offline against a synthetic mock by default, with every transmission to a live provider named in a startup egress report.66 npmApache 2.0
- FlicenseAqualityCmaintenanceDeterministic tools for structuring high-stakes career and life decisions: cash-runway math with a safety floor, evidence grading (KNOWN/ASSUMED/UNKNOWN/SYNTHETIC) and six-dimension option comparison. Zero-dependency Python stdio server.4-
- AlicenseNot gradedqualityAmaintenanceExposes three tools over stdio that answer typed yes/no, choice, and score questions with calibrated probabilities, letting MCP hosts get structured decisions instead of generated prose. It runs against an offline mock by default and only transmits state to a configured provider when a live route is explicitly enabled and a credential is resolved.66 npmApache 2.0
TDQS
Scored across 3 tools
Three tools with clearly distinct purposes: enumerate calculators, retrieve one calculator's schema, and run an evaluation against it. There is no overlap between listing, describing, and computing.
All snake_case, but the verbs are mixed: list_calculators and get_schema follow verb_noun, while evaluate is a bare verb with no object noun. Still predictable and readable.
Only 3 tools, but the purpose is narrow and self-contained; list → get_schema → evaluate is a minimal complete lifecycle. Slightly thin, though each tool clearly earns its place.
Listing, schema retrieval, and evaluation cover the core read-only workflow, and the domain appears not to require mutation. Minor gaps: no batch evaluation or saved-result retrieval, but agents can compose calls.