Curo Peptide Research MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| search_productsA | 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. |
| get_productA | 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. |
| build_cartA | 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_coaA | 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. |
| get_store_infoA | 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_researchA | 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_researchA | 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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| research_peptide | Ask what the research says about one peptide. |
| lab_report | Ask for the lab report (COA) of one lot. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| store_info | Shipping, returns, contact and research-use policies. |
TDQS
Scored across 7 tools
Each tool targets a distinct resource+action, and the descriptions actively route the agent (search_products → get_product → get_coa, peptide_research vs search_research). The only real overlap is that get_product embeds per-lot COA data while get_coa fetches reports by lot number, so an agent could plausibly pick either for a testing question; the descriptions mitigate this by telling you to use get_coa when a lot number is given.
Six of seven names follow a clear verb_noun pattern (get_store_info, search_products, get_product, build_cart, get_coa, search_research). peptide_research is the lone noun-first outlier, a minor deviation that is still readable and semantically sensible.
Seven tools is well-scoped for a storefront-plus-research server: two discovery tools, two detail tools, one cart tool, one policy tool and one research lookup. Nothing looks redundant or padded, and no obvious capability is missing a tool slot.
The surface covers the full browse→inspect→verify→buy path plus policy and research lookups, with no dead ends for the stated scope (it explicitly does not place orders or take payment). Minor gaps: there is no direct lookup of a product by name without search_products, no way to list or search COAs without a lot/product, and no order-status or shipping-cost estimate.