Skip to content

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs…

you.curo/peptide-researchcuro.youstreamable-httpv1.0.5Scanned

Peptide research for your AI: PepBank study findings plus the curo.you peptide catalog and lot COAs.

8 tools: 1 change things and 7 only read.

Tools: 0 delete, 0 irreversible, 1 write, 7 read.
  • Reads private data · 1
  • Reads text others write · 8
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… can do

The Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… is published by curo.you, a domain the MCP Registry verified. It has 8 tools. It can create or change data (1 tool: build_cart), but cannot delete data. 7 tools only read.

1 tool reads private data (get_store_info); 8 tools bring in text other people can write (search_products, get_product, build_cart and 5 more).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.0.5.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

8 tools

Changes things 1Claude Code: ask
  • build_cartMake a curo.you cart link for products and quantities.Reads text others writeNo findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Make a curo.you cart link for products and quantities. Use it only when the user wants to buy. It does not place an order or take payment: the user opens cart_link, then checks out and pays on curo.you. Returns the cart lines and cart_link.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 7Show 7 read-only tools
  • get_coaRead third-party lab reports (COAs) by lot number or product.Reads text others writeNo findings

    Why it is in this group

    • The name "get_coa" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read third-party lab reports (COAs) by lot number or product. Each report gives the lab, lot, test date, identity result, purity, potency, a report link and a link to verify it on the lab's own site. Use it for questions about testing, purity or a lot number, and to check that a lab report is real. Use get_product for prices and stock.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_productRead every dose of one Curo product, with price, stock and the lab reports (COAs) for each lot.Reads text others writeNo findings

    Why it is in this group

    • The name "get_product" says "get": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read every dose of one Curo product, with price, stock and the lab reports (COAs) for each lot. Call search_products first and pass a slug from its results. Use get_coa when the user gives a lot number.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • get_store_infoRead Curo's shipping, returns, contact and research-use-only policies, with a link to each policy page.Reads private dataReads text others writeNo findings

    Why it is in this group

    • The name "get_store_info" says "get": a word for reading.

    What it can reach

    • private-dataThe description's first sentence says "read" and "contact": it reads contacts.
    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read Curo's shipping, returns, contact and research-use-only policies, with a link to each policy page. Use it for questions about delivery, refunds or how to reach Curo. Product facts come from search_products and get_product.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • peptide_researchRead the PepBank brief for one peptide: names and aliases, an evidence summary split into human, animal and lab studies, key findings with citations, regulatory status, and the Pep…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read the PepBank brief for one peptide: names and aliases, an evidence summary split into human, animal and lab studies, key findings with citations, regulatory status, and the PepBank credit line to show with the answer. Use it when the user names one peptide. Use search_research for a question across many studies, such as an outcome or a body system. If PepBank has no data, the result gives a PepBank link.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • search_productsFind Curo products by peptide or product name, or list all products when query is empty.Reads text others writeNo findings

    Why it is in this group

    • The name "search_products" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Find Curo products by peptide or product name, or list all products when query is empty. Returns name, slug, dose, price in USD, stock, a lab report link and a buy link. Use get_product for every dose of one product with its lot reports. Use peptide_research for what the studies say.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • search_researchSearch PepBank study findings across all peptides by topic, outcome or question.Reads text others writeNo findings

    Why it is in this group

    • The name "search_research" says "search": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Search PepBank study findings across all peptides by topic, outcome or question. Each result gives the finding in plain words, the peptide, the evidence class and its source passages. The response also gives the PepBank credit line to show. Use it for questions like "which peptides were studied for tendon healing". Use peptide_research when the user names one peptide.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • use_and_doseRead what community sources report about how people use one peptide: uses, route, amount, frequency, duration, reported effects and cautions, each line with its sources.Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Read what community sources report about how people use one peptide: uses, route, amount, frequency, duration, reported effects and cautions, each line with its sources. Also read the doses from published studies, with species, route, study design and source. Community reports are not tested in trials. Use it for use, dose or cycle questions. Use peptide_research for what the studies found. A peptide can have no record.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.

Reads private data1
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write8
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 17, 2026, 15:23 UTC, unchanged since Nov 3, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.curo.you/mcp: tools/list returned 8 tools to an anonymous client, including build_cart (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools1 added, 1 changed.+1 added~1 changedView diff
  2. Tools7 changed.~7 changedView diff

Install

Pinned to version 1.0.5. Values in angle brackets are yours to fill in.

claude mcp add --transport http peptide-research https://mcp.curo.you/mcp
claude mcp add --transport http peptide-research https://mcp.curo.you/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__peptide-research__search_products",
      "mcp__peptide-research__get_product",
      "mcp__peptide-research__get_coa",
      "mcp__peptide-research__get_store_info",
      "mcp__peptide-research__peptide_research",
      "mcp__peptide-research__search_research",
      "mcp__peptide-research__use_and_dose"
    ],
    "ask": [
      "mcp__peptide-research__build_cart"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as peptide-research. Review it before you use it.

Capability tags behind 8 rules
  • mcp__peptide-research__search_products untrusted-input
  • mcp__peptide-research__get_product untrusted-input
  • mcp__peptide-research__build_cart untrusted-input
  • mcp__peptide-research__get_coa untrusted-input
  • mcp__peptide-research__get_store_info private-data, untrusted-input
  • mcp__peptide-research__peptide_research untrusted-input
  • mcp__peptide-research__search_research untrusted-input
  • mcp__peptide-research__use_and_dose untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/you.curo/peptide-research/verify?hash=be88a6bd44a449d54bdca4fab18fbd7c5d3cdf00690d32c93cf2f78dbdd67669" | jq -e '.changed == false'

Pinned hash be88a6bd44a4, from Nov 16, 2026, 23:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/you.curo/peptide-research/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for you.curo/peptide-research
[![Anlyon Radar](https://radar.anlyon.com/badge/you.curo/peptide-research.svg)](https://radar.anlyon.com/servers/you.curo/peptide-research)

Source: MCP Registry · repository. Synced Nov 3, 2026, 11:18 UTC.

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs…: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… safe?

No scan can promise that. What its definitions show: 8 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… have?

8 tools: 1 write, 7 read. build_cart, search_products, get_product, get_coa, get_store_info, peptide_research, search_research and use_and_dose.

Does the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs… changed its tools?

Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.