# 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.

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

## Components

- remote · `peptlas.com`: 82/100 (this document), [markdown](https://verifymcp.io/servers/com-peptlas-legal-status/peptlas.md), [page](https://verifymcp.io/servers/com-peptlas-legal-status/peptlas)

## Channel facts

- Endpoint: `https://peptlas.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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-05.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-peptlas-legal-status 'https://peptlas.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-peptlas-legal-status": {
      "url": "https://peptlas.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-peptlas-legal-status": {
      "type": "http",
      "url": "https://peptlas.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-peptlas-legal-status]
url = "https://peptlas.com/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-peptlas-legal-status --url 'https://peptlas.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-peptlas-legal-status:
    url: "https://peptlas.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-peptlas-legal-status": {
      "Transport": "http",
      "Url": "https://peptlas.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-peptlas-legal-status -t streamable-http -u 'https://peptlas.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-peptlas-legal-status": {
      "type": "http",
      "url": "https://peptlas.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-04 (score 82, +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.

### 2026-11-02 (score 81, +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-10-31 (score 80, +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.

### 2026-10-29 (score 79, +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.

### 2026-10-27 (score 78, +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.

### 2026-10-24 (score 77, +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.

### 2026-10-22 (score 76, +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.

### 2026-10-20 (score 75, +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.

## MCP tools (4)

### `check_legal_status` (~232 tokens)

Is this peptide legal?

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.

Input parameters:

- `compound` (string, required): 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.

### `status_in_place` (~114 tokens)

What is legal in a country?

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.

Input parameters:

- `place` (string, required): 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.

### `list_compounds` (~69 tokens)

List compounds

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.

Input parameters:

- `us_status` (string): Only compounds with this U.S. status.

### `recent_changes` (~125 tokens)

Recent changes

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".

Input parameters:

- `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).

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79
- 2026-10-28: 78
- 2026-10-27: 78
- 2026-10-26: 77
- 2026-10-25: 77
- 2026-10-24: 77
- 2026-10-23: 76
- 2026-10-22: 76
- 2026-10-21: 75
- 2026-10-20: 75
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 73
- 2026-10-14: 72
- 2026-10-13: 72
- 2026-10-12: 71
- 2026-10-10: 70

## Common questions

### 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.

## Links

- Remote endpoint: https://peptlas.com/mcp
- Repository: https://github.com/Peptlas/peptlas-mcp
- Website: https://peptlas.com/mcp-server/
- Changelog RSS feed: https://verifymcp.io/servers/com-peptlas-legal-status/peptlas.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-peptlas-legal-status/peptlas.json
- HTML version of this page: https://verifymcp.io/servers/com-peptlas-legal-status/peptlas