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

io.pepbank/pepbank · v1.5.3 · health-and-science

PepBank Peptide Research MCP: BPC-157, Retatrutide and Tirzepatide Studies and Trials is healthy: it completed an MCP handshake in 1281 ms and exposes 15 tools.

Studies and clinical trials for BPC-157, retatrutide, tirzepatide and 160+ peptides, with sources.

Endpoint: https://pepbank.io/mcp (streamable-http)

Repository · Website · JSON · Add to my inventory

Facts

Users (last 30 days)0
HandshakeHealthy
Auth neededNone
Tool count15
Latency1281 ms
Last checked (UTC)2026-11-05T21:10:45.070Z

Health history

Checked (UTC)StatusLatencyError
2026-11-05T21:10:45.070ZHealthy1281

Tools (15)

resolve_peptideReturn 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 similarity, then edit distance. Normalization ignores letter case
get_peptide_briefFor 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. regulatory gives approval by place and use, plus sport status.
get_community_practiceReturn 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 sources. Community-reported, not tested in trials. Use it for use,
search_peptidesReturn 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 one peptide summary. evidence_level comes only from checked f
search_findingsReturn 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, direction, outcome group, body system and year. Use search_p
search_publicationsReturn 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 peptide overview. extraction_status identifies the layer: extra
search_trialsReturn 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 trial. The default role=tests lists and counts trials that tes
search_live_sourcesReturn 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 separate unchecked label.
get_recordReturn 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 an unclear name, or search_publications to find papers. as_o
get_evidence_mapReturn 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 sentences, or compare_peptides for several peptides. Counts
compare_peptidesReturn 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 compares evidence without ranking peptides as better or worse. Eac
get_changesReturn 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_freshness instead for source import times, or get_record with as_of_
replay_queryReturn a saved search at its original data_seq, with the first page and result_set_hash comparison. Use this to check whether a recorded query reproduces identical data. Use search_findings with as_of_seq instead for a new search at an earlier sequence, or get_record with as_of_seq for one earlier r
get_freshnessReturn source import and extraction times from stored study results. Use this to inspect data freshness. Use get_changes instead for record events, or get_my_usage for caller quotas. lag_hours measures time since success, not upstream backlog. source_latest_known is not reported yet and remains null
get_my_usageReturn the caller's plan, grants, quotas and usage in the current windows. Use this to inspect access limits and remaining allowances. Use get_freshness instead for source import times, or get_changes for record updates. This tool reports account access, not evidence coverage.