Skip to main content
Glama
msuicaut

MeSH MCP

by msuicaut
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to MeSH MCP

No user-submitted related servers found.

    Related Servers

    • med-lit-mcp

      fc0web
      A
      license
      A
      quality
      C
      maintenance
      Enables searching medical literature, clinical trials, drug information, guidelines, and medical fee schedules directly from Claude, returning only original sources and text without medical judgment.
      9
      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

    • Assay MCP Server

      cirruslycurious
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables Claude Desktop to search, retrieve summaries, and explore documents from an Assay document library.
      9 npm
      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
      102 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.7/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: search_mesh finds descriptors, get_mesh_record retrieves full cataloging details, get_mesh_qualifiers fetches allowable subheadings, and get_mesh_tree provides hierarchical context. There is no functional overlap—an agent can easily distinguish when to use each tool based on the specific metadata needed.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern with 'mesh' as a prefix: search_mesh, get_mesh_record, get_mesh_qualifiers, get_mesh_tree. The naming is perfectly uniform, using snake_case throughout with clear, descriptive action-object pairs.

    Tool Count5/5

    Four tools is well-scoped for a MeSH lookup server, covering the essential workflow: search, retrieve full record, get qualifiers, and understand hierarchy. Each tool earns its place without redundancy, and the count is appropriate for the domain's focused purpose.

    Completeness5/5

    The toolset provides complete coverage for MeSH descriptor lookup and cataloging support. It includes search, full record retrieval, qualifier access, and tree hierarchy—covering the entire lifecycle from discovery to detailed metadata without any obvious gaps for the server's stated purpose.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources