---
title: "Amass MCP — Cited evidence inside your assistant"
description: "Connect Claude, ChatGPT, Claude Code or Codex to six Amass *Cores. Your assistant's search tools return records with PMIDs, NCT IDs and patent numbers."
url: https://amass.tech/mcp
---

# Amass MCP — Cited evidence inside your assistant

Model Context Protocol

# Cited biomedical evidence, inside

Your assistant calls Amass search tools across six \*Cores and gets back papers, trials, drugs, genes, patents and regulatory records, each with its identifier. Works in Claude, ChatGPT, Codex, Claude Code and any MCP client.

Get started with:

[or any other MCP tool](#any-client)

[or watch the CTO’s demo (1:37) →](#demo)

APIBuilding with the API instead? [The Amass API: six \*Cores, cross-linked and cited.](https://amass.tech/life-science-api)

Works with

Claude

Claude Code

ChatGPT

Codex

Cursor

Microsoft Copilot

[…and any other MCP-compatible tool](#any-client)

Why MCP for evidence

## What the tool calls give your assistant.

### Filters built for evidence.

The tools take filters for date, journal quality, retraction status and identifiers, so the assistant narrows the set before it reads.

### Searches that chain.

The assistant runs a broad scan, filters it and opens specific records, without you driving each step.

### Citations back to sources.

Every result carries the identifier and link of its record, so you can check a claim against its source.

Install

## Connect Amass to your assistant.

Pick your tool, add the connector and sign in once with your Amass account. Nothing else to configure: the assistant gets the access your plan gives you.

Amass is listed in Claude's connector directory as **Amass Connector**. Find it in the app and connect in one click. Available on Claude Pro, Max, Team, and Enterprise.

[Open Amass Connector in Claude](https://claude.ai/directory/amass)

Press **Connect** on the listing and sign in once with your existing Amass account. That's the whole install. Your plan's access applies.

See the step-by-step walkthrough (with screenshots)

1.  Find Amass in Claude's connector directory.

    Use the button above — or in Claude, open **Settings → Connectors → Browse connectors** and search for **Amass**.

2.  Open the listing, press Connect, and sign in with your Amass account.

    No URLs to paste, nothing to configure — the listing carries the setup. One-time sign-in, and your Amass plan's access applies.


You'll be redirected to sign in with your Amass account. Your existing plan's access applies through the MCP.

The skill

## Teach your assistant to use Amass well.

Biomedical Evidence Scout is a small instruction pack: when to filter by journal quality, how to structure a landscape scan, when to open a specific record. It works in any assistant that reads the open SKILL.md format: Claude, Codex, GitHub Copilot, Gemini CLI.

[Download .skill (Claude)](https://raw.githubusercontent.com/amass-technologies/public-skills/main/dist/amass-biomedical-evidence-scout.skill)[Download .zip (everything else)](https://raw.githubusercontent.com/amass-technologies/public-skills/main/dist/amass-biomedical-evidence-scout.zip)

See [the Biomedical Evidence Scout in the Skills & Prompts library](https://amass.tech/skills/amass-biomedical-evidence-scout), with a KRAS G12C landscape briefing built from Amass data.

How do I install the skill?

Install every Amass skill in one step with `npx skills add amass-technologies/public-skills`. Or grab a file from the [amass-technologies/public-skills](https://github.com/amass-technologies/public-skills) repo: double-click the `.skill` on Mac to install it into Claude, or unzip the `.zip`into the tool's skills directory:

-   Claude Code: `~/.claude/skills/`
-   Codex: `~/.codex/skills/`
-   Gemini CLI: `~/.gemini/skills/`

Try it

## Prompts to try once it's connected.

The first tab is direct retrieval through the MCP. The second is multi-step work, where the skill guides the assistant.

Clinical / translational

### Lp(a)HORIZON deep dive

Can you pull up Lp(a)HORIZON and tell me the key trial details, whether results are available, and any papers linked to it?

Returns: NCT ID, phase, sponsor, status, enrollment, countries, endpoints, posted results, and linked publications.

Target / mechanism

### Recent TREM2 mechanisms

What are the most important recent TREM2 mechanism papers, and what do they suggest about TREM2 as an Alzheimer's target?

Returns: Ranked papers with journal, year, citations, PMID/DOI, model system, and core mechanistic claims.

Competitive / BD

### RayzeBio active trials

Which RayzeBio radiopharmaceutical trials are currently active, and what are the main assets, indications, and timelines?

Returns: Active or recruiting trials, assets such as RYZ101/RYZ801/RYZ811/RYZ401, indications, phase, NCT IDs, enrollment, and completion dates.

See it in action

## One query in Claude, with citations.

Alex, Amass’s CTO, walks through a query in Claude.

ClaudeChatGPTClaude CodeCodexAmass connected

Which Lp(a)-lowering programs are in phase 3?

amass`search_amass_trialcore_records`Completed

`query: "lipoprotein(a) cardiovascular outcomes"``phase: "PHASE3"`

[NCT04023552](https://clinicaltrials.gov/study/NCT04023552)Lp(a)HORIZON · COMPLETED · Novartis Pharmaceuticals

[NCT05581303](https://clinicaltrials.gov/study/NCT05581303)OCEAN(a)-Outcomes · ACTIVE\_NOT\_RECRUITING · Amgen

Two phase 3 programs: Lp(a)HORIZON (NCT04023552) has completed, and OCEAN(a)-Outcomes (NCT05581303) is active and no longer recruiting.

Reply…

The demo’s opening frame: the tool call, and the two trial records it returns.

Microsoft Copilot

## Amass as a data source in Microsoft Copilot.

Add Amass from the + menu in Copilot and ask your question there. The same MCP and the same sign-in run underneath, so the answers come from the same \*Cores and link to their sources. If Amass does not show up in your organization yet, we will help you set it up.

[Amass for Microsoft Copilot](https://amass.tech/integrations/microsoft-copilot)

Microsoft and Microsoft Copilot are trademarks of the Microsoft group of companies.

Changelog

## Changes to the tools you call.

Each release lists the tools, fields and filters it changed, newest first.

1.  v11

    ### Date ranges, journal filters and trial endpoints

    October 2026

    BioMedCore, PatentCore and TrialCore searches can now be bounded on both ends of a date range, BioMedCore filters by journal and publication type, TrialCore records carry endpoints, arms and posted results, and DrugCore gains freshness filters.

    -   `search_amass_biomedcore_records` accepts `publicationTypes`, to keep only papers of the given NLM publication types such as `Clinical Trial` (which includes randomized and phase I–IV trials) or `Conference` for conference abstracts.
    -   `search_amass_biomedcore_records` accepts `journalIssns`, to keep only papers from the journals with those linking ISSNs (the value records return in `issn`).
    -   `search_amass_biomedcore_records` and `get_amass_biomedcore_record` return the journal's `issn` and the record's `publicationTypes` in the default response.
    -   `search_amass_biomedcore_records` and `search_amass_patentcore_records` accept `maxPublicationDate`, so a search can be limited to records published on or before a given date.
    -   `search_amass_trialcore_records` accepts `maxStartDate`, `minCompletionDate` and `maxCompletionDate`, so a search can be limited to trials starting or completing within a date range.
    -   `get_amass_trialcore_record` accepts `includeOutcomes` to return a ClinicalTrials.gov trial's posted results.
    -   `get_amass_trialcore_record` now returns `whyStopped`, `resultsFirstPostDate`, `enrollmentType`, `sponsorType`, `collaborators`, `armGroups`, `primaryOutcomeMeasures` and `secondaryOutcomeMeasures` by default, and its description now lists what the record contains.
    -   `search_amass_trialcore_records` now returns `whyStopped` and `enrollmentType` on each result, and its description now lists what a result contains and points to `get_amass_trialcore_record` for endpoints, arms and posted results.
    -   `search_amass_drugcore_records` accepts `minLastUpdateDate` and `minCreateDate`, to find drugs that changed or were added since a given date.
2.  v10

    ### GeneCore freshness filters and record dates

    September 2026

    GeneCore search now takes the same freshness filters as BioMedCore, TrialCore and RegulatoryCore, and a fetched gene says when Amass last wrote it.

    -   `get_amass_genecore_record` now also returns `lastUpdateDate` and `createDate` on each gene: when Amass last wrote the record, and when it first entered Amass. Search results do not carry them.
    -   `search_amass_genecore_records` accepts `minLastUpdateDate` and `minCreateDate`, filtering on when Amass last wrote a gene or first ingested it, for "which genes changed since I last looked" and "what genes are new in Amass" questions. Any ingested change counts toward `minLastUpdateDate`: an HGNC edit, or a new target-intelligence, protein, RefSeq summary or drug-link value. Genes are refreshed weekly, and records without the date are excluded.
3.  v9

    ### Source links on records

    September 2026

    Search and get results on every Core now include a `url` that links to the source of each record.

    -   `search_amass_biomedcore_records` and `get_amass_biomedcore_record` return `url` next to `pmid` and `doi`, so an assistant can cite a publication with a working link instead of assembling one. It is null when a record has no PMID, DOI or PMCID.
    -   The link target may change over time. `pmid` and `doi` are unchanged and remain the fields to build links to a specific external system from.
    -   `search_amass_trialcore_records` and `get_amass_trialcore_record` return `url` next to `sourceUrl`. Today they carry the same registry link, except that a non-US trial with no registry link gets its WHO ICTRP record. `sourceUrl` keeps pointing to the registry even if `url` later moves.
    -   `search_amass_drugcore_records` and `get_amass_drugcore_record` return `url` next to `chemblId`.
    -   `search_amass_genecore_records` and `get_amass_genecore_record` return `url` next to `ensemblGeneId`.
    -   `search_amass_regulatorycore_records` and `get_amass_regulatorycore_record` return `url` next to `sourceUrl`, with the same agency landing page today. `sourceUrl` keeps pointing to the agency even if `url` later moves.
    -   `search_amass_patentcore_records` and `get_amass_patentcore_record` return `url` next to `publicationNumber`.

Show all 11 releases

1.  v11

    ### Date ranges, journal filters and trial endpoints

    October 2026

    BioMedCore, PatentCore and TrialCore searches can now be bounded on both ends of a date range, BioMedCore filters by journal and publication type, TrialCore records carry endpoints, arms and posted results, and DrugCore gains freshness filters.

    -   `search_amass_biomedcore_records` accepts `publicationTypes`, to keep only papers of the given NLM publication types such as `Clinical Trial` (which includes randomized and phase I–IV trials) or `Conference` for conference abstracts.
    -   `search_amass_biomedcore_records` accepts `journalIssns`, to keep only papers from the journals with those linking ISSNs (the value records return in `issn`).
    -   `search_amass_biomedcore_records` and `get_amass_biomedcore_record` return the journal's `issn` and the record's `publicationTypes` in the default response.
    -   `search_amass_biomedcore_records` and `search_amass_patentcore_records` accept `maxPublicationDate`, so a search can be limited to records published on or before a given date.
    -   `search_amass_trialcore_records` accepts `maxStartDate`, `minCompletionDate` and `maxCompletionDate`, so a search can be limited to trials starting or completing within a date range.
    -   `get_amass_trialcore_record` accepts `includeOutcomes` to return a ClinicalTrials.gov trial's posted results.
    -   `get_amass_trialcore_record` now returns `whyStopped`, `resultsFirstPostDate`, `enrollmentType`, `sponsorType`, `collaborators`, `armGroups`, `primaryOutcomeMeasures` and `secondaryOutcomeMeasures` by default, and its description now lists what the record contains.
    -   `search_amass_trialcore_records` now returns `whyStopped` and `enrollmentType` on each result, and its description now lists what a result contains and points to `get_amass_trialcore_record` for endpoints, arms and posted results.
    -   `search_amass_drugcore_records` accepts `minLastUpdateDate` and `minCreateDate`, to find drugs that changed or were added since a given date.
2.  v10

    ### GeneCore freshness filters and record dates

    September 2026

    GeneCore search now takes the same freshness filters as BioMedCore, TrialCore and RegulatoryCore, and a fetched gene says when Amass last wrote it.

    -   `get_amass_genecore_record` now also returns `lastUpdateDate` and `createDate` on each gene: when Amass last wrote the record, and when it first entered Amass. Search results do not carry them.
    -   `search_amass_genecore_records` accepts `minLastUpdateDate` and `minCreateDate`, filtering on when Amass last wrote a gene or first ingested it, for "which genes changed since I last looked" and "what genes are new in Amass" questions. Any ingested change counts toward `minLastUpdateDate`: an HGNC edit, or a new target-intelligence, protein, RefSeq summary or drug-link value. Genes are refreshed weekly, and records without the date are excluded.
3.  v9

    ### Source links on records

    September 2026

    Search and get results on every Core now include a `url` that links to the source of each record.

    -   `search_amass_biomedcore_records` and `get_amass_biomedcore_record` return `url` next to `pmid` and `doi`, so an assistant can cite a publication with a working link instead of assembling one. It is null when a record has no PMID, DOI or PMCID.
    -   The link target may change over time. `pmid` and `doi` are unchanged and remain the fields to build links to a specific external system from.
    -   `search_amass_trialcore_records` and `get_amass_trialcore_record` return `url` next to `sourceUrl`. Today they carry the same registry link, except that a non-US trial with no registry link gets its WHO ICTRP record. `sourceUrl` keeps pointing to the registry even if `url` later moves.
    -   `search_amass_drugcore_records` and `get_amass_drugcore_record` return `url` next to `chemblId`.
    -   `search_amass_genecore_records` and `get_amass_genecore_record` return `url` next to `ensemblGeneId`.
    -   `search_amass_regulatorycore_records` and `get_amass_regulatorycore_record` return `url` next to `sourceUrl`, with the same agency landing page today. `sourceUrl` keeps pointing to the agency even if `url` later moves.
    -   `search_amass_patentcore_records` and `get_amass_patentcore_record` return `url` next to `publicationNumber`.
4.  v8

    ### Conference abstracts in BioMedCore

    September 2026

    BioMedCore search and get now say that the Core holds conference abstracts as well as journal articles, and how to tell the two apart.

    -   The BioMedCore tool descriptions and the server instructions name conference abstracts from society meetings as part of the Core, and state that such a record carries `Conference` in `publicationTypes` alongside NLM's own values. The data was already searchable; only the descriptions changed, so results and parameters are unaffected.
    -   `search_amass_biomedcore_records` adds congress readouts that precede the full paper to what it is for, so an assistant reaches for BioMedCore on those questions instead of falling back to web search.
    -   The headline count in both descriptions moves from 40M+ to 43M+, which is the corpus with conference abstracts included.
5.  v7

    ### MCP protocol revision 2026-07-28

    September 2026

    The server now speaks the 2026-07-28 MCP protocol revision alongside every earlier one, so assistants built on the newest MCP SDKs connect without an `initialize` handshake or a session.

    -   Clients on the 2026-07-28 revision are served per request: no session id, and the client identifies itself on every call.
    -   Clients on earlier revisions (2024-10-07 through 2025-11-25) keep working unchanged; the tools and their parameters are identical on both.
6.  v6

    ### Freshness filters, result limits, and data feedback

    September 2026

    The search tools gained control over how many results come back and how recently Amass touched them. You can now optionally report data issues straight from the assistant to the Amass team.

    -   Every search tool takes a `limit` (1–50) for how many results to return. The default stays at 10, so existing calls behave exactly as before.
    -   BioMedCore, TrialCore, and RegulatoryCore search accept `minLastUpdateDate` and `minCreateDate`, filtering on when Amass last wrote a record or first ingested it — for "what changed since I last looked" and "what is new in Amass" questions, independent of publication, trial start, or authorization dates.
    -   New send\_feedback MCP tool: report a wrong, missing, or outdated value in a record, a search that missed records that clearly exist, or a gap in the data model. It files the report with the Amass data team and is scoped to the six Cores — you name the Core(s) the issue concerns and, where it applies, the record id, the query you ran, and the ids you expected. It is not for web search or third-party results or context. Sending feedback is optional, and the tool returns only a receipt id rather than echoing the report back.
7.  v5

    ### International trials and PatentCore

    July 2026

    TrialCore now spans non-US trials from the WHO ICTRP, and PatentCore adds patents as a new linked core.

    -   TrialCore search and lookup now cover 1.2M+ trials — ClinicalTrials.gov plus non-US national registries via the WHO ICTRP (EUCTR, ChiCTR, JPRN, ISRCTN, and more).
    -   Every trial record carries its source: a native registry ID (populated even for non-US trials, which have no NCT Id), the source registry, and a link to the trial on that registry.
    -   The get\_amass\_trialcore\_record tool now accepts a registry ID (not just an Amass Id or NCT Id), so you can fetch non-US trials by their native registry id.
    -   PatentCore search and lookup (preview) — patent publications with bibliographic metadata, full text (title, abstract, claims, description), CPC/IPC classifications, inventors/assignees, key dates, and citation lineage. Search the full text with filters for jurisdiction, classification, assignee/inventor, dates, and citation count.
    -   PatentCore search collapses each patent family to one result, so an invention filed across many jurisdictions takes a single slot — the collapsed siblings' Amass IDs ride along on the kept record.
    -   Patent records cross-link to DrugCore (the drugs disclosed in or linked to a patent) and BioMedCore (via references), and you can look a patent up directly by its publication number or Amass Id.
8.  v4

    ### GeneCore, target intelligence, and drug targets

    June 2026

    GeneCore brings human genes into the linked cores with a full target-intelligence layer and DrugCore now carries the gene targets each drug acts on.

    -   GeneCore search and lookup — harmonized gene records with approved symbols, names, synonyms, gene families, gene type (biotype), RefSeq functional summary, genomic location, external identifiers, and UniProt protein annotations.
    -   Search filters for gene type/biotype, druggability, CRISPR essentiality, ChEMBL target class, clinical-precedent tractability (by modality and stage), curated safety liabilities, and gnomAD LOEUF constraint.
    -   DrugCore records now return each drug's mechanisms of action — how it acts on each pharmacological target, its mode of action, and the target genes it hits.
    -   Records link both ways: gene records point to the drugs (DrugCore) that target them, and drug records now carry their gene targets.
9.  v3

    ### RegulatoryCore and DrugCore

    June 2026

    Coverage extends past papers and trials into the regulatory record and the drugs themselves — each core cross-linked to the rest.

    -   RegulatoryCore search and lookup — FDA and EMA on one schema, from NDA/BLA approvals to EMA marketing authorizations. Filter by agency, molecule type, authorization status, authorization date, and orphan designation; cross-agency by default.
    -   DrugCore search and lookup — harmonized drugs and molecules with trade names, synonyms, modality, clinical stage, and chemical structure. Filter by modality and clinical stage.
    -   A new tool pulls the full text of a single regulatory document section — FDA labels and reviews, EMA SmPCs and EPARs.
    -   Records now link across all four cores: a drug connects to its trials, its literature, and its regulatory authorizations.
10.  v2

     ### Better search, richer records

     May 2026

     The two launch cores grew filters, optional full text, and the cross-links that tie papers and trials together.

     -   BioMedCore search gained filters for publication date, journal quality (JuFo tier), retraction status, and author or institution — by name, ORCID, or ROR.
     -   TrialCore search gained filters for phase, recruitment status, study type, intervention type, start date, and whether results have posted.
     -   Fetching a publication can now return its full text on request, not just the abstract.
     -   Records carry their cross-references — publication-to-trial links, plus what each record cites and what cites it.
11.  v1

     ### Launch — BioMedCore and TrialCore

     April 2026

     The first release: two cores, each with a search tool and a direct-lookup tool.

     -   BioMedCore — search and fetch across 39M+ PubMed and PMC publications, abstracts included.
     -   TrialCore — search and fetch across 575K+ ClinicalTrials.gov trials, with protocols, sponsors, and endpoints.
     -   Look any record up directly by identifier — PMID or DOI for papers, NCT Id for trials.

1.  v8

    ### Conference abstracts in BioMedCore

    September 2026

    BioMedCore search and get now say that the Core holds conference abstracts as well as journal articles, and how to tell the two apart.

    -   The BioMedCore tool descriptions and the server instructions name conference abstracts from society meetings as part of the Core, and state that such a record carries `Conference` in `publicationTypes` alongside NLM's own values. The data was already searchable; only the descriptions changed, so results and parameters are unaffected.
    -   `search_amass_biomedcore_records` adds congress readouts that precede the full paper to what it is for, so an assistant reaches for BioMedCore on those questions instead of falling back to web search.
    -   The headline count in both descriptions moves from 40M+ to 43M+, which is the corpus with conference abstracts included.
2.  v7

    ### MCP protocol revision 2026-07-28

    September 2026

    The server now speaks the 2026-07-28 MCP protocol revision alongside every earlier one, so assistants built on the newest MCP SDKs connect without an `initialize` handshake or a session.

    -   Clients on the 2026-07-28 revision are served per request: no session id, and the client identifies itself on every call.
    -   Clients on earlier revisions (2024-10-07 through 2025-11-25) keep working unchanged; the tools and their parameters are identical on both.
3.  v6

    ### Freshness filters, result limits, and data feedback

    September 2026

    The search tools gained control over how many results come back and how recently Amass touched them. You can now optionally report data issues straight from the assistant to the Amass team.

    -   Every search tool takes a `limit` (1–50) for how many results to return. The default stays at 10, so existing calls behave exactly as before.
    -   BioMedCore, TrialCore, and RegulatoryCore search accept `minLastUpdateDate` and `minCreateDate`, filtering on when Amass last wrote a record or first ingested it — for "what changed since I last looked" and "what is new in Amass" questions, independent of publication, trial start, or authorization dates.
    -   New send\_feedback MCP tool: report a wrong, missing, or outdated value in a record, a search that missed records that clearly exist, or a gap in the data model. It files the report with the Amass data team and is scoped to the six Cores — you name the Core(s) the issue concerns and, where it applies, the record id, the query you ran, and the ids you expected. It is not for web search or third-party results or context. Sending feedback is optional, and the tool returns only a receipt id rather than echoing the report back.
4.  v5

    ### International trials and PatentCore

    July 2026

    TrialCore now spans non-US trials from the WHO ICTRP, and PatentCore adds patents as a new linked core.

    -   TrialCore search and lookup now cover 1.2M+ trials — ClinicalTrials.gov plus non-US national registries via the WHO ICTRP (EUCTR, ChiCTR, JPRN, ISRCTN, and more).
    -   Every trial record carries its source: a native registry ID (populated even for non-US trials, which have no NCT Id), the source registry, and a link to the trial on that registry.
    -   The get\_amass\_trialcore\_record tool now accepts a registry ID (not just an Amass Id or NCT Id), so you can fetch non-US trials by their native registry id.
    -   PatentCore search and lookup (preview) — patent publications with bibliographic metadata, full text (title, abstract, claims, description), CPC/IPC classifications, inventors/assignees, key dates, and citation lineage. Search the full text with filters for jurisdiction, classification, assignee/inventor, dates, and citation count.
    -   PatentCore search collapses each patent family to one result, so an invention filed across many jurisdictions takes a single slot — the collapsed siblings' Amass IDs ride along on the kept record.
    -   Patent records cross-link to DrugCore (the drugs disclosed in or linked to a patent) and BioMedCore (via references), and you can look a patent up directly by its publication number or Amass Id.
5.  v4

    ### GeneCore, target intelligence, and drug targets

    June 2026

    GeneCore brings human genes into the linked cores with a full target-intelligence layer and DrugCore now carries the gene targets each drug acts on.

    -   GeneCore search and lookup — harmonized gene records with approved symbols, names, synonyms, gene families, gene type (biotype), RefSeq functional summary, genomic location, external identifiers, and UniProt protein annotations.
    -   Search filters for gene type/biotype, druggability, CRISPR essentiality, ChEMBL target class, clinical-precedent tractability (by modality and stage), curated safety liabilities, and gnomAD LOEUF constraint.
    -   DrugCore records now return each drug's mechanisms of action — how it acts on each pharmacological target, its mode of action, and the target genes it hits.
    -   Records link both ways: gene records point to the drugs (DrugCore) that target them, and drug records now carry their gene targets.
6.  v3

    ### RegulatoryCore and DrugCore

    June 2026

    Coverage extends past papers and trials into the regulatory record and the drugs themselves — each core cross-linked to the rest.

    -   RegulatoryCore search and lookup — FDA and EMA on one schema, from NDA/BLA approvals to EMA marketing authorizations. Filter by agency, molecule type, authorization status, authorization date, and orphan designation; cross-agency by default.
    -   DrugCore search and lookup — harmonized drugs and molecules with trade names, synonyms, modality, clinical stage, and chemical structure. Filter by modality and clinical stage.
    -   A new tool pulls the full text of a single regulatory document section — FDA labels and reviews, EMA SmPCs and EPARs.
    -   Records now link across all four cores: a drug connects to its trials, its literature, and its regulatory authorizations.
7.  v2

    ### Better search, richer records

    May 2026

    The two launch cores grew filters, optional full text, and the cross-links that tie papers and trials together.

    -   BioMedCore search gained filters for publication date, journal quality (JuFo tier), retraction status, and author or institution — by name, ORCID, or ROR.
    -   TrialCore search gained filters for phase, recruitment status, study type, intervention type, start date, and whether results have posted.
    -   Fetching a publication can now return its full text on request, not just the abstract.
    -   Records carry their cross-references — publication-to-trial links, plus what each record cites and what cites it.
8.  v1

    ### Launch — BioMedCore and TrialCore

    April 2026

    The first release: two cores, each with a search tool and a direct-lookup tool.

    -   BioMedCore — search and fetch across 39M+ PubMed and PMC publications, abstracts included.
    -   TrialCore — search and fetch across 575K+ ClinicalTrials.gov trials, with protocols, sponsors, and endpoints.
    -   Look any record up directly by identifier — PMID or DOI for papers, NCT Id for trials.

FAQ

## Questions about the connector.

Which assistants is the Amass MCP available in?

Claude (Pro/Max/Team/Enterprise, listed in the connector directory), ChatGPT (Plus/Business/Enterprise/Edu, listed in the plugin directory), Claude Code and Codex CLI. In Microsoft Copilot, Amass is a data source you add from the + menu. Perplexity, Gemini CLI, Cursor, VS Code and other MCP clients connect with the generic connection details under Install, "Other clients".

Is the connector approved by Anthropic, OpenAI, or others?

Amass is listed in Claude's connector directory and in ChatGPT's plugin directory (the former app store), with one-click installs in both. Other MCP clients add it as a custom connector, which works the same way.

Do I need an API key?

No. You sign in once with your Amass account when you connect, and the MCP uses your plan's access.

Does this work on ChatGPT Plus?

Yes. The Amass MCP works on ChatGPT Plus, Business, Enterprise and Edu, with a one-click install from ChatGPT's plugin directory (the former app store). If your tenant blocks third-party apps, use the developer-mode fallback.

What data does Amass have access to?

Only the queries the assistant sends and the responses we return. The assistant itself runs on your provider's infrastructure.

My company uses Microsoft 365. What are my options?

Add Amass from the + menu in Microsoft Copilot under Change data sources, then sign in with your Amass account. If Amass does not show up there yet, or an administrator has to approve new sources, we will help with the setup.

## Cited biomedical evidence, inside Claude.

Included on every plan, Free too, with one sign-in to your Amass account.

Get started with:

[or any other MCP tool](#any-client)

Data

No training on your data

Hosting

EU-hosted, enterprise

Isolation

Tenant-isolated by architecture

Certification

ISO 27001, SOC 2, NIS2: in motion