Skip to main content
Glama
asanm11611622ubca006

Patient Data MCP Server

by asanm11611622ubca006
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Patient Data MCP Server

No user-submitted related servers found.

    Related Servers

    • clinic-mcp-server

      leomengineer
      F
      license
      A
      quality
      C
      maintenance
      Exposes a clinic's knowledge base and structured records to Claude Desktop as callable tools, with read tools grounded with citations and write tools gated behind approval.
      4
      -

    • customer-data-mcp

      Haseeb-Ahmed-AI
      F
      license
      A
      quality
      C
      maintenance
      Enables Claude Desktop to answer natural-language questions about customers by exposing search, profile, order history, status filter, and spend statistics tools backed by local mock data, with a single-file swap path to Oracle AI Agent Studio later.
      5
      -

    • MCP Alchemy

      runekaagaard
      A
      license
      Not graded
      quality
      B
      maintenance
      Connects Claude Desktop directly to databases, allowing it to explore database structures, write SQL queries, analyze datasets, and create reports through an API layer with tools for table exploration and query execution.
      3,220 PyPI
      419
      Mozilla Public 2.0

    • SQLite MCP Server

      sparxit
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language interaction with local SQLite databases through Claude Desktop, translating plain English queries into SQL for data analysis and exploration.
      3
      MIT

    • PodQuery

      rilhia
      A
      license
      A
      quality
      B
      maintenance
      Enables Claude Desktop to query and analyze diabetes data from Omnipod 5 and Glooko through natural language, providing clinical audit and triage insights such as time in range, trends, and bolus analysis.
      12
      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

    A4.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct query: by ID, by age, by disease, by name, list diseases, and overall statistics. There is no overlap in their purposes, even though several search patients in different ways.

    Naming Consistency3/5

    Tool names use a mix of verbs: get, list, find, search. While all are snake_case and readable, the pattern is not consistent across the set (e.g., 'get_patient_by_id' vs 'find_patients_by_disease').

    Tool Count5/5

    With 6 tools, the server is well-scoped for a read-only patient data querying purpose. Each tool covers a distinct and necessary operation without unnecessary bloat.

    Completeness4/5

    The set covers all obvious read-only query needs: lookup by ID, filtering by age, disease, name, listing available diseases, and summary statistics. Missing write operations (create/update/delete) may be out of scope, but a generic 'list all patients' could be a minor gap.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources