Skip to main content
Glama
hannesill

M4

by hannesill
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to M4

No user-submitted related servers found.

    Related Servers

    • M3

      rafiattrach
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables querying MIMIC-IV medical data using natural language through MCP clients, with support for local DuckDB and cloud BigQuery backends.
      77
      MIT

    • OMOP MCP Server

      aandresalvarez
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language exploration of OMOP CDM databases for concept discovery, patient count queries, and cohort SQL generation with support for multiple database backends.
      1
      MIT

    • Clinical MCP

      karishmadhingra30
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables exploring a synthetic electronic health record via natural language, including patient demographics, encounters, notes, and medications, with optional write support for adding synthetic progress notes.
      -

    • medmcp

      GattaniAkshit
      F
      license
      A
      quality
      B
      maintenance
      Enables language models to query a clinical relational database through a small set of validated, row-capped tools, with evaluation of answerability and data leakage.
      4
      -

    • Claims Data MCP Server

      Rutvikmerai
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables natural language querying of healthcare claims data by exposing a SQLite database with read-only SQL tools, allowing users to ask questions in plain English and get answers backed by real database queries.
      -
    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

    B3.4/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: database exploration (get_database_schema, get_table_info, execute_query), note handling (search_notes, list_patient_notes, get_note), cohort building (cohort_builder, query_cohort), and meta tasks (capabilities, list_datasets). The deprecated set_dataset is clearly marked, avoiding confusion.

    Naming Consistency4/5

    Most tools follow a consistent verb_noun snake_case pattern (e.g., execute_query, get_note, list_datasets). However, 'capabilities' is a plain noun and 'cohort_builder' is noun_noun, breaking the pattern slightly.

    Tool Count5/5

    11 tools is well-scoped for a medical data analysis server. Each tool covers a necessary operation without overlap or redundancy, and the count feels balanced for the domain.

    Completeness4/5

    The tool surface covers core workflows: database discovery, SQL querying, note retrieval and search, and cohort filtering. A minor gap is the lack of a direct patient demographics tool, but SQL queries can retrieve that information.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources