tools.schemasevery tool has an object input schema
pass
tools.annotations8 of 8 tools declare readOnlyHint or destructiveHint
pass
tools.directory_hintsevery tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
pass
tools.token_costabout 1,300 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump
stabilityn/a · weight 15
n/a
stability.changes, stability.rug_pulltool history recorded for 5 of the 7 days needed
dependenciesn/a · weight 15
n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvabledeps.dev does not know [email protected]
8 tools, about 1,300 tokens to load them all · tool set 4be0295e7084 · tools last changed 2026-11-06 · checked 2026-11-07 18:35 UTC
Tool changes
use_and_doseadded
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.
get_coachangeddescription
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 · 91% of words in common
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.
Search stored PepBank findings. Read sources and credit with each result.
after · 14% of words in common
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.
Read a PepBank peptide summary, main findings, sources, and credit.
after · 14% of words in common
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.
get_store_infochangeddescriptionmeaning changed
before
Read shipping, returns, contact, and research-use policies.
after · 24% of words in common
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.
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.
Build a cart link from product IDs and quantities. The customer checks out and pays on curo.you.
after · 30% of words in common
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.
Read product variants, prices, stock, and lot reports.
after · 16% of words in common
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.
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.
Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.
Dependencies
[email protected]npmthis version is not known to the dependency resolver
Dependency graphs from deps.dev; advisories from OSV.dev, including the GitHub Advisory Database and the PyPI Advisory Database; all CC BY 4.0. The graph is what a clean install of this version resolves today; nothing was installed or run. How it is checked.
Endpoints
remote
auth
reachable
uptime 30d
p50
protocol
last ok
https://mcp.curo.you/mcpstreamable-http
none
yes
100%
457 ms
2026-07-28
2026-11-07
package
registry
version
runtime
secrets
curo-peptides
npm
1.0.2
–
Tools (8)
build_cartread-only
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_coaread-only
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_productread-only
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_inforead-only
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_researchread-only
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_productsread-only
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_researchread-only
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_doseread-only
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.