PepBank Peptide Research MCP: BPC-157, Retatrutide and Tirzepatide Studies and Trials

ONLINE PepBank Peptide Research MCP: BPC-157, Retatrutide and Tirzepatide Studies and Trials answered an MCP connection on 05 Nov 2026 and introduced itself as PepBank 1.5.2 (MCP protocol 2025-06-18).

15 tools offered to AI assistants

• resolve_peptide · Return peptide IDs and name matches for a name, alias or code. Use this before other calls when the name is unclear. Use search_peptides instead to browse or filter many peptides. Matching order: exact alias, normalized alias, trigram simil
• get_peptide_brief · For a dose question, use studied_doses together with get_community_practice. Return a precomputed summary of one peptide: identity, sequence, checked findings by evidence class, trials, key findings with citations, coverage and notices. reg
• get_community_practice · Return what community sources report about how people use one peptide: uses, regimens (route, amount, how often, how long), reported side effects, cautions and regulatory status notes such as US compounding policy, each line with its source
• search_peptides · Return peptides with identity and evidence counts. Use this to browse or filter by text, category, kind, evidence level, registry level or the curated launch list. Use resolve_peptide instead for one unclear name, or get_peptide_brief for o
• search_findings · Return checked findings with exact total_count and source sentences in included.passages. Each finding is one claim from one paper. Use this for specific outcomes, with filters for peptide, evidence class, design, claim type, peptide role,
• search_publications · Return stored papers with citation identifiers and extraction status. Use this for paper discovery, publication dates or unchecked coverage. Use search_findings instead for checked claims and source sentences, or get_peptide_brief for a pep
• search_trials · Return registered clinical trials with registry status, phase, posted-results status and peptide role. Use this for clinical development and trial records. Use search_findings instead for checked study results, or get_record for one full tr
• search_live_sources · Return live, unchecked papers from Europe PMC. Use this for gaps in database coverage or an explicit live literature search. Use search_publications instead for stored papers, or search_findings for checked claims. Live results have a separ
• get_record · Return one full peptide, publication, finding or trial record by PEP-, PUB-, FND- or TRL- ID. A peptide slug, PMID or NCT number also works. Use this for known records or fields omitted from compact results. Use resolve_peptide instead for
• get_evidence_map · Return checked finding counts for one peptide by outcome group, evidence class and direction, plus year, design and safety counts. Use this to inspect evidence coverage and gaps. Use search_findings instead for individual claims and source
• compare_peptides · Return identity, evidence counts, outcome groups and top findings for 2 to 5 peptides, plus shared outcome groups. Use this for a comparison in one call. Use get_peptide_brief instead for a detailed summary of one peptide. The result compar
• get_changes · Return record change events in sequence order. Use this to synchronize data after since_seq, with 0 for full history. Without since_seq, the response gives the newest page. next_since_seq supplies the continuation position. Use get_freshnes

What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method

Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.