_ registry / mcp http-sse · checked 2h ago

peptlas

https://peptlas.com

Registry code: fac1eea26297129c

api record

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…

endpoint
https://peptlas.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is peptlas live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is peptlas free to use?
Yes — the hub reached it with no key and no payment.
What tools does peptlas have?
4 tools: status_in_place, check_legal_status, list_compounds, recent_changes.
Is peptlas safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
374ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 4 tools
2 open 2 never probed 2 of 4 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_compounds open 2h ago

    The 19 compounds 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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "us_status": {
          "enum": [
            "compounding_legal",
            "under_review",
            "in_limbo",
            "restricted",
            "unscheduled"
          ],
          "type": "string",
          "description": "Only compounds with this U.S. status."
        }
      }
    }
    arguments 17 lines
  • recent_changes open 2h ago

    Dated regulatory events from the Peptlas changelog, newest first: FDA advisory votes, list changes, comment deadlines, warning letters. Optionally for one compound or since a date. Use it for "what changed" or "any news on BPC-157".

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1,
          "description": "How many events, newest first (1-50)."
        },
        "since": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Only events on or after this date (YYYY-MM-DD)."
        },
        "compound": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "Only this compound. Omit it for every compound."
        }
      }
    }
    arguments 24 lines
  • status_in_place unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "place"
      ],
      "properties": {
        "place": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "A country, region or regulator: \"Australia\", \"UK\", \"Germany\" (EU), \"Brazil\", \"FDA\", or \"sport\" for WADA."
        },
        "status": {
          "enum": [
            "compounding_legal",
            "under_review",
            "in_limbo",
            "restricted",
            "unscheduled"
          ],
          "type": "string",
          "description": "Only this status: compounding_legal, under_review, in_limbo, restricted or unscheduled."
        }
      }
    }
    arguments 26 lines
  • check_legal_status unknown 2h ago

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

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "compound"
      ],
      "properties": {
        "place": {
          "type": "string",
          "maxLength": 60,
          "minLength": 1,
          "description": "A country, region or regulator: \"Australia\", \"UK\", \"Germany\" (EU), \"Brazil\", \"FDA\", or \"sport\" for WADA. Omit it for every place."
        },
        "compound": {
          "type": "string",
          "maxLength": 100,
          "minLength": 1,
          "description": "A compound by name, brand, code or street name: \"BPC-157\", \"Ozempic\", \"tirzepatide\", \"reta\", \"TB500\"."
        }
      }
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id fac1eea26297129c.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/fac1eea26297129c/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/fac1eea26297129c/badge.svg)](https://brick.blue/agent/fac1eea26297129c?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
80%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.