_ registry / mcp http-sse · checked 1h ago

pubmed-mcp-server

https://pubmed.caseyjhand.com

Registry code: 33f28d7c947973db

api record

Use the pubmed_* tools to search PubMed and PubMed Central, fetch article metadata and full text, format citations, and find related articles via NCBI's E-utilities. Articles are keyed by PMID (integer); PMC full text by PMCID (`PMC` prefix); most also carry a DOI. Typical flow: `pubmed_search_articles` → `pubmed_fetch_articles` → `pubmed_fetch_fulltext`. When PubMed itself comes up empty (preprints, EPMC-only OA), broaden via `pubmed_europepmc_search`, then `pubmed_europepmc_fetch` with a hit's `source` + `epmcId` for its complete abstract. Prefer deterministic resolvers when inputs are…

endpoint
https://pubmed.caseyjhand.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is pubmed-mcp-server live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is pubmed-mcp-server free to use?
Yes — the hub reached it with no key and no payment.
What tools does pubmed-mcp-server have?
11 tools: pubmed_search_articles, pubmed_lookup_mesh, pubmed_europepmc_fetch, pubmed_find_related, pubmed_spell_check, pubmed_convert_ids, pubmed_europepmc_search, pubmed_fetch_fulltext, ….
Is pubmed-mcp-server safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.4%· all time 99.6%

latency
494ms

last good check

priced tools
0

of 11 tools

_ answered our checks, 90 days 494 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
used for
  • search pubmed articles
  • fetch article full text
  • format citations
  • find related articles
  • look up mesh terms
takes → gives
text → data, text
tools
11 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 11 tools
11 never probed 0 of 11 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • pubmed_search_articles reads unknown 24h ago

    Search PubMed with full query syntax, filters, and date ranges. Returns PMIDs and optional brief summaries. Supports field-specific filters (author, journal, MeSH terms), common filters (language, species, free full text), and pagination via offset for paging through large result sets.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "sort": {
          "enum": [
            "relevance",
            "pub_date",
            "author",
            "journal"
          ],
          "type": "string",
          "default": "relevance",
          "description": "Sort order: relevance (default), pub_date (newest first), author, or journal"
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "PubMed search query (supports full NCBI syntax). Must carry a search term: a value that is blank once markup, bracketed field tags (`[pdat]`), parentheses, and invisible characters such as a zero-width space are disregarded is rejected rather than sent to PubMed."
        },
        "author": {
          "type": "string",
          "description": "Filter by author name (e.g. \"Smith J\"). An empty string applies no filter; a value of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 9998,
          "minimum": 0,
          "description": "Result offset for pagination (0-based). PubMed serves at most the first 9999 records of a result set, so this caps at 9998; narrow the query or add filters to reach anything beyond it."
        },
        "journal": {
          "type": "string",
          "description": "Filter by journal name. An empty string applies no filter; a value of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected."
        },
        "species": {
          "enum": [
            "humans",
            "animals"
          ],
          "type": "string",
          "description": "Filter by species"
        },
        "language": {
          "type": "string",
          "description": "Filter by language (e.g. \"english\"). An empty string applies no filter; a value of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected."
        },
        "dateRange": {
          "type": "object",
          "required": [
            "minDate",
            "maxDate"
          ],
          "properties": {
            "maxDate": {
              "type": "string",
              "pattern": "^$|^\\d{4}([/\\-.]\\d{1,2}([/\\-.]\\d{1,2})?)?$",
              "description": "End date (YYYY/MM/DD, YYYY/MM, or YYYY). Must be a real calendar date — `2023/02/29` is rejected. Leaving it empty drops the whole date range, not just this bound; for no upper bound pass a wide sentinel such as `3000`."
            },
            "minDate": {
              "type": "string",
              "pattern": "^$|^\\d{4}([/\\-.]\\d{1,2}([/\\-.]\\d{1,2})?)?$",
              "description": "Start date (YYYY/MM/DD, YYYY/MM, or YYYY). Must be a real calendar date — `2023/02/29` is rejected. Leaving it empty drops the whole date range, not just this bound; for no lower bound pass a wide sentinel such as `1000`."
            },
            "dateType": {
              "enum": [
                "pdat",
                "mdat",
                "edat"
              ],
              "type": "string",
              "default": "pdat",
              "description": "Date type: pdat (publication), mdat (modification), edat (entrez)"
            }
          },
          "description": "Filter by date range. The filter is applied only when both `minDate` and `maxDate` are non-empty; either one empty disables the entire date range. A partial date covers its whole year or month, and a range whose `minDate` falls after its `maxDate` is rejected: `2024/06` to `2024` is valid, `2024/07` to `2024/06/30` is not."
        },
        "meshTerms": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Filter by MeSH terms. Multiple terms are AND'd — all must match. Empty strings are skipped; an element of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected."
        },
        "maxResults": {
          "type": "integer",
          "default": 20,
          "maximum": 1000,
          "minimum": 0,
          "description": "Maximum results to return. 0 returns only `totalCount`."
        },
        "hasAbstract": {
          "type": "boolean",
          "description": "Only include articles with abstracts"
        },
        "freeFullText": {
          "type": "boolean",
          "description": "Only include free full text articles"
        },
        "summaryCount": {
          "type": "integer",
          "default": 0,
          "maximum": 50,
          "minimum": 0,
          "description": "Fetch brief summaries for top N results (0 = PMIDs only). Above the 50 cap, pass the remaining PMIDs to pubmed_fetch_articles."
        },
        "publicationTypes": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Filter by publication type (e.g. \"Review\", \"Clinical Trial\", \"Meta-Analysis\"). Multiple values are OR'd — any match qualifies. Empty strings are skipped; an element of only whitespace, invisible characters, markup, parentheses, brackets, or double quotes is rejected."
        }
      },
      "additionalProperties": false
    }
    arguments 119 lines
  • pubmed_lookup_mesh reads unknown 24h ago

    Search and explore the MeSH (Medical Subject Headings) controlled vocabulary. Returns descriptor records with tree numbers, scope notes, and entry terms, plus pagination via offset for paging past the maxResults cap.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "MeSH descriptor name or free-text term to look up. Must carry a term: a value of only whitespace or invisible characters, such as a zero-width space, is rejected rather than searched."
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Result offset for pagination (0-based). Pass the `nextOffset` from the previous response to get the following page; the exact-descriptor match is pinned to the first page only."
        },
        "maxResults": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum results"
        },
        "includeDetails": {
          "type": "boolean",
          "default": true,
          "description": "Fetch full MeSH records (scope notes, tree numbers, entry terms)"
        }
      },
      "additionalProperties": false
    }
    arguments 34 lines
  • pubmed_europepmc_fetch reads unknown 21h ago

    Fetch complete Europe PMC records — including the full, untruncated abstract — for records addressed by `source` plus `epmcId`. Pairs with `pubmed_europepmc_search`, which returns bounded `abstractSnippet` values and flags cut ones with `abstractTruncated: true`; pass those hits' `source` and `epmcId` here to read the whole abstract. This is the retrieval path for preprint (`PPR`), patent (`PAT`), and Agricola (`AGR`) records, which frequently carry no PMID and no DOI, so `pubmed_fetch_articles` and `pubmed_fetch_fulltext` cannot address them. Up to 25 records per call. Set `maxResponseCharacters` to bound the whole response: records past the ceiling are deferred whole and listed in `deferred.records` for a follow-up call.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "records"
      ],
      "properties": {
        "records": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "source",
              "epmcId"
            ],
            "properties": {
              "epmcId": {
                "type": "string",
                "pattern": "^[A-Za-z0-9][A-Za-z0-9._-]*$",
                "maxLength": 64,
                "description": "Europe PMC's own record id within that source. Copy it from the search hit's `epmcId` — for `MED` records this is the PMID; for the other sources it is an EPMC-native accession."
              },
              "source": {
                "enum": [
                  "MED",
                  "PMC",
                  "PPR",
                  "PAT",
                  "AGR"
                ],
                "type": "string",
                "description": "Europe PMC source corpus — `MED` (PubMed), `PMC` (PubMed Central), `PPR` (preprint), `PAT` (patent), `AGR` (Agricola). Copy it from the search hit's `source`. `PMC` paired with a PMCID resolves whether or not the article is also indexed in PubMed, and a PubMed-indexed one comes back as its canonical `MED` record carrying that PMCID in `pmcId`."
              }
            },
            "description": "One record address: the Europe PMC source corpus plus its id within that corpus"
          },
          "maxItems": 25,
          "minItems": 1,
          "description": "Records to retrieve, each addressed by the `source` and `epmcId` of a `pubmed_europepmc_search` hit. The whole batch resolves in one Europe PMC request."
        },
        "maxResponseCharacters": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "Opt-in ceiling for the whole response, in characters. Each record is measured as the JSON record it is returned as — title, authors, journal, abstract, identifiers, every field it carries. Records are kept in the order Europe PMC returned them until the next one would cross the ceiling; that record and the rest are deferred whole (never partially populated) and listed in `deferred.records`. Response envelope fields — `notFound`, `deferred` itself — are not counted. Omit to return every resolved record."
        }
      },
      "additionalProperties": false
    }
    arguments 49 lines
  • pubmed_find_related reads unknown 11h ago

    Find articles related to a source article — similar content (similar), articles citing this one (cited_by), or articles this one cites (references). Uses NCBI ELink as the primary source; falls back to Europe PMC then OpenAlex when NCBI is unavailable.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "pmid"
      ],
      "properties": {
        "pmid": {
          "type": "string",
          "pattern": "^\\d+$",
          "description": "Source PubMed ID"
        },
        "offset": {
          "type": "integer",
          "default": 0,
          "maximum": 9007199254740991,
          "minimum": 0,
          "description": "Result offset for pagination (0-based); page through results by incrementing by maxResults"
        },
        "maxResults": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "Maximum related articles"
        },
        "relationship": {
          "enum": [
            "similar",
            "cited_by",
            "references"
          ],
          "type": "string",
          "default": "similar",
          "description": "Relationship type: similar (content-based), cited_by (articles citing this one), references (articles this one cites)"
        }
      },
      "additionalProperties": false
    }
    arguments 39 lines
  • pubmed_spell_check reads unknown 24h ago

    Spell-check a PubMed search query against NCBI ESpell and get the corrected query back. Use after a zero-hit or thin `pubmed_search_articles` result, or when a drug, gene, disease, or author name may be misspelled — every misspelled token is corrected in one call (`alzhiemer diseese treatmnt outcomse` → `alzheimer disease treatment outcomes`), and `hasSuggestion` is false when NCBI has no change to offer. Re-run the search with `corrected`.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "minLength": 2,
          "description": "PubMed search query to spell-check. Must carry a term: a value of only whitespace or invisible characters, such as a zero-width space, is rejected rather than sent to ESpell."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • pubmed_convert_ids reads unknown 21h ago

    Convert between article identifiers (DOI, PMID, PMCID). Accepts up to 50 IDs of a single type per request. Only resolves articles indexed in PubMed Central — for articles not in PMC, use pubmed_search_articles instead.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "ids",
        "idType"
      ],
      "properties": {
        "ids": {
          "type": "array",
          "items": {
            "type": "string",
            "minLength": 1
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "Article identifiers to convert — one identifier per element, all of the same type. Each element is checked against `idType` before the request: `doi` starts with \"10.\" and carries a \"/\" (\"10.1093/nar/gks1195\"); `pmid` is digits (\"23193287\"); `pmcid` is digits with an optional \"PMC\" prefix (\"PMC3531190\" or \"3531190\"). No element may contain a comma or whitespace — a packed value like \"23193287,37952131\" is rejected, so split it across elements."
        },
        "idType": {
          "enum": [
            "pmcid",
            "pmid",
            "doi"
          ],
          "type": "string",
          "description": "The type of IDs being submitted. Required so the API can unambiguously resolve them."
        }
      },
      "additionalProperties": false
    }
    arguments 30 lines
  • pubmed_europepmc_search reads unknown 13h ago

    Search Europe PMC, a broad open-access biomedical corpus. Surfaces preprints (`source: PPR`), patents (`source: PAT`), Agricola (`source: AGR`), plus everything in PubMed (`MED`) and PMC. Use when additional coverage is needed — preprints and EPMC-only OA records are the typical recovery. Paginate via `cursorMark`. Defaults to `MED`, `PMC`, and `PPR`; pass `sources` to include `PAT` / `AGR`. Abstracts arrive as a bounded `abstractSnippet` with `abstractTruncated` marking the cut ones — pass a hit’s `source` and `epmcId` to `pubmed_europepmc_fetch` for the complete abstract.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "sort": {
          "type": "string",
          "description": "Optional EPMC sort: `<field> asc|desc`, or several comma-separated keys applied in order (`PUB_YEAR desc, CITED desc`). Documented sortable fields: `P_PDATE_D` (publication date), `CITED` (citation count), `AUTH_FIRST` (first author surname), `PUB_YEAR` (publication year). Examples: `P_PDATE_D desc` (newest first), `CITED desc` (most cited). Omit for relevance ranking. Field and direction match case-insensitively. A field outside the documented set may be honored, silently ignored, or rejected, and a sort using one — or a key without `asc`/`desc` — can fail with `europepmc_invalid_input` naming it, even when Europe PMC honors the field. Note: `P_PDATE_D` is ignored for preprint-only (`sources: [\"PPR\"]`) result sets — preprints have no populated publication date, so use `PUB_YEAR` to order preprints by date."
        },
        "query": {
          "type": "string",
          "minLength": 1,
          "description": "Europe PMC search query. Supports field tokens like `AUTH:\"<name>\"`, `JOURNAL:\"<title>\"`, `TITLE:\"<words>\"`, `PUB_YEAR:[2020 TO 2024]`, `DOI:\"...\"`, `EXT_ID:<pmid> AND SRC:MED`, `PMCID:PMC<digits>`. Identifier tokens may be quoted or unquoted — this tool wraps every query with its `sources` filter, and Europe PMC honors a quoted identifier inside that wrapper. A PubMed-indexed article resolves under `SRC:MED`, not `SRC:PMC`, whichever identifier is used. Free text is matched broadly across abstract/title/keywords. A query with no search term — blank once HTML entities are decoded and markup, parentheses, and invisible characters are disregarded, such as `()` or `<b></b>` — is rejected; any other query is sent as written."
        },
        "sources": {
          "type": "array",
          "items": {
            "enum": [
              "MED",
              "PMC",
              "PPR",
              "PAT",
              "AGR"
            ],
            "type": "string"
          },
          "minItems": 1,
          "description": "Filter to specific EPMC sources. Defaults to MED, PMC, PPR when omitted. Pass an explicit array including PAT or AGR to broaden coverage. Allowed values: MED, PMC, PPR, PAT, AGR."
        },
        "pageSize": {
          "type": "integer",
          "default": 25,
          "maximum": 100,
          "minimum": 1,
          "description": "Results per page. Max 100 per EPMC API."
        },
        "cursorMark": {
          "type": "string",
          "default": "*",
          "description": "Pagination cursor. Use `*` (default) for the first page; pass the previous response's `nextCursorMark` verbatim for subsequent pages. A whitespace-only cursor, invisible characters included, is rejected before the request, and a cursor Europe PMC cannot read fails with `europepmc_invalid_input` once a retry of it fails again while the first page of the same query is served."
        },
        "resultType": {
          "enum": [
            "core",
            "lite"
          ],
          "type": "string",
          "default": "core",
          "description": "`core` returns abstract, IDs, dates, license; `lite` is a smaller payload with IDs and titles only."
        }
      },
      "additionalProperties": false
    }
    arguments 55 lines
  • pubmed_fetch_fulltext reads unknown 13h ago

    Fetch full-text articles from PubMed Central as structured sections — the body, then back matter such as acknowledgments, declarations, and appendices — with tables and references. When PMC misses, transparently falls back to Europe PMC `fullTextXML` (structured JATS for records with a PMC counterpart), then to Unpaywall — publisher-hosted or institutional open-access copies as HTML-as-Markdown or PDF-as-text. Name articles by `pmcids` (PMC IDs directly), `pmids` (PubMed IDs, auto-resolved), `dois` (DOIs, auto-resolved to PMC via the ID Converter; preprints and EPMC-only OA fall through to the Europe PMC and Unpaywall layers), or any mix of the three — up to 50 distinct identifiers; the first 10 are fetched per call, the rest returned in `overLimit`; an article several of them name is fetched and returned once. Two independent character controls: `maxCharacters` caps body text per article, `maxResponseCharacters` caps the whole response and defers articles past the ceiling whole, listing them in `deferred.ids` for a follow-up call.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "dois": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^10\\.[^\\s,]+\\/[^\\s,]+$"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "DOIs to resolve (e.g. [\"10.21203/rs.3.rs-9010375/v1\"]), one per element. Combinable with `pmcids` and `pmids` — up to 50 distinct identifiers across the three; the first 10 are fetched per call, the rest returned in `overLimit`. Resolved to a PMCID via the PMC ID Converter and returned as structured JATS when the article is in PMC; DOIs with no PMC counterpart (preprints, EPMC-only OA) fall through to Europe PMC, then Unpaywall, when those layers are enabled."
        },
        "pmids": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^\\d+$"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "PubMed IDs. Combinable with `pmcids` and `dois` — up to 50 distinct identifiers across the three; the first 10 are fetched per call, the rest returned in `overLimit`. Articles in PMC are returned as structured JATS; articles not in PMC fall through to Europe PMC (when EPMC has a `fullTextXML`), then to Unpaywall when `UNPAYWALL_EMAIL` is set and a DOI is available."
        },
        "pmcids": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^(?:PMC)?\\d+$"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "PMC IDs to fetch (e.g. [\"PMC9575052\"]). Combinable with `pmids` and `dois` — up to 50 distinct identifiers across the three; the first 10 are fetched per call, the rest returned in `overLimit`. PMC IDs with no retrievable full text fall through to Europe PMC, then to Unpaywall on the DOI the chain resolves for them."
        },
        "sections": {
          "type": "array",
          "items": {
            "type": "string"
          },
          "description": "Filter to specific sections by title (e.g. [\"Introduction\", \"Methods\", \"Results\", \"Discussion\"]). A term matches a section or subsection title at any nesting depth, case-insensitively, as a substring — \"resul\" matches \"Results\". Back-matter sections match the same way: by their own titles, or by their kind when they carry neither a title nor a label — \"appendix\" matches a section titled \"Appendix A\", \"footnotes\" an untitled footnote group. A label is never matched, so an appendix labelled \"Appendix A\" under a title of its own matches only on that title. A section whose own title matches is returned whole; one kept only because a nested subsection matched keeps its heading as a breadcrumb, with its own text cleared and only the matching branch beneath it. Tables and assets narrow with the filter: one whose section did not survive, or that names no section, is dropped. Empty strings are skipped, so `[\"\"]` applies no filter; an element of only whitespace or invisible characters, such as a zero-width space, is rejected. Applies to `source=pmc` results only."
        },
        "maxSections": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "Maximum top-level sections. Back-matter sections count and follow the body, so a cap drops them first. Applies to `source=pmc` results only."
        },
        "overflowMode": {
          "enum": [
            "truncate",
            "outline"
          ],
          "type": "string",
          "default": "truncate",
          "description": "How to spend `maxCharacters` across an article that exceeds it. truncate: fill sections in document order, so early sections stay whole, the section the budget runs out in is cut, and every section or subsection past that point is dropped (counted in `truncation.omittedSections`). outline: split the budget evenly so every section and subsection keeps its heading, and an excerpt as far as the budget reaches — a heading the budget left empty is marked as such in the rendered text. In both modes the body sections spend the budget first and back-matter sections share what the body, tables, and assets leave. Use it to survey what an article contains before requesting specific `sections`. Ignored when no budget is set, and identical for `source=unpaywall` bodies, which have no headings to preserve."
        },
        "includeAssets": {
          "type": "boolean",
          "default": true,
          "description": "Include the article's figures and supplementary material — `assets[]`, each with its label, caption, enclosing section and deposit pointer. On by default because it is cheaper than tables: a median asset-bearing article grows about 10%, and the body prose already refers to these by label. Set false to omit them, which also removes the `[Figure: …]` / `[Supplementary: …]` markers from the section text, since without the array they point at nothing. Prose-shaped blocks — lists, definition lists, block quotes, boxed text, preformatted blocks, displayed formulae — are section text rather than assets and this switch never affects them. Applies to `source=pmc` results only."
        },
        "includeTables": {
          "type": "boolean",
          "default": true,
          "description": "Include the article's tables — cells, captions, labels and footnotes. On by default because a dropped table takes its numbers with it. Table-dense articles pay for it: rendered tables typically add 12–17% to an article record and can more than double it. Set false to omit them, or cap the cost with `maxCharacters`, which drops tables it cannot fit whole. Applies to `source=pmc` results only."
        },
        "maxCharacters": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "Per-article budget for body text, in characters. Counts `source=pmc` section and subsection text — which carries the inline blocks the parser renders in place, such as lists, definition lists, block quotes, boxed text, preformatted blocks and displayed formulae — plus table label, caption, cell and footnote text and asset label, caption and `href` text; or the `source=unpaywall` `content` body. Titles, abstracts, identifiers, and references are never counted or shortened. Shortened text ends at the last word boundary inside its allowance, so it can come back a few characters under it. The counted unit is that text alone — the Markdown grid `content[]` renders around the cells (pipes, padding, the divider row, headings) is scaffolding this budget does not measure, so a table renders longer than it costs here. Body sections are served first, then tables, then assets, then back-matter sections, each spending what is left, in document order. For tables and assets, admission stops at the first entry that does not fit, and every entry from there on is dropped whole rather than cut mid-row or returned with a shortened caption, counted in `truncation.omittedTables` / `truncation.omittedAssets` and named in `truncation.articles[].omittedTableNames` / `omittedAssetNames`. Back matter takes only what remains and is shortened or dropped as body sections are; `sections` still returns it after the body. Applied after `sections`, `maxSections`, `includeReferences`, `includeTables`, and `includeAssets`, so semantic filtering is unaffected. This knob alone bounds only bodies: the response-wide ceiling it implies is this value times the number of articles returned, plus every uncounted field. Use `maxResponseCharacters` for a true whole-response ceiling. Omit for the full body."
        },
        "includeReferences": {
          "type": "boolean",
          "default": false,
          "description": "Include reference list. Applies to `source=pmc` results only."
        },
        "maxResponseCharacters": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "Opt-in ceiling for the whole response, in characters — the true response-wide counterpart to the per-article `maxCharacters`. Each article is measured as the JSON record it is returned as, after every filter and the per-article body budget: title, abstract, sections, references, identifiers, license and source metadata — every field it carries. One ledger covers all tiers, so PMC-, Europe PMC-, and Unpaywall-served articles spend the same budget. Articles are kept in response order until the next one would cross the ceiling; that article and the rest are deferred whole (never partially populated) and listed in `deferred.ids`. Response envelope fields — counts, `unavailable`, `truncation`, `deferred` itself — are not counted. Omit to return every resolved article."
        },
        "maxCharactersPerSection": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "Budget for a single top-level section, in characters, counting the section text plus its subsections. Combine with `maxCharacters` to cap both one section and the article; the tighter of the two wins. Applies to `source=pmc` results only."
        }
      },
      "additionalProperties": false
    }
    arguments 92 lines
  • pubmed_fetch_articles reads unknown 13h ago

    Fetch full article metadata by PubMed IDs. Returns detailed article information including abstract, authors, journal, MeSH terms, and linked retraction, erratum, and comment notices; grants and the members of a collective author are opt-in (`includeGrants`, `includeInvestigators`). Set `maxResponseCharacters` to bound the whole response: articles past the ceiling are deferred whole and listed in `deferred.ids` for a follow-up call.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "pmids"
      ],
      "properties": {
        "pmids": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^\\d+$"
          },
          "maxItems": 200,
          "minItems": 1,
          "description": "PubMed IDs to fetch"
        },
        "includeMesh": {
          "type": "boolean",
          "default": true,
          "description": "Include MeSH terms"
        },
        "includeGrants": {
          "type": "boolean",
          "default": false,
          "description": "Include grant information"
        },
        "includeInvestigators": {
          "type": "boolean",
          "default": false,
          "description": "Include `investigators`: the members NCBI lists for a collective author such as \"TGU Investigators\". Off by default because the list is unbounded: consortium trials name thousands, at about 60 characters of JSON each — PMID 33933206 lists 6,349, adding about 372,000 characters to its record. Under `maxResponseCharacters` they count toward the size of their article, which is deferred whole when it no longer fits."
        },
        "maxResponseCharacters": {
          "type": "integer",
          "maximum": 9007199254740991,
          "minimum": 1,
          "description": "Opt-in ceiling for the whole response, in characters. Each article is measured as the JSON record it is returned as — title, abstract, authors, journal, MeSH terms, grants, identifiers, every field it carries. Articles are kept in response order until the next one would cross the ceiling; that article and the rest are deferred whole (never partially populated) and listed in `deferred.ids`. Response envelope fields — counts, `unavailablePmids`, `deferred` itself — are not counted. Omit to return every resolved article."
        }
      },
      "additionalProperties": false
    }
    arguments 41 lines
  • pubmed_format_citations reads unknown 11h ago

    Get formatted citations for PubMed articles in one or more formats (apa, mla, bibtex, ris, vancouver). Pass a single format as a string or multiple as an array. Retractions, errata, and expressions of concern NCBI links to an article come back in `notices`; Vancouver and APA also cite a retraction in the reference itself.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "pmids"
      ],
      "properties": {
        "pmids": {
          "type": "array",
          "items": {
            "type": "string",
            "pattern": "^\\d+$"
          },
          "maxItems": 50,
          "minItems": 1,
          "description": "PubMed IDs to cite"
        },
        "format": {
          "anyOf": [
            {
              "enum": [
                "apa",
                "mla",
                "bibtex",
                "ris",
                "vancouver"
              ],
              "type": "string",
              "description": "Single citation style. One of: apa, mla, bibtex, ris, vancouver."
            },
            {
              "type": "array",
              "items": {
                "enum": [
                  "apa",
                  "mla",
                  "bibtex",
                  "ris",
                  "vancouver"
                ],
                "type": "string"
              },
              "minItems": 1,
              "description": "Multiple citation styles to generate. Each entry: apa, mla, bibtex, ris, or vancouver."
            }
          ],
          "default": "apa",
          "description": "Citation format(s) to generate — single style as a string or multiple as an array. Allowed values: apa, mla, bibtex, ris, vancouver."
        }
      },
      "additionalProperties": false
    }
    arguments 52 lines
  • pubmed_lookup_citation reads unknown 11h ago

    Look up PubMed IDs from partial bibliographic citations. Useful when you have a reference (journal, year, volume, page, author) and need the PMID — deterministic citation matching, more reliable than free-text search for structured references. Each citation must include at least journal or a four-digit year (ECitMatch primary-keys on journal+volume+page; author-only or volume-only inputs guarantee no match); more fields = better match accuracy.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "citations"
      ],
      "properties": {
        "citations": {
          "type": "array",
          "items": {
            "type": "object",
            "properties": {
              "key": {
                "type": "string",
                "description": "Arbitrary label to track this citation in results. Auto-assigned if omitted. Echoed back unchanged and never sent to NCBI, so any character is accepted here."
              },
              "year": {
                "type": "string",
                "pattern": "^[ \\t]*\\d{4}[ \\t]*$",
                "description": "Publication year as four digits (e.g., \"1991\")."
              },
              "volume": {
                "type": "string",
                "pattern": "^[^|\\r\\n]*$",
                "description": "Volume number. Must contain a visible character, and cannot contain a pipe (\"|\") or a line break."
              },
              "journal": {
                "type": "string",
                "pattern": "^[^|\\r\\n]*$",
                "description": "Journal title or ISO abbreviation (e.g., \"proc natl acad sci u s a\"). Must contain a visible character, and cannot contain a pipe (\"|\") or a line break."
              },
              "firstPage": {
                "type": "string",
                "pattern": "^[^|\\r\\n]*$",
                "description": "First page number. Must contain a visible character, and cannot contain a pipe (\"|\") or a line break."
              },
              "authorName": {
                "type": "string",
                "pattern": "^[^|\\r\\n]*$",
                "description": "Author name, typically \"lastname initials\" (e.g., \"mann bj\"). Must contain a visible character, and cannot contain a pipe (\"|\") or a line break."
              }
            },
            "description": "Citation to match against PubMed. Must include at least journal or a four-digit year — ECitMatch primary-keys on journal+volume+page, so author-only or volume-only inputs guarantee no match."
          },
          "maxItems": 25,
          "minItems": 1,
          "description": "Citations to look up, 1–25, each matched independently. More fields = better match accuracy."
        }
      },
      "additionalProperties": false
    }
    arguments 51 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 33f28d7c947973db.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/33f28d7c947973db/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/33f28d7c947973db/badge.svg)](https://brick.blue/agent/33f28d7c947973db?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.

_ also on caseyjhand.com 109 entries

Served from the same domain, which is what was measured. Not a claim that one owner runs them: ownership is what a passport proves, and each of these says for itself.

101 more sit on this domain. All of them.