Skip to main content
Glama
Sign In
dingdawg-healthcare-agent

dingdawg-healthcare-agent

by dingdawg
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to dingdawg-healthcare-agent

No user-submitted related servers found.

    Related Servers

    • clinical-mcp

      sarathi-aiml
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables clinical workflows including search and summarization of synthetic FHIR patient records, PubMed literature search, and HIPAA Safe Harbor de-identification of text, via any MCP client.
      MIT

    • CharmHealth MCP Server

      Talha-2
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs and MCP clients to interact with patient records, encounters, and practice information through tools for clinical, scheduling, messaging, and administrative workflows.
      MIT

    • MCP Healthcare Server

      SaadRiaz99
      F
      license
      Not graded
      quality
      D
      maintenance
      An MCP server for clinical workflows with tools for patient lookup, appointment booking, prescriptions, drug interactions, symptom triage, lab results, insurance eligibility, and telehealth, enforcing role-based access control and audit logging.
      2
      -

    • FHIR MCP Server

      Nicholas64181
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables MCP-compatible clients and LLM agents to perform CRUD operations on healthcare resources and query clinical data through natural-language prompts. It also provides document ingestion, semantic search, and medical terminology lookup for interoperability workflows.
      -
    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 4 tools

    Disambiguation5/5

    Each tool targets a distinct healthcare function—patient intake, clinical summarization, HIPAA compliance, and scheduling. There is no overlap in purpose or output, making misselection unlikely.

    Naming Consistency4/5

    All tool names follow a consistent <domain>_<function> snake_case pattern (e.g., patient_intake, hipaa_check). The suffix types vary between nouns and verbs, but the overall naming is predictable and uniform.

    Tool Count4/5

    Four tools is a reasonable, focused set for a healthcare agent, each earning its place in the workflow. The count is slightly lean but still well-scoped.

    Completeness3/5

    The set covers intake, summarization, compliance, and scheduling, but lacks basic CRUD operations for patients or appointments (e.g., no get, update, or delete). This leaves notable gaps for ongoing management.

    Resources