mcpbeat Sign in

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) MCP Server

not responding

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) is listed as active in the registry but did not answer our last check. 910 installs a week from npm. It exposes 7 tools. Last commit 6 Nov 2026.

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

Installs per day peak 422 · avg 14
a month agotoday
Uptime history 6 days of history · worst day 0%
6 days agonow
0.0%
Uptime 24h
0 of 91 checks
7
Tools
read from the server
58 ms
Response time
average over 24h
910
Installs / week
npm and PyPI

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) does not always answer

Over the last week it answered 7.0% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add peptide-research --transport http https://mcp.curo.you/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mcp.curo.you/mcp
~/.codex/config.toml
[mcp_servers.peptide-research]
url = "https://mcp.curo.you/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "peptide-research": {
      "url": "https://mcp.curo.you/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "peptide-research": {
      "type": "http",
      "url": "https://mcp.curo.you/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

build
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.
coa
get_coa
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.
peptide
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.
product
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.
products
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.
research
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.
store
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.curo.you/mcp streamable-http answering 58 ms 11 min ago

Alternatives to Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs)

same job, measured the same way
Loomaly
by loomaly

One MCP for all your SEO: rankings, AI search, fixes & reports. Fixed in code, proven in numbers.

answering
Pentest Tools
by pentest-tools

MCP server for Pentest-Tools.com: run scans, manage findings and reports via your preffered LLM.

answering
Context Memo
by contextmemo

AI visibility reports, prompt results, memos, and landing pages for your Context Memo brands.

answering
Liftaven
by liftaven

MCP connector for Liftaven SEO research, connected search reports and reviewed website proposals.

54 installs/wk answering
Hi, Moose
by himoose

AEO and SEO for your brand: content briefs, drafts, audits, and AI search visibility reports.

answering
XERJ
by xerj-org

The search engine for AI agents: cited answers from your local code, docs, specs and logs.

local only
mcpprobe
by mcpprobe

Read-only MCP security data: check catalogue, public scan status and your own scan reports.

answering
PulseLake
by pulselake

AI-native market research: research studies, persona audience studies, analysis, reports and media

answering

Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) — questions

Answers built from our own checks of this server.

What can Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) do?
It exposes 7 tools, read directly from the server on our last check. Among them: build_cart, get_coa, get_product, get_store_info, peptide_research, search_products and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 0 of 91 checks got a reply (0.0%), average response time 58 ms. The bar chart above shows every period we have measured.
The registry lists Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs)?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) need an API key?
No. Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How many people use Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs)?
The npm package curo-peptides was installed 910 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is Curo Peptide Research MCP: PepBank Studies, Peptide Lookup and Lab Reports (COAs) open source?
The code is open source: it is published under the MIT licence, written in JavaScript and 0 stars on GitHub. The licence covers the code in the repository, not the hosted service at mcp.curo.you, which runs on its operator's own terms.