TruePeptideSource MCP server
com.truepeptidesource/peptidestruepeptidesource.comstreamable-httpv1.0.0Scanned
Peptide reference and exact math: reconstitution units, blends, supply, dose ranges by origin.
6 tools: 3 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
3 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the TruePeptideSource MCP server can do
The TruePeptideSource MCP server is published by truepeptidesource.com, a domain the MCP Registry verified. It has 6 tools. It can create or change data (3 tools: peptide_reconstitution_calculator, peptide_blend_calculator and peptide_supply_calculator), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 9, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 3Claude Code: ask
peptide_blend_calculatorMath 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- title: Blend vial calculator
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
peptide_reconstitution_calculatorExact 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 giv…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Reconstitution and syringe units
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
peptide_supply_calculatorPlans 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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).
Annotations the server declares
- title: Supply and cost planner
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 3Show 3 read-only tools
peptide_compareSide-by-side comparison of two peptides (e.g.No findings
Why it is in this group
- The name "peptide_compare" says "compare": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Compare two peptides
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
peptide_lookupFor questions about one peptide: published dose ranges and protocols, reconstitution, vial sizes, side effects, storage, half-life, FDA status, stacks and community reports.No findings
Why it is in this group
- The name "peptide_lookup" says "lookup": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Look up a peptide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
peptide_searchLists the peptides TruePeptideSource covers, matched by name, alias or topic (GLP-1, healing, weight loss, sleep).No findings
Why it is in this group
- The name "peptide_search" says "search": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Search peptides
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 16, 2026, 14:22 UTC, unchanged since Oct 25, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://truepeptidesource.com/mcp: tools/list returned 6 tools to an anonymous client, including peptide_reconstitution_calculator (write), peptide_blend_calculator (write), peptide_supply_calculator (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:peptide_lookupOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http peptides https://truepeptidesource.com/mcpclaude mcp add --transport http peptides https://truepeptidesource.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__peptides__peptide_lookup",
"mcp__peptides__peptide_search",
"mcp__peptides__peptide_compare"
],
"ask": [
"mcp__peptides__peptide_reconstitution_calculator",
"mcp__peptides__peptide_blend_calculator",
"mcp__peptides__peptide_supply_calculator"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as peptides. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.truepeptidesource/peptides/verify?hash=ecd519845b43e289d8a7d380e5fb4e2311b3d5f8911caae316fb9db1b117a0d3" | jq -e '.changed == false'Pinned hash ecd519845b43, from Nov 9, 2026, 04:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.truepeptidesource/peptides/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.truepeptidesource/peptides)Source: MCP Registry. Synced Oct 25, 2026, 07:17 UTC.
TruePeptideSource MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the TruePeptideSource MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the TruePeptideSource MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the TruePeptideSource MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the TruePeptideSource MCP server have?
- 6 tools: 3 write, 3 read. peptide_reconstitution_calculator, peptide_blend_calculator, peptide_supply_calculator, peptide_lookup, peptide_search and peptide_compare.
Does the TruePeptideSource MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the TruePeptideSource MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the TruePeptideSource MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.