# PepBank Peptide Research MCP: BPC-157, Retatrutide and Tirzepatide Studies and Trials (slim)

> PepBank Peptide Research MCP: BPC-157, Retatrutide and Tirzepatide Studies and Trials, an MCP server by pepbank.io, listed from the official MCP registry. Indexed, not reviewed: facts and our own checks, no score or ranking. Studies and clinical trials for BPC-157, retatrutide…

- Full: https://www.anchorterminal.com/tools/pepbank.md (~1,300 tokens) · this version ~1,230 tokens · JSON https://www.anchorterminal.com/tools/pepbank.json · canonical https://www.anchorterminal.com/tools/pepbank
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-10
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

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

> Indexed, not reviewed: facts from the official MCP registry and our own checks. No score, grade or rank, and not in the rankings until the panel reviews it. How the index works: https://www.anchorterminal.com/indexed/

- Kind: MCP server, by pepbank.io (https://pepbank.io/developers)
- Listed because: It's published in the registry under pepbank.io, a namespace the registry only gives to whoever proves they control that domain.
- What the official MCP registry says: Studies and clinical trials for BPC-157, retatrutide, tirzepatide and 160+ peptides, with sources.

## Facts

- MCP registry: `io.pepbank/pepbank` 1.5.4
- Endpoint: https://pepbank.io/mcp (streamable HTTP)
- Package: npm `pepbank` (stdio)
- Source: https://github.com/pepbank/peptide-research-mcp
- Website: https://pepbank.io/developers
- npm downloads a week: 514
- GitHub stars: 0
- Registry entry updated: 2026-11-09

## Tools

- Tools it lists (15, about 9,005 tokens of context, `tools/list` without credentials over MCP 2026-07-28, checked 2026-11-10 02:37 UTC):
  - `resolve_peptide` (read-only): 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…
  - `get_peptide_brief` (read-only): For a dose question, use studied_doses together with get_community_practice. Return a precomputed summary of one peptide: identity, sequence, checked findings…
  - `get_community_practice` (read-only): Return what community sources report about how people use one peptide: uses, regimens (route, amount, how often, how long), reported side effects, cautions and…
  - `search_peptides` (read-only): 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…
  - `search_findings` (read-only): 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…
  - `search_publications` (read-only): Return stored papers with citation identifiers and extraction status. Use this for paper discovery, publication dates or unchecked coverage. Use…
  - `search_trials` (read-only): Return registered clinical trials with registry status, phase, posted-results status and peptide role. Use this for clinical development and trial records. Use…
  - `search_live_sources` (read-only): Return live, unchecked papers from Europe PMC. Use this for gaps in database coverage or an explicit live literature search. Use search_publications instead…
  - `get_record` (read-only): 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…
  - `get_evidence_map` (read-only): 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…
  - `compare_peptides` (read-only): 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_changes` (read-only): 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…
  - `replay_query` (read-only): Return 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…
  - `get_freshness` (read-only): Return 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` (read-only): Return the caller's plan, grants, quotas and usage in the current windows. Use this to inspect access limits and remaining allowances. Use get_freshness…
- How its tools read to an agent (0 errors, 1 warning, 0 notes, about 9,005 tokens; rules at https://www.anchorterminal.com/check.md; not part of the score):
  - warn TC22 search_findings: the definition is about 1,755 tokens

- JSON: https://www.anchorterminal.com/api/v1/tools/pepbank.json
- Being indexed says nothing about quality, and nobody can pay for it. Ask for a review: https://www.anchorterminal.com/builders/#claiming