Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

search-peptides

REMOTE · SEARCH.PEPTIDES.PIT.WORLD

Peptide vendor/listing search (search.peptides.pit.world)

+3 this week 72 Trust /100

Last scanned (21 hours ago)

Scores higher than 57% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Health and Science

Trust breakdown (7 categories)

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 → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • 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
Schema Quality & AI Usability60
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1096 tokens (~156/item across 7 items; 7 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 Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage88
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 63% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +15
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • MCP protocol: unverified → fail ▼ functional
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.23 ▲ functional
  • 18 Nov 26 −14

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 16 Nov 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: 0.10 → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • TLS certificate: pass → unverified ▼ security
    • HSTS header: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 15 Nov 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.

  • 13 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 +64
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • TLS certificate: unverified → pass ▲ security
    • HSTS header: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • First check of Judged manipulation: pass security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → 100 ▲ functional
    • First check of Schema quality: fail functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: good functional
    • First check of Tool coverage: 63 functional
  • 11 Nov 26 4

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://search.peptides.pit.world/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=search.peptides.pit.world CN=YE2,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA384 5f21a2cc613ac88995077e4016aae1d6269
SANs: bbs.search.peptides.pit.world, search.peptides.pit.world, social.search.peptides.pit.world
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of search.peptides.pit.world. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
world. DS published 422 8 Verified
pit.world. No DS 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
content-security-policy default-src 'self'; script-src 'self' https://crawlproof.com https://cdn.jsdelivr.net; style-src 'self'; img-src 'self' data: https:; connect-src 'self' https://crawlproof.com; frame-src https://crawlproof.com; form-action 'self' https://coinpayportal.com; base-uri 'none'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://search.peptides.pit.world/mcp Verified 200
http (plaintext) http://search.peptides.pit.world/mcp HTTPS enforced 301 https://search.peptides.pit.world/mcp
MCP tools · 7 exposed · ~979 tokens

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. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_peptide ~37

One peptide: how many vendors list it, cheapest USD per mg, and independent lab results by vendor.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

get_rules ~65

How the verification score is computed: what counts as a verifiable certificate, each component with its weight and rule, the scored/insufficient/unscored thresholds, and the latest score changes across vendors.

NameTypeReqDescription
limitinteger–Recent score changes to return (default 20).

No output schema declared.

No examples provided.

get_vendor ~66

Everything about one vendor: verification score with every component (weight, points, evidence), score history, independent tests with lab, batch and public record link, contact card, every listing with price per mg, payment, shipping, coupons, how to order.

NameTypeReqDescription
slugstringyes–

No output schema declared.

No examples provided.

list_peptides ~29

Every peptide in the register with vendor and listing counts, lowest USD per mg and lab pass counts.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

search_listings ~439

Search every research-peptide listing (vendor × peptide × size) and rank by USD per mg, price, vendor verification score or size. Filter by lab testing, stock, payment method, where it ships from and more. Returns listings with the vendor verification score, Finnrick rating and lab-test flags, plus facet counts.

NameTypeReqDescription
blendboolean–Blends only.
couponboolean––
formstring––
in_stockboolean––
limitinteger–Listings to return (default 25, max 200).
max_mgnumber–Maximum mg per vial.
max_per_mgnumber–Maximum USD per mg.
max_pricenumber–Maximum listing price in USD.
min_mgnumber–Minimum mg per vial.
min_pricenumber––
min_scorenumber–Minimum Finnrick rating (0-100, as Finnrick publishes it).
min_verificationnumber–Minimum verification score (0-100, computed from checkable evidence; see get_rules). Unscored vendors never match.
orderingstring––
pageinteger––
passedboolean–Only vendors that passed a lab test for this peptide.
paymentstring––
peptidestring–Peptide slug or name, e.g. "bpc-157", "Tirzepatide", "BPC-157 + TB-500".
qstring–Words to match in the product name, peptide or vendor.
ships_fromstring–ISO-3166 alpha-2 (US, CN, HK, CA, GB, AU…) or EU.
singleboolean–Single peptides only (no blends).
sortstring––
testedboolean–Only vendors with independent lab tests.
textstring–Free text, e.g. "retatrutide lab tested under $1/mg in stock". Parsed into the filters below.
vendorstring–Vendor slug.

No output schema declared.

No examples provided.

search_vendors ~265

Search peptide vendors by verification score (default order; null = insufficient data or unscored, never guessed), Finnrick rating, lab pass rate, payment, where they ship from, how to order and how to contact them (email, phone, WhatsApp, Telegram, socials). Each vendor carries a contact card.

NameTypeReqDescription
contactstring––
couponboolean––
limitinteger–Vendors to return (default 25).
min_passnumber–Minimum lab pass rate in percent.
min_scorenumber–Minimum Finnrick rating (0-100, as Finnrick publishes it).
min_verificationnumber–Minimum verification score (0-100, computed from checkable evidence; see get_rules). Unscored vendors never match.
orderingstring––
paymentstring––
peptidestring–Only vendors that list this peptide (slug).
pricedboolean–Only vendors with published prices.
qstring–Vendor name words.
ships_fromstring–ISO-3166 alpha-2 (US, CN, HK, CA, GB, AU…) or EU.
sortstring––
testedboolean––

No output schema declared.

No examples provided.

sponsor_vendor ~78

Start a sponsorship: $49 pins one vendor above matching results for 30 days, always labelled Sponsored. Returns a CoinPay hosted checkout url; the buyer opens it and pays with any coin or PayPal. Nothing is charged until they pay there.

NameTypeReqDescription
emailstringyesEmail for the receipt.
vendorstringyesVendor slug.

No output schema declared.

No examples provided.

Install

How do I install the search-peptides MCP server?

search-peptides is a hosted endpoint at https://search.peptides.pit.world/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · search.peptides.pit.world

# add to Claude Code
claude mcp add --transport http com-profullstack-search-peptides 'https://search.peptides.pit.world/mcp'
Common questions

What is the search-peptides MCP server?

search-peptides is an MCP server listed in the public MCP registry as com.profullstack/search-peptides. Peptide vendor/listing search (search.peptides.pit.world). This page covers its hosted endpoint (https://search.peptides.pit.world/mcp).

Is the search-peptides MCP server safe to use?

search-peptides scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the search-peptides MCP server expose?

search-peptides exposes 7 tools: search_listings, search_vendors, get_vendor, get_rules, get_peptide, and 2 more. Their descriptions and schemas cost roughly 979 tokens of context every time the server is loaded.

Does the search-peptides MCP server require authentication?

No. We connected to search-peptides without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the search-peptides MCP server still maintained?

search-peptides is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the search-peptides MCP server?

VerifyMCP ran 13 checks on search-peptides, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.