Skip to main content
Glama
MiltonPolanco

Clinic Laboratory MCP Server

by MiltonPolanco
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Clinic Laboratory MCP Server

No user-submitted related servers found.

    Related Servers

    • HealthLedger MCP

      Cole-Will-I-Am
      A
      license
      C
      quality
      B
      maintenance
      A local-first, model-agnostic MCP server that stores personal health data in a SQLite file and provides analysis-ready views for any AI client to log, retrieve, and reason over health records.
      79
      MIT

    • sharp-on-fhir-mcp

      TerminallyLazy
      A
      license
      Not graded
      quality
      C
      maintenance
      A clean-room SHARP-on-MCP compliant FHIR R4 MCP server that enables AI agents to interact with any FHIR R4 endpoint using SHARP context headers, without server-side OAuth. It provides clinical tools, lab results, imaging, and interactive MCP-UI dashboards.
      MIT

    • Intelligent Medical Assistant

      sp2learn
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server and web application that enables natural language medical queries and patient data analysis powered by Gemini AI. It allows users to track and analyze patient biometrics, including vitals, sleep patterns, and laboratory results, through a comprehensive set of automated medical tools.
      -

    • health-example

      pietrodileo
      A
      license
      Not graded
      quality
      B
      maintenance
      This MCP server enables secure, read-only access to synthetic preventive-care patient records and bounded IRIS namespace health metrics through a small set of allowlisted, parameterized tools.
      1
      MIT

    • featherless

      TerminallyLazy
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables interaction with FHIR R4 healthcare data through SHARP-on-MCP tools, including search, read, and clinical context aggregation, with built-in Chart.js dashboards for visualizing lab trends, vitals, and patient data.
      3 npm
      3
      MIT
    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.6/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action in the lab workflow: scheduling, recording, searching, retrieving, comparing, and listing pending exams. There is no meaningful overlap between tool purposes, so an agent can reliably select the right tool.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern, such as record_lab_result, schedule_lab_exam, and list_pending_exams. Modifiers like 'latest' and 'pending' are used uniformly and do not break the convention.

    Tool Count5/5

    Six tools is a well-scoped count for a laboratory-focused server. Each tool covers a clear part of the domain without unnecessary duplication or bloat.

    Completeness4/5

    The core lab workflow is well covered: search patients, schedule exams, record results, list pending exams, and retrieve/compare results. Minor gaps exist, such as no explicit update/cancel flow for scheduled exams or recorded results, but agents can work around these for typical lab tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources