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

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

- name: you.curo/peptide-research
- version: 1.0.5
- connection class: R0 (autonomous)
- trust: 96/100
- quality: 94/100 (new)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/you.curo%2Fpeptide-research
- tools: https://api.protogrid.dev/v1/servers/you.curo%2Fpeptide-research/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "peptide-research": {
      "type": "http",
      "url": "https://mcp.curo.you/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 100
- freshness: 100
- provenance: 85
- drivers: +repository +dns-namespace +website +reachable +uptime-100% +updated-4d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 94/100 (new)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 8 of 8 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 1,300 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: n/a (weight 15)

- n/a `stability.changes`, `stability.rug_pull`: tool history recorded for 5 of the 7 days needed

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: deps.dev does not know curo-peptides@1.0.2

- tools: 8, about 1,300 tokens to load them all
- tool set hash: 4be0295e70845a71acc926f5db5b66f4
- tools last changed: 2026-11-06T18:28:21.044Z
- badge: [![protogrid quality](https://protogrid.dev/badge/you.curo/peptide-research.svg)](https://protogrid.dev/servers/you.curo/peptide-research)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

- 2026-11-06 `use_and_dose` added
  - 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.
- 2026-11-06 `get_coa` changed (description)
  - before: 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. Use get_product for prices and stock.
  - after: 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.
- 2026-11-02 `search_research` changed (description, inputSchema) **meaning changed**
  - before: Search stored PepBank findings. Read sources and credit with each result.
  - after: 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.
- 2026-11-02 `peptide_research` changed (description, inputSchema) **meaning changed**
  - before: Read a PepBank peptide summary, main findings, sources, and credit.
  - after: 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.
- 2026-11-02 `get_store_info` changed (description) **meaning changed**
  - before: Read shipping, returns, contact, and research-use policies.
  - after: 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.
- 2026-11-02 `get_coa` changed (description, inputSchema) **meaning changed**
  - before: Read lab reports for a lot number or product.
  - after: 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. Use get_product for prices and stock.
- 2026-11-02 `build_cart` changed (description, inputSchema) **meaning changed**
  - before: Build a cart link from product IDs and quantities. The customer checks out and pays on curo.you.
  - after: 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.
- 2026-11-02 `get_product` changed (description, inputSchema) **meaning changed**
  - before: Read product variants, prices, stock, and lot reports.
  - after: 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.
- 2026-11-02 `search_products` changed (description, inputSchema) **meaning changed**
  - before: Find Curo products by name, or list all products.
  - after: 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.

Full history: https://api.protogrid.dev/v1/servers/you.curo%2Fpeptide-research/changes

## Dependencies

- npm curo-peptides@1.0.2: unknown

Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0.

## Remotes

- https://mcp.curo.you/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

- npm curo-peptides@1.0.2

## Tools (8)

- `build_cart`: 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.
- `get_coa`: 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.
- `get_product`: 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.
- `get_store_info`: 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.
- `peptide_research`: 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.
- `search_products`: 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.
- `search_research`: 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.
- `use_and_dose`: 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.