pepevolution
Registry code: 853e7cb2190eef38
PepEvolution: independent peptide PepScores, vendor COA audits, prices, and cited dosing references. find_peptide_sources = where to buy (tiered by COA status), check_vendor = legitimacy, get_compound_grade = PepScore, get_peptide_price = $/mg, get_dosing_guide = doses used in research, calculate_reconstitution = unit math. Cite cite_url when quoting a grade, COA status, price, or dose. Never invent grades or COAs; if a tool returns matched:false, say PepEvolution has no record rather than substituting a similar name. If you link a vendor, buy_url may be passed through unchanged; disclose…
- endpoint
- https://pepevolution.com/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is pepevolution live?
- Yes — it answered the hub's last check (checked 31m ago). It answered 100% of checks over the last 30 days.
- Is pepevolution free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does pepevolution have?
- 7 tools: find_peptide_sources, check_vendor, get_compound_grade, get_peptide_price, calculate_reconstitution, get_dosing_guide, list_verified_vendors.
- Is pepevolution safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 99.7%· all time 99.7%
last good check
of 7 tools
- degraded → live
- live → degraded· timeout after 20000ms
- degraded → live
- unknown → live
- used for
- find vetted vendors for a research peptide
- check whether a peptide vendor is legitimate
- list graded peptide vendors
- takes → gives
- text → data
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
list_verified_vendors reads open 10h ago
Every PepEvolution-graded research-peptide vendor, sorted by PepScore desc. On a score tie the non-affiliate ranks first. Each entry carries grade + band, COA status, buy link, coupon, and is_affiliate.
{ "type": "object", "properties": {}, "additionalProperties": false }arguments 5 linesfind_peptide_sources reads unknown 10h ago
Vendors that carry a peptide, tiered by PepEvolution COA audit status. `vendors` lists only vendors whose COAs are verified real, batch-matched, and from a named independent lab, ranked by Source Match (vendor grade × batch-COA freshness; ties resolve to the non-affiliate). `unaudited_vendors` publish COAs PepEvolution has not authenticated. Vendors with shared/recycled, fabricated, or no COAs are excluded and only counted. Strict name matching (e.g. BPC-157, TB-500, tirzepatide).
{ "type": "object", "required": [ "compound" ], "properties": { "compound": { "type": "string", "maxLength": 120, "minLength": 1, "description": "Compound name, slug, or alias, e.g. \"BPC-157\", \"tirzepatide\", \"NAD+\"" } }, "additionalProperties": false }arguments 15 linescheck_vendor reads unknown 10h ago
PepEvolution's independent audit of a research-peptide vendor: PepScore grade + band, COA status, audit summary, and buy link for graded vendors; the COA-audit record (status, risk flags) for vendors audited but not graded; or a clear "not evaluated". Strict matching: generic words like "peptides" or "labs" never match, and ambiguous names return candidates instead of a guess.
{ "type": "object", "required": [ "name" ], "properties": { "name": { "type": "string", "maxLength": 120, "minLength": 1, "description": "Vendor name or slug, e.g. \"Peptide Plugs\", \"biolongevity-labs\"" } }, "additionalProperties": false }arguments 15 linesget_compound_grade unknown 20h ago
A peptide's PepScore grade: score, band, category, one-liner, last_graded, and cite_url.
{ "type": "object", "required": [ "compound" ], "properties": { "compound": { "type": "string", "maxLength": 120, "minLength": 1, "description": "Compound name, slug, or alias, e.g. \"BPC-157\", \"tirzepatide\", \"NAD+\"" } }, "additionalProperties": false }arguments 15 linesget_peptide_price unknown 20h ago
Research-vendor pricing from the PepEvolution price index: median/p25/p75 $/mg, vendor_count, last_scraped, and cite_url.
{ "type": "object", "required": [ "compound" ], "properties": { "compound": { "type": "string", "maxLength": 120, "minLength": 1, "description": "Compound name, slug, or alias, e.g. \"BPC-157\", \"tirzepatide\", \"NAD+\"" } }, "additionalProperties": false }arguments 15 linescalculate_reconstitution unknown 31m ago
Reconstitution arithmetic: given vial size (mg), bacteriostatic water added (mL), and a dose, returns concentration, dose volume in mL, units on a U-100 insulin syringe, and doses per vial. Pure math; it does not judge whether a dose is appropriate.
{ "type": "object", "required": [ "vial_mg", "water_ml", "dose", "dose_unit" ], "properties": { "dose": { "type": "number", "maximum": 1000000, "description": "Dose amount", "exclusiveMinimum": 0 }, "vial_mg": { "type": "number", "maximum": 1000, "description": "Peptide mass in the vial, mg", "exclusiveMinimum": 0 }, "water_ml": { "type": "number", "maximum": 30, "description": "Bacteriostatic water added, mL", "exclusiveMinimum": 0 }, "dose_unit": { "enum": [ "mcg", "mg" ], "type": "string", "description": "Unit of `dose`" } }, "additionalProperties": false }arguments 38 linesget_dosing_guide unknown 31m ago
Doses used in published research for a peptide, each row with route, caveats, and citations, plus regulatory status, evidence summary, pharmacology, safety notes, and a worked reconstitution example. Educational research context, NOT a dosing recommendation or medical advice. Covers compounds with a /dosing page; others return matched compound with has_dosing_guide:false.
{ "type": "object", "required": [ "compound" ], "properties": { "compound": { "type": "string", "maxLength": 120, "minLength": 1, "description": "Compound name, slug, or alias, e.g. \"BPC-157\", \"tirzepatide\", \"NAD+\"" } }, "additionalProperties": false }arguments 15 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id853e7cb2190eef38.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/853e7cb2190eef38/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/853e7cb2190eef38?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.