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

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

• 连接方式: 在云端运行
• 传输方式: Streamable HTTP
• 分类: 搜索与 AI 记忆

安装

选择你使用的 AI 应用，然后复制设置。

你需要

• 在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

https://pepbank.io/mcp

claude mcp add --transport http pepbank https://pepbank.io/mcp

{
  "mcpServers": {
    "pepbank": {
      "url": "https://pepbank.io/mcp"
    }
  }
}

{
  "servers": {
    "pepbank": {
      "type": "http",
      "url": "https://pepbank.io/mcp"
    }
  }
}

https://pepbank.io/mcp

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月6日 报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

• 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 similarity, then edit distance. Normalization

• 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. regulatory gives approval by place and use,

• 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 sources. Community-reported, not tested in tri

• 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 one peptide summary. evidence_level comes

• 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, direction, outcome group, body system an

• 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 peptide overview. extraction_status identif

• 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 trial. The default role=tests lists and co

• 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 separate unchecked label.

• 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 an unclear name, or search_publications

• 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 sentences, or compare_peptides for sever

• 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 compares evidence without ranking peptides as

• 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_freshness instead for source import times, or ge

• replay_query

  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 identical data. Use search_findings with as_of_seq instead for a new search at an earlier sequence, or get_record with as_of_s

• get_freshness

  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 for caller quotas. lag_hours measures time since success, not upstream backlog. source_latest_known is not reported

• get_my_usage

  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 instead for source import times, or get_changes for record updates. This tool reports account access, not evidence coverage.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

• ✓ 通过

  作者与仓库一致

  注册名称已通过域名 pepbank.io 验证（注册中心会核实域名所有权）

• … 尚未检查

  仍在维护

  我们还没有从 GitHub 读取这个仓库

• … 尚未检查

  有许可证

  我们还没有从 GitHub 读取这个仓库

• ✓ 通过

  端点有响应

  在 1828 毫秒内响应（HTTP 200）

• – 不适用

  使用 OAuth 登录

  无需登录

• ✓ 通过

  工具描述中没有隐藏指令

  已读取 15 个工具描述，未发现针对 AI 的隐藏指令

与“搜索与 AI 记忆”中的其他服务器比较i

• 星标数多于此分类中其他 7251 个服务器的 0%
• 发布到注册中心的时间比此分类中其他 7251 个服务器的 96% 更新
• 基础检查结果等于或优于此分类中其他 7251 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

作者的 README

https://pepbank.io/mcp

claude mcp add --transport http pepbank https://pepbank.io/mcp

[mcp_servers.pepbank]

{ "mcpServers": { "pepbank": { "url": "https://pepbank.io/mcp" } } }

{ "servers": { "pepbank": { "type": "http", "url": "https://pepbank.io/mcp" } } }

{ "mcpServers": { "pepbank": { "httpUrl": "https://pepbank.io/mcp" } } }

npx pepbank brief BPC-157

{ "mcpServers": { "pepbank": { "command": "npx", "args": ["-y", "pepbank"] } } }

npx skills add pepbank/peptide-research-mcp