robins-i-mcp
Related Servers
Alternatives to robins-i-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityAmaintenanceMCP server for querying PROSPERO registered protocols, enabling search, retrieval, and registration workflow management.-
- AlicenseNot gradedqualityCmaintenanceAn MCP server that evaluates whether retrieval methods and AI outputs are grounded in long narrative manuscripts by retrieving evidence and scoring coverage deterministically, without external model APIs. It provides tools for chunking, indexing, retrieval, and evaluation.1MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that enables AI assistants to drive systematic literature review workflows, including screening, downloading, converting, and reviewing papers through natural language conversation.28AGPL 3.0
- AlicenseNot gradedqualityCmaintenanceMCP server for agentic systematic literature reviews with citation verification. Enables AI assistants to list reviews, get drafts, retrieve citation audits, and manage discovered papers.01MIT
- AlicenseAqualityBmaintenanceA standalone MCP server that searches multiple scholarly metadata providers (PubMed, Europe PMC, bioRxiv, Crossref, OpenAlex, Semantic Scholar, arXiv), deduplicates results, and returns ranked literature with optional open-access full-text retrieval from Europe PMC.31Apache 2.0
- AlicenseNot gradedqualityAmaintenanceAn MCP server that provides tools for deterministic EU AI Act risk classification and documentation generation, enabling human-in-the-loop AI system assessments inside Claude Code.1MIT
TDQS
Scored across 9 tools
Each tool serves a distinct step in the ROBINS-I workflow, but assess_result and get_spec both return specification/rubric information, which could cause an agent to fetch the wrong one. parse_document and parse_pmcid are clearly distinguished by input type.
All tool names follow a consistent verb_noun pattern in snake_case: parse_document, parse_pmcid, specify_result, submit_answers, render_report, export_robvis. The pattern is uniform and predictable across the entire set.
Nine tools is well within the ideal range and each tool covers a necessary step in the assessment lifecycle—parsing, setup, domain work, finalization, and export. No tool feels redundant or extraneous.
The tool set covers the full ROBINS-I assessment workflow: document ingestion (parse_document/parse_pmcid), protocol setup (set_prespecified_confounders, specify_result), domain assessment (assess_result, submit_answers), and reporting (render_report, export_robvis). There are no obvious dead ends or missing critical operations.