F
licenseA
qualityD
maintenanceEnables users to interact with the CUF health portal to retrieve patient information, appointments, clinical documents, invoices, and prescriptions through natural language.
12
2
-
jcs-mcp
Related Servers
Alternatives to jcs-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceExposes tools from the Ecuro Light API for managing clinical appointments, patient records, and clinic availability. It enables users to perform healthcare management tasks such as scheduling, patient search, and report generation through MCP-compatible clients.-
- FlicenseNot gradedqualityBmaintenanceExposes Garmin Connect health data (steps, sleep, HR, HRV, stress, activities, etc.) as tools for MCP-compatible clients like Claude.-
- AlicenseBqualityDmaintenanceExposes the ProDoctor Cloud API as MCP tools for AI agents to manage appointments, patients, users, and procedures.18MIT
- AlicenseCqualityBmaintenanceExposes the Feegow clinic management API as MCP tools for agents, enabling scheduling, patient management, and more via natural language.97MIT
- FlicenseAqualityCmaintenanceEnables Claude to query and manage home-care operations including clients, visits, and compliance, with schema-validated write tools and a tamper-evident audit log.5-
TDQS
A3.8/5.0
Scored across 11 tools
Disambiguation3/5
Most tools are clearly distinct, but list_timeline and list_notifications overlap significantly—both return lists of messages with similar arguments and point to get_message for details. Additionally, get_document_content and download_document both handle attachment URIs, which could cause misselection without careful reading.
Naming Consistency4/5
The naming pattern is predominantly verb_noun (get_patient_info, list_appointments, download_document, parse_prescription), which is consistent and predictable. The outlier is jcs_login, which breaks the pattern by using a product prefix and lacking a clear object, introducing minor inconsistency.
Tool Count5/5
With 11 tools, the server is well-scoped for a healthcare portal client. It covers authentication, data retrieval, document access, and a niche parsing feature without being bloated or too thin. Each tool serves a distinct purpose in the overall workflow.
Completeness4/5
The tool surface provides a complete read-only lifecycle for the domain: listing and getting messages, appointments, prescriptions, invoices, and documents. Minor gaps exist, such as no ability to search, mark-as-read, or perform actions like scheduling appointments, but these are not core to the apparent purpose.
Maintenance
ActivityInactive
ResponsivenessNo issues