Skip to main content
Glama
Nniol

Hospital Data MCP Server

by Nniol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to Hospital Data MCP Server

No user-submitted related servers found.

    Related Servers

    • hospital

      GTA7-Lab
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables access to patient records, symptom triage, appointment scheduling, and hospital data lookup through a JSON-RPC MCP interface with HTTP and stdio transports.
      -

    • 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

    • Alexa+ LifeOps

      vatsShashwat07
      A
      license
      Not graded
      quality
      B
      maintenance
      Exposes clinical triage and ambient care tools over the MCP 2025-11-25 Streamable HTTP transport, letting voice-driven clients analyze blood pressure, heart rate and SpO2, schedule medication reminders, retrieve patient profiles and trigger simulated emergency escalation. Tool orchestration can be driven by AWS Bedrock Converse multi-turn reasoning, with a deterministic rule-based fallback when cloud credentials are absent.
      1
      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.5/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools target distinct data types (drug info, vital signs, patient info, medical info). The only overlap is wxoGetPatient360, which explicitly aggregates the individual patient-related getters, but its purpose as a composite view is clear from the description.

    Naming Consistency5/5

    All tools follow the exact same 'wxoGet' + PascalCase noun pattern, creating a predictable and uniform naming convention. The minor typo in 'DrugInterations' does not affect the consistent structure.

    Tool Count5/5

    With 8 tools, the server is well-scoped for a hospital data access API. The number is within the ideal 3-15 range and each tool serves a clear query purpose.

    Completeness3/5

    The tool set covers core patient, medical, vital signs, and drug-related queries, but lacks search/list operations (e.g., find patients, search drugs) and any write capabilities. While likely read-only, the absence of basic lookup endpoints creates notable gaps for general hospital data exploration.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources