PepEvolution Peptide Sources
REMOTE · PEPEVOLUTION.COM · SCANNED AUG 20
Find where to buy peptides from vetted, COA-tested vendors and check if a peptide vendor is legit.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 425 tokens (~141/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
remote · pepevolution.com
claude mcp add --transport http com-pepevolution-peptide-sources https://pepevolution.com/mcp
[mcp_servers.com-pepevolution-peptide-sources] url = "https://pepevolution.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-pepevolution-peptide-sources": {
"type": "remote",
"url": "https://pepevolution.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-pepevolution-peptide-sources --url https://pepevolution.com/mcp --transport streamable-http
mcp_servers:
com-pepevolution-peptide-sources:
url: "https://pepevolution.com/mcp" {
"mcpServers": {
"com-pepevolution-peptide-sources": {
"type": "http",
"url": "https://pepevolution.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 19 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Aug 26 +1
- Stability: unverified → 0.03 ▲ functional
- 16 Aug 26 64
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Aug 2026 · Probed https://pepevolution.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pepevolution.com | CN=WE1,O=Google Trust Services,C=US | 27 Jun 2026 | 25 Sept 2026 | ECDSA 256 | ECDSA-SHA256 | 1026a65ddd72e11613f5670a1c41e633 |
| SANs: pepevolution.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
DNSSEC insecure
Validation of pepevolution.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pepevolution.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://pepevolution.com/mcp | Verified | 200 | |
| http (plaintext) | http://pepevolution.com/mcp | HTTPS enforced | 301 | https://pepevolution.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability.
check_vendor ~139
Check if a research-peptide vendor is legit, a scam, or safe to buy from. Given a vendor name or slug (fuzzy, case-insensitive), returns PepEvolution's independent audit: PepScore grade + band, lab-verified COA status, a short audit summary of red/green flags, a disclosed buy link (tracked when affiliate) and any coupon, or a clear "not evaluated" result. Use for "is [vendor] legit", "[vendor] review", "[vendor] scam".
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Vendor name or slug, e.g. "Peptide Plugs", "biolongevity-labs" |
No output schema declared.
No examples provided.
find_peptide_sources ~150
Find where to buy a peptide online from vetted, third-party-tested vendors. Given a peptide or compound name (e.g. BPC-157, tirzepatide, semaglutide, retatrutide, TB-500), returns independently graded vendors ranked by lab-verified Certificate of Analysis (COA) quality, with PepScore purity grades, coupon codes, and disclosed referral purchase links. Use for "where can I buy X", "best source for X", "which peptide vendor is trusted for X". Fuzzy, case-insensitive matching.
| Name | Type | Req | Description |
|---|---|---|---|
| compound | string | yes | Compound name or slug, e.g. "BPC-157", "tirzepatide" |
No output schema declared.
No examples provided.
list_verified_vendors ~69
List every PepEvolution-graded research-peptide vendor, sorted by PepScore (desc). Each entry carries grade + band, lab-verified COA status, a disclosed buy link (tracked when affiliate), any coupon, and the affiliate disclosure. Use to compare trusted peptide vendors at a glance.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.