Skip to main content
Glama
robsyc

loinc-mcp

by robsyc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to loinc-mcp

No user-submitted related servers found.

    Related Servers

    • searchloinc

      jesse-smith
      A
      license
      A
      quality
      B
      maintenance
      Enables LLMs to search LOINC terms with free-text, relevance-ranked, and faceted queries via the LOINC Search API, mirroring the loinc.org/search experience.
      5
      MIT

    • mcp-umls

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables searching clinical terms and codes across UMLS vocabularies, retrieving concept details, listing source-asserted atoms, and crosswalking codes between vocabularies via the NLM UMLS Terminology Services REST API.
      MIT

    • medical-codes

      pipeworx-io
      A
      license
      Not graded
      quality
      B
      maintenance
      Search medical codes including ICD-10, LOINC, and clinical terms for conditions, procedures, and drugs via natural language queries.
      5 npm
      MIT

    • rxnorm

      pipeworx-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables users to query standardized drug concepts from the National Library of Medicine's RxNorm, including name-based search, drug property retrieval, and related concept exploration via the RxNav REST API.
      1 npm
      MIT

    • SNOMED CT MCP Server

      OrgLance
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables querying and browsing SNOMED CT medical terminology concepts, including search, details, and hierarchy navigation via MCP tools.
      3
      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

    A4/5.0

    Scored across 2 tools

    Disambiguation5/5

    get_code retrieves details for a specific code, while search finds codes by text. Their purposes are completely distinct, leaving no ambiguity.

    Naming Consistency4/5

    Both names follow a simple verb pattern, but get_code uses verb_noun while search is just a verb. Slight inconsistency, though both are clear and predictable.

    Tool Count3/5

    With only 2 tools, the server is minimal but covers basic search and retrieval for LOINC. It is slightly thin for a domain with many potential operations, yet acceptable for a focused utility.

    Completeness3/5

    The set covers core lookup and search but lacks operations like listing by class, navigating hierarchies, or batch queries. Notable gaps exist, but the two tools serve essential needs.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources