typesafe-screening-mcp
Related Servers
Alternatives to typesafe-screening-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables prototyping, running, and evaluating typed judgment questions against TypeSafe's Jev model, including accuracy, calibration, and threshold analysis.328 npm3MIT
- AlicenseAqualityCmaintenanceEnables MCP clients to call TypeSafe's JEV classifier and receive structured, typed judgments with probabilities for binary, choice, and scoring questions.17MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to get machine-readable yes/no, choice, and score decisions from TypeSafe Jev, bridging fast classification to Cursor and other clients.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to consult TypeSafe's Jev through a judge tool, answering narrow typed questions with calibrated probabilities instead of prose.27 npm1MIT
- 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.11470 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables an AI assistant to run systematic review screening steps such as creating projects, importing records, scoring and ranking them with a zero-shot LLM classifier, presenting records for human decisions, applying a statistical stopping criterion, and exporting results. Human reviewers retain responsibility for inclusion decisions, with probabilities hidden unless requested.Apache 2.0
TDQS
Scored across 3 tools
Each tool has a distinct input path: search-then-screen, screen specific PMIDs, and screen arbitrary non-PubMed records. screen_pmids and screen_records are similar in action but clearly separated by input type, so an agent can select correctly with the descriptions.
Tools follow a mostly consistent verb-first snake_case pattern (screen_pmids, screen_records), with search_and_screen as the one oddity using a compound verb form. The naming is predictable and readable despite this minor deviation.
Three tools is a well-scoped set for a narrow screening workflow: one search+screening tool and two variants for different input sources. Each tool earns its place and there is no bloat.
The tools cover the full screening pipeline: searching PubMed, screening known PMIDs, and screening external records. A minor gap is the lack of a raw article/metadata retrieval tool, but it is not essential for the stated screening purpose.