DrugCore and RegulatoryCore are now live in the API and MCP. Read more

Amass
MCP showcasesSubmission evidence assembler

MCP Showcase

Submission evidence assembler

Name one drug asset; get a citation-auditable, Module-2.5-style evidence narrative — every pivotal Phase-3 trial, its describing papers, and a canonical Amass-ID audit trail — assembled from Amass's publication↔trial graph with trust metadata on every cited paper.

New to Amass? Connect Amass to Claude first

6Phase-3 trials
37linked papers
0retracted
You getxlsxdocx2 files
Skillregulatoryclaude

The prompt

Paste this into Claude

Asset (drug)mavacamten
prompt
Use the submission-evidence-assembler skill.

Asset (drug): mavacamten

Why not just ask the model?

Ask a plain model to "assemble the published evidence base for mavacamten's HCM submission" and it invents the asset→trial→paper linkage — plausible trial acronyms, PMIDs, journals, and citation counts that read like the literature and are wrong.

  • Plain model: fabricated trial acronyms, made-up NCTs and PMIDs, guessed citation counts, and no way to tell a retracted paper from a sound one.
  • Amass: the real TrialCore rows for the asset's Phase-3 search, and each trial's referencesBiomedCore edge walked in one hop to the publications that describe it — every paper arriving with its PMID, journal, journalQualityJufo tier, isRetracted flag, and citation count copied verbatim. The cross-core edge is the load-bearing primitive; the canonical Amass IDs (AMTC_… / AMBC_…) are the stable audit trail.

Why a skill, not a prompt?

This is a multi-step orchestration, not a single question: one TrialCore search for the asset's pivotal trials, a 10-cap completeness check on that result set, a get_amass_trialcore_record per trial to read its identity and referencesBiomedCore array, then a fan-out — a get_amass_biomedcore_record for every referenced paper (37 fetches here) — followed by a union/dedupe across trials and a two-file Office assembly. Packaging it as a skill means you trigger the whole chain with one line instead of pasting a brittle, branch-heavy procedure every time.

Honest scope

It assembles and trust-screens evidence; it does not author regulatory conclusions. The Phase-3 search returns at most 10 trials — for mavacamten it returned 6, so the trial set is complete and the skill says so; an asset that hits the 10-cap is a relevance sample, not a census, and the skill fires a truncation banner (broaden by widening phase or wording and unioning the results). Per-paper figures are verbatim Amass fields and can lag the registry by hours; any abstract-derived claim the returned text does not state is written "not in abstract," never guessed. The verdict "0 of 37 cited papers carry isRetracted=true" is a checkable field claim, not an assurance of quality.

Install the skill

Add the skill to Claude

Download SKILL.md and add it to Claude (Settings → Capabilities → Skills, or drop it in your Claude Code skills directory), then paste the prompt above to trigger it.

Run it yourself

Connect Amass to Claude and paste the prompt.

No build, no deploy — the connector takes about a minute, then this workflow runs on your own inputs.