Curo Peptide Research MCP
Related Servers
Alternatives to Curo Peptide Research MCP
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to search and retrieve structured peptide research profiles with cited, tier-labelled evidence, safety and regulatory status, and to compare two or three peptides side by side without ranking. Also provides research article and FAQ search, category and trend lookups, plus unit conversion, solution concentration, blend and cost-per-amount calculators, all read-only and anonymous.MIT
- AlicenseNot gradedqualityBmaintenanceEnables searching peptide listings and vendors by facets such as price per mg, lab testing, and contact details, plus retrieving individual vendor and peptide records and listing peptides.14 npmMIT

Hormonaly MCP Serverofficial
FlicenseNot gradedqualityDmaintenanceEnables AI agents to access 24 clinical tools for evidence synthesis, protocol lookup, and decision support in peptide, hormone, and longevity medicine.2-- AlicenseBqualityBmaintenanceEnables AI assistants to search and read the full Ray Peat corpus and WikiPeatia wiki, including articles, books, interviews, newsletters, and forum posts, with full-text, semantic, and LLM-powered Q&A tools, plus access to Ray Peat's original articles.32MIT
- FlicenseNot gradedqualityDmaintenanceEnables AI agents to browse product catalogs, search products with filters, and initiate checkouts, generating order summaries and checkout URLs.-
- AlicenseAqualityCmaintenanceEnables AI assistants to answer customer questions from a shop's own product catalog, FAQs, and policy documents, with read-only access and cited answers.5MIT
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.