
Peptlas MCP server
Which MCP servers are Peptlas's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.peptlas/legal-statusverified in the MCP registry
The registry name sits under peptlas.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools4
- Server calls itselfpeptlas
- Server version1.1.0
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 202 ms.
- Whether its tools do the product's job has not been judged yet.
- Checked on 1 of the 7 days it takes to judge reliability.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP scoreafter a weeka score needs 7 daily checks: 1 so far
- Answeredmeasuring1 of the 7 daily checks it takes to print a share
- Median first answer313 ms
- Space in an agent's context≈ 781 tokensthe definitions of all its tools (4), which an agent carries on every turn
- Tool definitionsA · 100 of 100
- Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once
- Every tool passes all six checks.
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
check_legal_statusThe 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…
status_in_placeEvery 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.
list_compoundsThe 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.
recent_changesDated 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…
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"legal-status": {
"type": "http",
"url": "https://peptlas.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http peptlas https://peptlas.com/mcpclaude.ai, ChatGPT and other clients: add https://peptlas.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Cookies
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.