Skip to main content
Glama
u9401066

pubmed-search-mcp

by u9401066
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to pubmed-search-mcp

No user-submitted related servers found.

    Related Servers

    • ScholarMCP

      lstudlo
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that enables coding agents to search academic papers, ingest full-text PDFs, extract structured details, and manage citations in literature research workflows.
      27
      MIT

    • Scholar MCP Server

      mlintangmz2765
      A
      license
      A
      quality
      C
      maintenance
      Unified MCP server for scientific literature search and extraction, integrating databases like Scopus, OpenAlex, Semantic Scholar, and Unpaywall to enable AI agents to discover papers, track citations, and analyze content.
      27
      MIT

    • sci-bot-mcp

      lnkvv210-eng
      F
      license
      A
      quality
      D
      maintenance
      AI-powered research assistant MCP server for searching academic papers and answering research questions with DOI citations.
      3
      -

    • Deep Research MCP Server

      wlu03
      F
      license
      Not graded
      quality
      D
      maintenance
      An advanced scholarly research MCP server that enables AI assistants to discover, fetch, process, and manage academic papers across multiple sources like arXiv, PubMed, and Semantic Scholar, with capabilities for summarization, citation analysis, and concept relationship extraction.
      2
      -

    • Science MCP

      l4b4r4b4b4
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for AI-assisted research: paper ingestion, semantic search, citation graph traversal, cross-domain knowledge synthesis, and workflow automation.
      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

    A3.6/5.0

    Scored across 41 tools

    Disambiguation3/5

    Most tools are clearly distinct, but there are multiple near-overlaps: build_citation_tree duplicates forward/backward citation functionality also covered by find_citing_articles and get_article_references, and unified_search vs analyze_search_query vs read_session vs read_research_chronicle can blur boundaries. Detailed descriptions help, but with 41 tools, misselection is still plausible.

    Naming Consistency4/5

    Tool names are predominantly verb_noun and consistently snake_case (search_gene, get_gene_details, save_pipeline, delete_pipeline). Minor inconsistencies like 'unified_search' lacking a separate verb and the interchangeable use of get/fetch/find weaken the pattern slightly, but the overall convention is predictable.

    Tool Count2/5

    41 tools far exceeds the 25+ threshold and feels overloaded for a server named pubmed-search-mcp. The server bundles search, citations, fulltext, genes/compounds, pipelines, chronicles, and institutional access into one surface, making the tool set heavy even though each tool has a clear role.

    Completeness5/5

    The tool surface covers the full research workflow: query analysis, unified search, article details, citation/reference exploration, metrics, fulltext, export, notes, and pipeline scheduling. It even adds gene/compound/ClinVar lookup and institutional access diagnostics, so most biomedical literature workflows have no critical dead ends.

    Maintenance

    ActivityActive
    ResponsivenessUnresponsive

    Resources