Skip to main content
Glama
Cicatriiz

cdisc-library-mcp-server

by Cicatriiz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to cdisc-library-mcp-server

No user-submitted related servers found.

    Related Servers

    • cdisc-mcp

      Teninq
      A
      license
      A
      quality
      D
      maintenance
      Exposes CDISC standards data including SDTM, ADaM, CDASH, and Controlled Terminology as tools for AI assistants via the CDISC Library API. It enables users to search standards, retrieve domain variables, and access codelist definitions to facilitate clinical research data management.
      12
      MIT

    • Shiranui

      i-akiya
      A
      license
      C
      quality
      C
      maintenance
      MCP server for retrieving clinical standard content from the CDISC Library, supporting controlled terminology, ADaM, SDTM, CDASH, SEND metadata, and search.
      31
      7
      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

    • cellosaurus-mcp-server

      QuentinCody
      F
      license
      Not graded
      quality
      B
      maintenance
      Enables querying and retrieving cell line records from the Cellosaurus knowledge base via its REST API, including searching, fetching by accession, and accessing release information.
      -

    • Andalusia AI MCP Server

      yasserkh2
      F
      license
      Not graded
      quality
      B
      maintenance
      Exposes six hospital metric tools (entity resolution, member search, cube querying, measure definitions, why-question resolution, investigation execution) as a thin wrapper around FastAPI backend services.
      -
    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

    B3.3/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a clear and distinct purpose. The bc.* and sdtm.* tools are name-spaced to avoid confusion, and other tools like cache.*, call_operation, and search.* are well-separated. No overlapping functionality.

    Naming Consistency4/5

    Most tools follow a domain.action or domain.entity pattern with dots (e.g., bc.categories, sdtm.list). However, call_operation and list_operations use underscores instead of dots, introducing a minor inconsistency in separator style.

    Tool Count5/5

    With 19 tools, the set is well-scoped for a CDISC library API. It covers browsing concepts, SDTM specializations, search, cache management, and generic API operations without being bloated or too sparse.

    Completeness5/5

    The toolset covers the main use cases of a library API: browsing (list, get), searching (query, suggest), and managing cache. For a read-only metadata service, missing create/update/delete operations are not gaps. The generic call_operation adds flexibility.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources