Skip to main content
Glama
Sign In
healthcare-ai

healthcare-ai

by CSOAI-ORG
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to healthcare-ai

No user-submitted related servers found.

    Related Servers

    • MCP Healthcare System

      Sudip-Pandit
      A
      license
      Not graded
      quality
      Not graded
      maintenance
      A production-grade MCP server that enables AI assistants to securely manage healthcare data through clinical tools for patient vitals, lab results, and medication ordering. It prioritizes security and compliance with features like HIPAA-ready audit logging, PII redaction, and role-based access control.
      -

    • FHIR MCP Server

      Leod22090
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients to perform full CRUD operations on FHIR resources, process documents, run semantic searches, resolve LOINC terminology, and query or manipulate clinical data through natural-language prompts. It provides a standardized interface to connect with FHIR-compliant backends and RAG-ready document retrieval.
      -

    • Heavenly Health Protocol

      xbirimensah
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI clients to securely access, query, and mutate normalized user-controlled health data (e.g., from Apple Health or Supabase) through a bounded set of MCP tools, with optional OAuth and sandboxed deployment.
      MIT

    • FHIR MCP Server

      Desai42382
      F
      license
      Not graded
      quality
      A
      maintenance
      Enables LLM-based agents and MCP-compatible clients to perform full CRUD operations on FHIR resources, plus AI-powered document ingestion, semantic search, and LOINC terminology lookup. Users can query and manipulate clinical data using natural-language prompts.
      -
    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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool targets a distinct regulatory framework (general AI safety, EU MDR, FDA SaMD, HIPAA), with no overlap in purpose. An agent can easily differentiate them.

    Naming Consistency4/5

    Names follow a pattern of domain/regulation plus topic, but vary between 'safety', 'compliance', and 'assessment' (e.g., clinical_ai_safety vs. eu_mdr_compliance vs. fda_ai_assessment). Slight inconsistency but still clear and predictable.

    Tool Count5/5

    Four tools is well-scoped for a healthcare AI compliance server, covering major regulations without excess. Each tool serves a necessary role.

    Completeness4/5

    Covers core regulatory areas (safety, EU MDR, FDA, HIPAA), but misses some potentially relevant frameworks like GDPR or ISO standards. Minor gaps that don't severely hinder the agent.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources