# Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) (remote · mcp.curo.you)

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

- Trust score: 76/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-04

## Components

- remote · `mcp.curo.you`: 76/100 (this document), [markdown](https://verifymcp.io/servers/you-curo-peptide-research/mcp.md), [page](https://verifymcp.io/servers/you-curo-peptide-research/mcp)
- npm · `curo-peptides`: 49/100, [markdown](https://verifymcp.io/servers/you-curo-peptide-research/curo-peptides.md), [page](https://verifymcp.io/servers/you-curo-peptide-research/curo-peptides)

## Channel facts

- Endpoint: `https://mcp.curo.you/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.5`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-04.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 969 tokens (~121/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 7/100
  - Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… server?

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… is a hosted endpoint at https://mcp.curo.you/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

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

### Cursor

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

### VS Code

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

### Codex

```toml
[mcp_servers.you-curo-peptide-research]
url = "https://mcp.curo.you/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "you-curo-peptide-research": {
      "type": "remote",
      "url": "https://mcp.curo.you/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add you-curo-peptide-research --url 'https://mcp.curo.you/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  you-curo-peptide-research:
    url: "https://mcp.curo.you/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "you-curo-peptide-research": {
      "Transport": "http",
      "Url": "https://mcp.curo.you/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add you-curo-peptide-research -t streamable-http -u 'https://mcp.curo.you/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-03 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-02 (score 75)

First indexed and scored.

## MCP tools (7)

### `search_products` (~99 tokens)

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.

Input parameters:

- `query` (string): Peptide or product name, for example BPC-157. Leave empty to list all products.

### `get_product` (~75 tokens)

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.

Input parameters:

- `slug` (string, required): The slug field from a search_products or get_product result.

### `build_cart` (~77 tokens)

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.

Input parameters:

- `items` (array, required): Products to add to the cart.

### `get_coa` (~99 tokens)

Get lab reports

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.

Input parameters:

- `query` (string, required): Lot number from the vial label, or a product name or slug.

### `get_store_info` (~57 tokens)

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` (~121 tokens)

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.

Input parameters:

- `peptide` (string, required): Peptide name or slug, for example BPC-157 or tb-500.

### `search_research` (~122 tokens)

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.

Input parameters:

- `cursor` (string): The next_cursor value from the previous result, to get the next page.
- `query` (string, required): Search words, for example tendon healing or BPC-157 inflammation.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/you-curo-peptide-research/mcp#diagnostics

## Score history

- 2026-11-04: 76
- 2026-11-03: 76
- 2026-11-02: 75

## Common questions

### What is the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… server?

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… is listed in the public MCP registry as you.curo/peptide-research. Peptide research for your AI: PepBank study findings plus the curo.you peptide catalog and lot COAs. This page covers its hosted endpoint (https://mcp.curo.you/mcp).

### Is the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… server safe to use?

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… scores 76 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… server expose?

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… exposes 7 tools: search_products, get_product, build_cart, get_coa, get_store_info, and 2 more. Their descriptions and schemas cost roughly 650 tokens of context every time the server is loaded.

### Does the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… server require authentication?

No. We connected to Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… server still maintained?

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup… is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.curo.you/mcp
- Repository: https://github.com/curo-you-peptides/peptide-research-mcp
- Website: https://curo.you/mcp?utm_source=mcp-registry&utm_medium=listing&utm_campaign=curo-mcp
- Changelog RSS feed: https://verifymcp.io/servers/you-curo-peptide-research/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/you-curo-peptide-research/mcp.json
- HTML version of this page: https://verifymcp.io/servers/you-curo-peptide-research/mcp