Peptlas: is this peptide legal?
REMOTE · PEPTLAS.COM
Legal status of peptides and GLP-1 drugs in the US, UK, EU, Australia, Canada, Brazil and sport.
Available components
Last scanned (30 minutes ago)
Scores higher than 85% 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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 747 tokens (~186/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +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.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 24 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
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://peptlas.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=peptlas.com | CN=WE1,O=Google Trust Services,C=US | 3 Nov 2026 | 1 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 5e13456fd7ce66ea0ec0414906b11427 |
| SANs: peptlas.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of peptlas.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| peptlas.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://peptlas.com/mcp | Verified | 200 | |
| http (plaintext) | http://peptlas.com/mcp | HTTPS enforced | 301 | https://peptlas.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 →
check_legal_status Is this peptide legal? ~232
The legal status of one peptide, GLP-1 drug or seller-named blend (KLOW, GLOW, the Wolverine stack) in the United States (FDA), Australia (TGA), the UK (MHRA), the EU (EMA), Canada (Health Canada), Brazil (ANVISA, where covered) and sport (WADA), or in the one place you name. Returns each status with a plain-language note; for the U.S. also the full answer (compounding rules, the latest FDA advisory vote, the next dated event), plus primary sources and the date it was last verified.
| Name | Type | Req | Description |
|---|---|---|---|
| compound | string | yes | A compound by name, brand, code or street name ("BPC-157", "Ozempic", "reta", "TB500"), or a blend ("KLOW", "GLOW", "Wolverine stack"). |
| place | string | – | A country, region or regulator: "Australia", "UK", "Germany" (EU), "Brazil", "FDA", or "sport" for WADA. Omit it for every place. |
No output schema declared.
No examples provided.
list_compounds List compounds ~69
The 26 compounds and 3 blends Peptlas tracks, with the names people search by (brands, codes, street names), each U.S. status and its page. Use it to see what is covered.
| Name | Type | Req | Description |
|---|---|---|---|
| us_status | string | – | Only compounds with this U.S. status. |
No output schema declared.
No examples provided.
recent_changes Recent changes ~125
Dated regulatory events from the Peptlas changelog, newest first: FDA advisory votes, list changes, comment deadlines, warning letters. Optionally for one compound (or a blend, meaning all its ingredients) or since a date. Use it for "what changed" or "any news on BPC-157".
| Name | Type | Req | Description |
|---|---|---|---|
| compound | string | – | Only this compound. Omit it for every compound. |
| limit | integer | – | How many events, newest first (1-50). |
| since | string | – | Only events on or after this date (YYYY-MM-DD). |
No output schema declared.
No examples provided.
status_in_place What is legal in a country? ~114
Every tracked peptide in one place, with its status and a note: use it for "which peptides are legal in Australia" or "what does WADA ban". Optionally only one status.
| Name | Type | Req | Description |
|---|---|---|---|
| place | string | yes | A country, region or regulator: "Australia", "UK", "Germany" (EU), "Brazil", "FDA", or "sport" for WADA. |
| status | string | – | Only this status: compounding_legal, under_review, in_limbo, restricted or unscheduled. |
No output schema declared.
No examples provided.
How do I install the Peptlas: is this peptide legal? MCP server?
Peptlas: is this peptide legal? is a hosted endpoint at https://peptlas.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 · peptlas.com
claude mcp add --transport http com-peptlas-legal-status 'https://peptlas.com/mcp'
What is the Peptlas: is this peptide legal? MCP server?
Peptlas: is this peptide legal? is an MCP server listed in the public MCP registry as com.peptlas/legal-status. Legal status of peptides and GLP-1 drugs in the US, UK, EU, Australia, Canada, Brazil and sport. This page covers its hosted endpoint (https://peptlas.com/mcp).
Is the Peptlas: is this peptide legal? MCP server safe to use?
Peptlas: is this peptide legal? scores 82 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 Peptlas: is this peptide legal? MCP server expose?
Peptlas: is this peptide legal? exposes 4 tools: check_legal_status, status_in_place, list_compounds, recent_changes. Their descriptions and schemas cost roughly 540 tokens of context every time the server is loaded.
Does the Peptlas: is this peptide legal? MCP server require authentication?
No. We connected to Peptlas: is this peptide legal? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Peptlas: is this peptide legal? MCP server still maintained?
Peptlas: is this peptide legal? 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.