Skip to main content
Glama
Sign In
m2ai-mcp-servers

mcp-ratchet-clinical-charting

by m2ai-mcp-servers
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-ratchet-clinical-charting

No user-submitted related servers found.

    Related Servers

    • FHIR MCP Server

      Sergei0313
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients such as Claude Desktop to perform full CRUD operations on Fast Healthcare Interoperability Resources and query clinical data through natural-language prompts. It also provides document ingestion with semantic search, a RAG-ready retrieval pipeline, and LOINC terminology lookup and validation.
      -

    • FHIR MCP Server

      HeleneUnal4227
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP clients such as Claude Desktop to interact with a FHIR-compliant backend, performing full CRUD operations on clinical resources through natural-language prompts. It also supports AI-powered document ingestion, semantic search over processed documents, LOINC terminology lookup, and synthetic FHIR test data generation.
      -

    • MCP Healthcare System

      Sudip-Pandit
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A production-grade MCP server that enables AI assistants to securely manage healthcare data through clinical tools for patient vitals, lab results, and medication ordering. It prioritizes security and compliance with features like HIPAA-ready audit logging, PII redaction, and role-based access control.
      -

    • FHIR MCP Server

      SusanneRangel66684
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients such as Claude Desktop to perform CRUD operations on FHIR resources and query or manipulate clinical data through natural-language prompts, with document processing, semantic search, and LOINC terminology lookup.
      -
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.9/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a distinct, non-overlapping purpose: searching for patients, retrieving visit history, and creating new visit notes. No ambiguity exists between them.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (search_patient, get_patient_history, create_visit_note) using snake_case, making it predictable and easy to understand.

    Tool Count4/5

    With only 3 tools, it is on the lower end but still appropriate for a focused clinical charting server. They cover the core workflow of searching, reviewing history, and creating notes without unnecessary bloat.

    Completeness3/5

    The tool set covers essential operations (search, history, create) but lacks update and delete functionalities for visit notes, which are notable gaps for a complete CRUD lifecycle in clinical charting.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources