medeval-mcp
Related Servers
Alternatives to medeval-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceProvides authenticated Streamable HTTP MCP access to a MedEval medical-device regulatory workspace, enabling project selection, evidence retrieval, section context, document revision management, and generation/evaluation task control.MIT
- AlicenseNot gradedqualityBmaintenanceEnables local MCP clients to interact with an AuroraCloud workspace, supporting object listing, content reading, search, and task management through authenticated API calls.44 npmApache 2.0
- AlicenseNot gradedqualityCmaintenanceEnables MCP clients to browse and edit approved local workspace files, inspect and modify .xlsx spreadsheets, run terminal commands, and use previews and local approvals backed by path guards, backups, and audit logging.MIT
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to interact with a local-first research knowledge workbench, supporting literature search, evidence-grounded Q&A, and reference export.2AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables MCP clients to work with a local planning workspace, including plans, tasks, examples, approvals, and agent execution state.1MIT
- FlicenseNot gradedqualityAmaintenanceEnables MCP-compatible clients and LLM agents to perform full CRUD operations on FHIR resources, query and manipulate clinical data through natural-language prompts, and use document ingestion, semantic search, and terminology lookup against a FHIR backend.-
TDQS
Scored across 21 tools
Tools generally have distinct purposes, but there is some overlap between get_run, get_task_progress, and get_generation_task, which could confuse an agent. Descriptions help clarify, but the boundaries are not perfectly crisp.
All tools share the 'medeval_' prefix and use a consistent snake_case verb_noun pattern (e.g., list_projects, create_workspace, read_document_revision). The one exception, medeval_health, is a minor deviation but does not break overall consistency.
21 tools is slightly heavy but justified given the broad domain covering workspaces, projects, evidence, generation, evaluation, and revisions. The count is within a reasonable range for such a server.
The tool surface covers most core workflows, but there are notable gaps: no workspace update/delete, no get_project, and no cancel/stop operations for generation or evaluation. These are gaps an agent might hit, though the main paths are present.