Skip to main content
Glama
healthchainai

HealthChain

by healthchainai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to HealthChain

No user-submitted related servers found.

    Related Servers

    • FHIR MCP Server

      the-momentum
      A
      license
      A
      quality
      D
      maintenance
      Enables LLM-based agents to interact with FHIR healthcare data through natural language prompts, providing full CRUD operations on FHIR resources, document processing, and semantic search capabilities.
      13
      101
      MIT

    • FhirMCP

      xSoVx
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables LLMs to securely interact with FHIR healthcare servers and HL7 terminology services. Provides comprehensive healthcare data operations with built-in PHI protection, audit logging, and SMART on FHIR authentication.
      MIT

    • FHIR MCP Server

      wso2
      A
      license
      A
      quality
      D
      maintenance
      Provides seamless integration with FHIR APIs, enabling AI/LLM tools to search, retrieve, and analyze clinical healthcare data with support for SMART-on-FHIR authentication and multiple transport protocols.
      7
      92 PyPI
      137
      Apache 2.0

    • MCP FHIR Server

      mrosata
      F
      license
      A
      quality
      D
      maintenance
      Provides read/write access to any FHIR-compliant healthcare API with built-in validation, supporting resource management, search operations, and granular permissions through natural language.
      5
      1
      -

    • HealthChain MCP Server

      Kunwgh
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access validated FHIR/EHR data and healthcare tools through the Model Context Protocol, supporting secure clinical data processing and LangChain integration.
      Apache 2.0
    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.2/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: building, validating, loading, retrieving, resolving references, and terminology lookup. No two tools overlap in functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using lowercase and underscores, e.g., build_resource, load_bundle, get_resources, lookup_code. This makes the API predictable.

    Tool Count5/5

    With 8 tools, the set is well-scoped for a FHIR utility server, covering essential operations without being bloated or too sparse.

    Completeness4/5

    The set covers building, validating, loading, and reading FHIR resources, as well as reference resolution and terminology lookup. Minor gaps like missing update/delete tools or limited build resource types prevent a perfect score.

    Maintenance

    ActivitySlowing
    ResponsivenessWithin a week

    Resources