Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs)
REMOTE · MCP.CURO.YOU · 2 COMPONENTS
Peptide research for your AI: PepBank study findings plus the curo.you peptide catalog and lot COAs.
Available components
Last scanned (17 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Health and Science
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 2 Nov 26 75
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.curo.you/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.curo.you | CN=YR1,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | 50bc54079a51ea59a7b42c6d48124d0d2e1 |
| SANs: *.curo.you, curo.you | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.curo.you. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| you. | present | 41656 | 8 | Verified |
| curo.you. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.curo.you/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.curo.you/mcp | HTTPS enforced | 308 | https://mcp.curo.you/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
build_cart Build cart ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Products to add to the cart. |
No output schema declared.
No examples provided.
get_coa Get lab reports ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Lot number from the vial label, or a product name or slug. |
No output schema declared.
No examples provided.
get_product Get product ~75
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.
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The slug field from a search_products or get_product result. |
No output schema declared.
No examples provided.
get_store_info Get store info ~57
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
peptide_research Peptide research ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| peptide | string | yes | Peptide name or slug, for example BPC-157 or tb-500. |
No output schema declared.
No examples provided.
search_products Search products ~99
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.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Peptide or product name, for example BPC-157. Leave empty to list all products. |
No output schema declared.
No examples provided.
search_research Search research ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | The next_cursor value from the previous result, to get the next page. |
| query | string | yes | Search words, for example tendon healing or BPC-157 inflammation. |
No output schema declared.
No examples provided.
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.
remote · mcp.curo.you
claude mcp add --transport http you-curo-peptide-research 'https://mcp.curo.you/mcp'
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.