# TruePeptideSource (remote · truepeptidesource.com)

Peptide reference and exact math: reconstitution units, blends, supply, dose ranges by origin.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `truepeptidesource.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-truepeptidesource-peptides/truepeptidesource.md), [page](https://verifymcp.io/servers/com-truepeptidesource-peptides/truepeptidesource)

## Channel facts

- Endpoint: `https://truepeptidesource.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1490 tokens (~248/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the TruePeptideSource MCP server?

TruePeptideSource is a hosted endpoint at https://truepeptidesource.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-truepeptidesource-peptides 'https://truepeptidesource.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-truepeptidesource-peptides": {
      "url": "https://truepeptidesource.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-truepeptidesource-peptides": {
      "type": "http",
      "url": "https://truepeptidesource.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-truepeptidesource-peptides]
url = "https://truepeptidesource.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-truepeptidesource-peptides": {
      "type": "remote",
      "url": "https://truepeptidesource.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-truepeptidesource-peptides --url 'https://truepeptidesource.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-truepeptidesource-peptides:
    url: "https://truepeptidesource.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-truepeptidesource-peptides": {
      "Transport": "http",
      "Url": "https://truepeptidesource.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-truepeptidesource-peptides -t streamable-http -u 'https://truepeptidesource.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-truepeptidesource-peptides": {
      "type": "http",
      "url": "https://truepeptidesource.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 84, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 83, +1)

- [functional] Server version: 1.0.0+2a55313 → 1.0.0+3d08ee3

### 2026-11-17 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 80, 0)

- [functional] Server version: 1.0.0+e5a59d6 → 1.0.0+2a55313

### 2026-11-12 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 78, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “peptide_lookup” rewrote its description, which is the text the model reads
- [functional] Server version: 1.0.0+52e9fbb → 1.0.0+e5a59d6

## MCP tools (6)

### `peptide_lookup` (~148 tokens)

Look up a peptide

For questions about one peptide: published dose ranges and protocols, reconstitution, vial sizes, side effects, storage, half-life, FDA status, stacks and community reports. Each dose row carries an origin label (study, regulator, protocol sites, community), sources and page links.

Input parameters:

- `peptide` (string, required): Peptide name, alias or slug, e.g. "BPC-157", "reta", "semaglutide", "CJC-1295 + Ipamorelin".
- `sections` (array): Sections to return. Omit for overview and dosing. Add others as needed, e.g. ["side_effects","community"] or ["storage","reconstitution"].

### `peptide_reconstitution_calculator` (~311 tokens)

Reconstitution and syringe units

Exact reconstitution math for a single-peptide vial: insulin syringe units for a dose, concentration after adding bacteriostatic water and doses per vial, or the dose held in a given number of units. Flags likely mg/mcg mix-ups against the peptide's published range. Returns a calculator link.

Input parameters:

- `dose` (number): Dose amount, e.g. 250 with doseUnit mcg. Give dose OR unitsDrawn.
- `doseUnit` (string): Unit of the dose (mcg, mg or IU). Required with dose; with unitsDrawn it picks the unit of the answer.
- `peptide` (string): Optional peptide name. Adds its IU factor, a range check and its published injected ranges.
- `syringe` (string): Insulin syringe type. "U-100" (the common 1 mL / 0.5 mL / 0.3 mL insulin syringe) unless the user says otherwise.
- `unitsDrawn` (number): Syringe units drawn, to get the dose they hold. Give dose OR unitsDrawn.
- `vialAmount` (number, required): Amount of peptide in the vial, e.g. 10 for a 10 mg vial.
- `vialUnit` (string): Unit of the vial amount: mg for nearly every peptide, IU for HGH-type vials.
- `waterMl` (number, required): Bacteriostatic water added to the vial, in mL, e.g. 2.

### `peptide_search` (~101 tokens)

Search peptides

Lists the peptides TruePeptideSource covers, matched by name, alias or topic (GLP-1, healing, weight loss, sleep). Returns names, one-line summaries, FDA status, evidence level and page links.

Input parameters:

- `category` (string): Optional category filter.
- `query` (string): Name, alias or topic, e.g. "tb", "ipamorelin", "GLP-1", "healing". Empty lists everything.

### `peptide_compare` (~153 tokens)

Compare two peptides

Side-by-side comparison of two peptides (e.g. semaglutide vs tirzepatide, BPC-157 vs TB-500): evidence, FDA status, half-life, routes, vial sizes, storage, published dose ranges and key differences, each labelled by origin.

Input parameters:

- `a` (string, required): Peptide name, alias or slug, e.g. "BPC-157", "reta", "semaglutide", "CJC-1295 + Ipamorelin".
- `b` (string, required): Peptide name, alias or slug, e.g. "BPC-157", "reta", "semaglutide", "CJC-1295 + Ipamorelin".

### `peptide_blend_calculator` (~380 tokens)

Blend vial calculator

Math for vials holding two or more peptides (KLOW, GLOW, BPC-157 + TB-500, CJC-1295 + Ipamorelin): units to draw and how much of each peptide one draw delivers. Name a known blend or list the components, then give the dose for one component (targetPeptide) or for the whole blend (totalDose).

Input parameters:

- `blend` (string): A blend TruePeptideSource covers, e.g. "KLOW", "GLOW", "BPC-157 + TB-500". Its label amounts are used unless components is given.
- `components` (array): Vial contents, 2 to 6 peptides, e.g. [{"peptide":"BPC-157","amount":10,"unit":"mg"},{"peptide":"TB-500","amount":10,"unit":"mg"}].
- `composition` (string): For a blend sold in several versions, which one, e.g. "70 mg". Omit for the first; the result lists the others.
- `dose` (number, required): Dose of targetPeptide, or of the whole blend when totalDose is true.
- `doseUnit` (string, required): Unit of the dose: mcg or mg.
- `syringe` (string): Insulin syringe type. "U-100" (the common 1 mL / 0.5 mL / 0.3 mL insulin syringe) unless the user says otherwise.
- `targetPeptide` (string): The component the dose is for. Use with dose.
- `totalDose` (boolean): True when the dose is for the whole blend ("2 mg of KLOW"), false when it is for targetPeptide.
- `waterMl` (number, required): Bacteriostatic water added, in mL.

### `peptide_supply_calculator` (~273 tokens)

Supply and cost planner

Plans supply and cost: how long a vial lasts, how many vials a cycle needs, and cost per dose, week and cycle when pricePerVial is given. Counts whole doses and respects how long a mixed vial keeps (from the dataset when a peptide is named).

Input parameters:

- `dose` (number, required): Dose per injection, e.g. 250.
- `doseUnit` (string, required): Unit of the dose. BPC-157 is usually dosed in mcg, GLP-1s like semaglutide in mg, HGH in IU.
- `durationWeeks` (integer, required): Cycle length in weeks, e.g. 8.
- `frequency` (string, required): How often the dose is taken.
- `peptide` (string): Optional peptide name, for its IU factor and mixed-vial shelf life.
- `pricePerVial` (number): Price of one vial in US dollars, for cost answers.
- `useWithinDays` (number): Days a mixed vial may be used. Omit to use the peptide's dataset value.
- `vialAmount` (number, required): Amount of peptide per vial, e.g. 5 for a 5 mg vial.
- `vialUnit` (string): Unit of the vial amount: mg for nearly every peptide, IU for HGH-type vials.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-truepeptidesource-peptides/truepeptidesource#diagnostics

## Score history

- 2026-11-21: 84
- 2026-11-20: 83
- 2026-11-19: 83
- 2026-11-18: 82
- 2026-11-17: 82
- 2026-11-16: 81
- 2026-11-15: 81
- 2026-11-14: 81
- 2026-11-13: 80
- 2026-11-12: 80
- 2026-11-11: 79
- 2026-11-10: 79
- 2026-11-09: 78
- 2026-11-08: 78
- 2026-11-07: 77
- 2026-11-06: 77
- 2026-11-05: 76
- 2026-11-04: 76
- 2026-11-03: 75
- 2026-11-02: 75
- 2026-11-01: 74
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72
- 2026-10-25: 71

## Common questions

### What is the TruePeptideSource MCP server?

TruePeptideSource is an MCP server listed in the public MCP registry as com.truepeptidesource/peptides. Peptide reference and exact math: reconstitution units, blends, supply, dose ranges by origin. This page covers its hosted endpoint (https://truepeptidesource.com/mcp).

### Is the TruePeptideSource MCP server safe to use?

TruePeptideSource scores 84 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the TruePeptideSource MCP server expose?

TruePeptideSource exposes 6 tools: peptide_lookup, peptide_reconstitution_calculator, peptide_search, peptide_compare, peptide_blend_calculator, peptide_supply_calculator. Their descriptions and schemas cost roughly 1,366 tokens of context every time the server is loaded.

### Does the TruePeptideSource MCP server require authentication?

No. We connected to TruePeptideSource without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the TruePeptideSource MCP server still maintained?

TruePeptideSource is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the TruePeptideSource MCP server?

VerifyMCP ran 13 checks on TruePeptideSource, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://truepeptidesource.com/mcp
- Website: https://truepeptidesource.com/ai
- Changelog RSS feed: https://verifymcp.io/servers/com-truepeptidesource-peptides/truepeptidesource.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-truepeptidesource-peptides/truepeptidesource/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-truepeptidesource-peptides/truepeptidesource.json
- HTML version of this page: https://verifymcp.io/servers/com-truepeptidesource-peptides/truepeptidesource
