Skip to main content
Glama
jesse-smith

searchloinc

by jesse-smith
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to searchloinc

No user-submitted related servers found.

    Related Servers

    • loinc-mcp

      robsyc
      A
      license
      A
      quality
      D
      maintenance
      Enables searching LOINC codes and retrieving detailed information including panel members and answer options via the LOINC Search API.
      2
      1
      MIT

    • LCSH MCP Server

      kltng
      A
      license
      C
      quality
      D
      maintenance
      Allows AI assistants to search the Library of Congress Subject Headings (LCSH) through a simple API interface, making it easy to query and retrieve official subject headings and related terms.
      1
      3
      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.
      60 npm
      MIT

    • openfda-mcp-server

      ek-nath
      A
      license
      A
      quality
      D
      maintenance
      Enables LLMs to search FDA drug labels and adverse event data via the OpenFDA API, supporting natural language queries for drug safety information.
      2
      MIT
    • OMOPHub MCP Server by OMOPHub

      OMOPHub MCP Serverofficial

      OMOPHub
      A
      license
      A
      quality
      A
      maintenance
      Provides AI agents with instant access to 10M+ OMOP medical vocabulary concepts for searching, mapping, and navigating clinical codes across SNOMED, ICD-10, RxNorm, LOINC, and more.
      11
      83 npm
      6
      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.2/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool targets a distinct entity (LOINC term, answer list, group, part) or action (search vs. detail). Descriptions clearly differentiate between them, leaving no ambiguity about which tool to use for a given task.

    Naming Consistency5/5

    Tool names follow a consistent verb_noun pattern: 'search_' for searching different entities and 'get_loinc' for fetching details. All names use lowercase and underscores, maintaining a uniform style.

    Tool Count5/5

    Five tools cover the core functionalities of searching and retrieving LOINC-related data without being excessive. The count is well-scoped for a focused LOINC search server.

    Completeness4/5

    The set covers searching for terms, answer lists, groups, and parts, plus detailed term retrieval. However, there is no dedicated detail tool for answer lists or groups; the workflow directs to get_loinc, which may not fully address those entities. This minor gap prevents a perfect score.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources