Pubmed
Server Details
PubMed MCP — wraps the NCBI E-utilities API (biomedical literature, free, no auth)
Glama couldn't complete the latest health check. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.
If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.
- Status
- Unhealthy
- Uptime
- 40.6% over 42 days
- Last Tested
- Transport
- Streamable HTTP
- URL
- Repository
- pipeworx-io/mcp-pubmed
- GitHub Stars
- 1
- Server Listing
- mcp-pubmed
TDQS
Scored across 43 tools
Most tools have long, carefully differentiated descriptions, but the set contains literal duplicates: the deprecated aliases get_citations/get_full_text/get_related_articles behave identically to their pubmed_* counterparts, and ask_pipeworx / ask_pipeworx_beta / ask_pipeworx_grounded / deep_research form a cluster of overlapping 'ask' entry points. An agent can still pick correctly if it reads carefully, but the aliasing and near-duplicate routers invite misselection.
Names are predominantly snake_case, but conventions are mixed: some are verb_noun (get_abstract, search_pubmed, compare_entities) while others are noun_verb (entity_profile, polymarket_edges, pipeworx_feedback), and the PubMed tools split between prefixed (pubmed_get_citations) and unprefixed (get_summary, get_abstract) forms. Readable, but not a single predictable pattern.
43 tools is far above a well-scoped set, and the surface is wildly over-broad for a server named 'Pubmed' — it bundles Polymarket arbitrage, npm dependency scanning, AI-visibility auditing, memory, and subscriptions alongside the PubMed tools. Each tool is individually plausible, but the count and scope mismatch is severe.
The PubMed subset is reasonably complete for read-only literature work (search, summary, abstract, full text, citations, related articles, integrity, trends, evidence landscape), and the gateway extras add breadth. However, the coexistence of deprecated alias tools rather than a clean surface, plus an unclear overall domain, leaves the set feeling like an incomplete grab-bag rather than a coherent, finished API.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "when-will-bitcoin-hit-150k" - }, - { - "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" - } -]New value: +[ + { + "market": "will-kristi-noem-win-the-2028-republican-presidential-nomination" + }, + { + "market": "https://polymarket.com/event/will-kristi-noem-win-the-2028-republican-presidential-nomination" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."New value: +"Polymarket slug (\"will-kristi-noem-win-the-2028-republican-presidential-nomination\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
1 tool update
- Changed
polymarket_kalshi_spread1 field changed- changed
Input schema / examplesPrevious value: -[ - { - "topic": "fed" - }, - { - "topic": "btc" - } -]New value: +[ + { + "topic": "fed" + }, + { + "topic": "btc" + }, + { + "topic": "bitcoin" + }, + { + "topic": "fed rate decision" + } +]
2 tool updates
- Changed
bet_research2 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "market": "will-bitcoin-reach-100k-in-july-2026" - }, - { - "market": "https://polymarket.com/event/will-bitcoin-hit-150k-by-june-30-2026" - } -]New value: +[ + { + "market": "when-will-bitcoin-hit-150k" + }, + { + "market": "https://polymarket.com/event/when-will-bitcoin-hit-150k" + } +] - changed
Input schema / properties / market / descriptionPrevious value: -"Polymarket slug (\"will-bitcoin-hit-150k-by-june-30-2026\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k by June 30?\")"New value: +"Polymarket slug (\"when-will-bitcoin-hit-150k\"), full URL (\"https://polymarket.com/event/...\"), or question text (\"Will Bitcoin hit $150k?\"). Dated slugs stop resolving once they settle — Polymarket de-indexes resolved markets — so prefer an undated one."
- Changed
polymarket_kalshi_spread1 field changed- changed
Input schema / properties / topic / descriptionPrevious value: -"Pre-mapped: fed | btc | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president"New value: +"Subject to compare. Canonical keys: fed | btc | eth | cpi | gdp | sp500 | recession | next_pope | next_uk_pm | next_israel_pm | 2028_president — but aliases and keywords resolve too (\"bitcoin\", \"fed rate decision\", \"ethereum\", \"inflation\", \"s&p 500\", \"us recession\", \"next pope\", \"2028 election\"). Check resolution.topic_matched_by in the response: \"exact\"/\"alias\" is a curated pairing, \"phrase\"/\"token\" is a keyword guess."
1 tool update
- Changed
get_summary6 fields changed- added
Output schema / properties / articles / items / properties / author_detailsAdded value: +{ + "description": "Per-author detail, index-aligned with authors[]: name, affiliations (verbatim from efetch XML), and any emails found inside them", + "items": { + "properties": { + "affiliations": { + "description": "Verbatim AffiliationInfo/Affiliation strings from efetch XML; empty if the record has none", + "items": { + "type": "string" + }, + "type": "array" + }, + "emails": { + "description": "Email addresses found inside this author's affiliation strings by plain regex; empty if none present", + "items": { + "type": "string" + }, + "type": "array" + }, + "name": { + "description": "Author name as indexed by esummary (e.g. \"Smith JA\")", + "type": "string" + } + }, + "required": [ + "name", + "affiliations", + "emails" + ], + "type": "object" + }, + "type": "array" +} - changed
Output schema / properties / articles / items / properties / authors / descriptionPrevious value: -"Per-author name, affiliations (verbatim from efetch XML), and any emails found inside them"New value: +"Author names as plain strings, e.g. \"Smith JA\" (unchanged shape; see author_details for affiliations/emails)" - removed
Output schema / properties / articles / items / properties / authors / items / propertiesRemoved value: -{ - "affiliations": { - "description": "Verbatim AffiliationInfo/Affiliation strings from efetch XML; empty if the record has none", - "items": { - "type": "string" - }, - "type": "array" - }, - "emails": { - "description": "Email addresses found inside this author's affiliation strings by plain regex; empty if none present", - "items": { - "type": "string" - }, - "type": "array" - }, - "name": { - "description": "Author name as indexed by esummary (e.g. \"Smith JA\")", - "type": "string" - } -} - removed
Output schema / properties / articles / items / properties / authors / items / requiredRemoved value: -[ - "name", - "affiliations", - "emails" -] - changed
Output schema / properties / articles / items / properties / authors / items / typePrevious value: -"object"New value: +"string" - changed
Output schema / properties / articles / items / requiredPrevious value: -[ - "pmid", - "title", - "authors", - "journal", - "pub_date", - "volume", - "issue", - "pages", - "pub_types", - "doi", - "url" -]New value: +[ + "pmid", + "title", + "authors", + "author_details", + "journal", + "pub_date", + "volume", + "issue", + "pages", + "pub_types", + "doi", + "url" +]
1 tool update
- Changed
get_summary4 fields changed- changed
Output schema / properties / articles / items / properties / authors / descriptionPrevious value: -"List of author names"New value: +"Per-author name, affiliations (verbatim from efetch XML), and any emails found inside them" - added
Output schema / properties / articles / items / properties / authors / items / propertiesAdded value: +{ + "affiliations": { + "description": "Verbatim AffiliationInfo/Affiliation strings from efetch XML; empty if the record has none", + "items": { + "type": "string" + }, + "type": "array" + }, + "emails": { + "description": "Email addresses found inside this author's affiliation strings by plain regex; empty if none present", + "items": { + "type": "string" + }, + "type": "array" + }, + "name": { + "description": "Author name as indexed by esummary (e.g. \"Smith JA\")", + "type": "string" + } +} - added
Output schema / properties / articles / items / properties / authors / items / requiredAdded value: +[ + "name", + "affiliations", + "emails" +] - changed
Output schema / properties / articles / items / properties / authors / items / typePrevious value: -"string"New value: +"object"
1 tool update
- Changed
get_summary4 fields changed- changed
Input schema / examplesPrevious value: -[ - { - "ids": "33579999,34567890" - } -]New value: +[ + { + "ids": [ + "33301246", + "32000001" + ] + }, + { + "ids": "33579999,34567890" + } +] - changed
Input schema / properties / ids / descriptionPrevious value: -"Comma-separated PubMed IDs (e.g., \"33579999,34567890\")"New value: +"PubMed IDs, either as an array ([\"33579999\",\"34567890\"] — what search_pubmed returns) or as a comma-separated string (\"33579999,34567890\")." - added
Input schema / properties / ids / itemsAdded value: +{ + "type": "string" +} - changed
Input schema / properties / ids / typePrevious value: -"string"New value: +[ + "string", + "array" +]
Related MCP Connectors
Search biomedical literature, get article details, find related articles, and explore MeSH terms
Crossref MCP — wraps the Crossref REST API (academic papers, free, no auth)
NCBI E-utilities MCP — federated Entrez search/fetch.
Nobel MCP — wraps the Nobel Prize API v2 (free, no auth)
Related MCP Servers
- AlicenseAqualityDmaintenanceExposes NCBI PubMed as MCP tools for searching literature, fetching abstracts, exploring citation graphs, and finding author publications without requiring an API key.4MIT
- FlicenseNot gradedqualityDmaintenanceMCP server for NCBI PubMed E-utilities with rate limiting, enabling article search, metadata retrieval, full-text access, BibTeX generation, and bibliography management.-
- AlicenseNot gradedqualityDmaintenanceMCP server for searching PubMed scientific articles using NCBI E-utilities API. Supports query, fetch summaries, and full text retrieval with caching and rate limiting.30 npmISC
- AlicenseAqualityDmaintenanceA local MCP server enabling PubMed, PMC, and iCite API access via stdio for tools like search, fetch, full text, and citation counts.1070 npm2MIT
Glama MCP Gateway
Add one secure layer between your agents and this server.