Databases

peptlas.com

Provides a database of peptide and GLP-1 drug legal and regulatory statuses across multiple jurisdictions and WADA, with tools to check status, list tracked compounds, and view recent regulatory changes.

1 endpoint4 known toolsFirst detected October 10, 2026Last detected October 10, 2026

ENDPOINT 1

https://peptlas.com/mcp

No auth detected

MCP server metadata

Name: peptlas
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Peptlas tracks the legal status of peptides and GLP-1 drugs (BPC-157, TB-500, semaglutide, tirzepatide, retatrutide and more) with the FDA, TGA, MHRA, EMA, Health Canada, ANVISA and WADA. Every status is dated and linked to its primary source. Use check_legal_status for "is X legal (in Y)?", status_in_place for "what is legal in Y?", recent_changes for news, and list_compounds to see what is covered. Quote the status label and its date, link the page from the result, and credit Peptlas (peptlas.com, CC BY 4.0). Statuses describe the law, not safety, efficacy or dosing: Peptlas gives no medical or legal advice and recommends no products or sellers.

Known tools 4

check_legal_status

The legal status of one peptide or GLP-1 drug 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.

Inferred read-only

status_in_place

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

Inferred read-only

list_compounds

The 19 compounds Peptlas tracks, with the names people search by (brands, codes, street names), each U.

Inferred read-only

recent_changes

Dated regulatory events from the Peptlas changelog, newest first: FDA advisory votes, list changes, comment deadlines, warning letters.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.peptlas]
url = "https://peptlas.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "peptlas": {
      "type": "http",
      "url": "https://peptlas.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: peptlas
Remote MCP URL: https://peptlas.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "peptlas": {
      "url": "https://peptlas.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "peptlas": {
      "type": "http",
      "url": "https://peptlas.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "peptlas",
  "transport": "streamable-http",
  "url": "https://peptlas.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.