PeptideLab Calculator
REMOTE · SWISSPEP.COM · 5 COMPONENTS
Research-use peptide reconstitution & dosing calculators for 15 compounds. Not medical advice.
Last scanned (7 hours ago)
Scores higher than 8% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint returned HTTP 404. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (5)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (6)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 23 Oct 26 −48
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 22 Oct 26 +48
- Injection markers: unverified → pass ▲ security
- Authorization: unverified → partial ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Stability: unverified → 0.03 ▲ functional
- First check of Schema quality: good functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 71 functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- 21 Oct 26 23
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://swisspep.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=swisspep.com | CN=YE1,O=Let's Encrypt,C=US | 18 Oct 2026 | 16 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e787ed36484a232be33f84a3409aeca6fe |
| SANs: *.swisspep.com, swisspep.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of swisspep.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| swisspep.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 404 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://swisspep.com/mcp | HTTP error | 404 | |
| http (plaintext) | http://swisspep.com/mcp | HTTPS enforced | 301 | https://swisspep.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calc_reconstitution Peptide reconstitution calculator ~244
Calculate peptide reconstitution: concentration, draw volume, syringe units and doses per vial. Forward mode: dose_mcg. Reverse mode: pass dose_units to back-solve the dose. Returns precision (parallax) warnings, syringe overflow checks and concentration advisories. Research use only.
| Name | Type | Req | Description |
|---|---|---|---|
| dose_mcg | number | – | Target dose in mcg (forward mode). |
| dose_units | number | – | Syringe units drawn (reverse mode; back-solves the dose). |
| lang | string | – | Language for human-readable fields. |
| peptide | string | – | Peptide id or name (e.g. "bpc-157"). Optional context provider; use list_peptides to discover. |
| syringe_capacity_ml | number | – | Barrel capacity in ml. Common: 0.3, 0.5, 1. |
| syringe_type | string | – | Syringe grading: U-100 (1 ml = 100 units) or U-40 (1 ml = 40 units). |
| vial_mg | number | yes | Peptide amount in the vial, mg. |
| water_ml | number | yes | Bacteriostatic water added, ml. |
No output schema declared.
No examples provided.
compare_syringes Compare syringes ~88
Compare U-100 and U-40 syringes for one target dose: units required, fit and relative reading error (parallax risk). Sorted best-first. Research use only.
| Name | Type | Req | Description |
|---|---|---|---|
| dose_mcg | number | yes | – |
| lang | string | – | – |
| peptide | string | – | – |
| vial_mg | number | yes | – |
| water_ml | number | yes | – |
No output schema declared.
No examples provided.
get_protocol Get research protocol ~73
Get the full research protocol record for one peptide: dosing window, frequency, cycle, titration ladder (GLP-1 class), special notes and confidence grade. Research use only.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| peptide | string | yes | Peptide id or name, e.g. "semaglutide". |
No output schema declared.
No examples provided.
list_peptides List research peptides ~62
List or search the curated research peptide dataset (ids, names, aliases, categories, confidence grades, common dosing windows). Research use only.
| Name | Type | Req | Description |
|---|---|---|---|
| lang | string | – | – |
| query | string | – | Optional search: id, name, alias or category fragment. |
No output schema declared.
No examples provided.
plan_schedule Plan titration schedule ~195
Generate a week-by-week research schedule: frequency presets (daily / 1-3x weekly), GLP-1 style titration ladders and optional syringe-unit readouts per event. On-demand compounds return an advisory instead of a calendar. Research use only.
| Name | Type | Req | Description |
|---|---|---|---|
| days | array | – | 0=Mon … 6=Sun; count must match the frequency (daily=7, 1x=1, 2x=2, 3x=3). |
| lang | string | – | – |
| peptide | string | yes | Peptide id or name. |
| start_date | string | – | First day of week 1, YYYY-MM-DD (defaults to today, UTC). |
| vial_mg | number | – | With water_ml: adds per-event syringe units. |
| water_ml | number | – | With vial_mg: adds per-event syringe units. |
| weeks | integer | – | Schedule length in weeks. |
No output schema declared.
No examples provided.
plan_stack Plan a compound stack ~132
Plan a multi-compound stack: per-compound draw volumes and units, combined draw volume with split-injection advisories, and frequency-conflict detection. Research use only.
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | yes | 2–4 compounds in the stack. |
| lang | string | – | Language for human-readable fields. |
| syringe_capacity_ml | number | – | Barrel capacity in ml. Common: 0.3, 0.5, 1. |
| syringe_type | string | – | Syringe grading: U-100 (1 ml = 100 units) or U-40 (1 ml = 40 units). |
No output schema declared.
No examples provided.
How do I install the PeptideLab Calculator MCP server?
PeptideLab Calculator is a hosted endpoint at https://swisspep.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.
remote · swisspep.com
claude mcp add --transport http com-rigorpeptides-peptidelab 'https://swisspep.com/mcp'
What is the PeptideLab Calculator MCP server?
PeptideLab Calculator is an MCP server listed in the public MCP registry as com.rigorpeptides/peptidelab. Research-use peptide reconstitution & dosing calculators for 15 compounds. Not medical advice. This page covers its hosted endpoint (https://swisspep.com/mcp).
Is the PeptideLab Calculator MCP server safe to use?
PeptideLab Calculator scores 23 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 PeptideLab Calculator MCP server expose?
PeptideLab Calculator exposes 6 tools: calc_reconstitution, list_peptides, get_protocol, plan_schedule, plan_stack, compare_syringes. Their descriptions and schemas cost roughly 794 tokens of context every time the server is loaded.
Does the PeptideLab Calculator MCP server require authentication?
Its publisher declares no required credentials for PeptideLab Calculator. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the PeptideLab Calculator MCP server still maintained?
PeptideLab Calculator is still listed as active in the MCP registry. We last reached this channel on 5 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 PeptideLab Calculator MCP server?
VerifyMCP ran 5 checks on PeptideLab Calculator, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 1 more. 6 items could not be completed, a gap on our side rather than a finding about PeptideLab Calculator: Authorization, Schema quality, Stability, Tool coverage and 2 more. 5 categories score 0 for that reason, because we only credit what we can confirm. 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.