# search-peptides (remote · search.peptides.pit.world)

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

- Trust score: 72/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `search.peptides.pit.world`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-profullstack-search-peptides/search.md), [page](https://verifymcp.io/servers/com-profullstack-search-peptides/search)

## Channel facts

- Endpoint: `https://search.peptides.pit.world/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 88/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 63% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http com-profullstack-search-peptides 'https://search.peptides.pit.world/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-profullstack-search-peptides": {
      "url": "https://search.peptides.pit.world/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-profullstack-search-peptides": {
      "type": "http",
      "url": "https://search.peptides.pit.world/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-profullstack-search-peptides]
url = "https://search.peptides.pit.world/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-profullstack-search-peptides": {
      "type": "remote",
      "url": "https://search.peptides.pit.world/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-profullstack-search-peptides --url 'https://search.peptides.pit.world/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-profullstack-search-peptides:
    url: "https://search.peptides.pit.world/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-profullstack-search-peptides": {
      "Transport": "http",
      "Url": "https://search.peptides.pit.world/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-profullstack-search-peptides -t streamable-http -u 'https://search.peptides.pit.world/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-profullstack-search-peptides": {
      "type": "http",
      "url": "https://search.peptides.pit.world/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 72, +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.

### 2026-11-19 (score 71, +15)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Endpoint reachability: unreachable → reachable
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.23

### 2026-11-18 (score 56, −14)

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

### 2026-11-16 (score 70, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] Stability: 0.10 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] HSTS header: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-11-15 (score 70, +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.

### 2026-11-13 (score 69, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 68, +64)

- [security improvement] Authorization: unverified → partial
- [security improvement] Injection markers: unverified → pass
- [security improvement] TLS certificate: unverified → pass
- [security improvement] HSTS header: unverified → pass
- [security improvement] Transport: fail → pass
- [security] First check of Judged manipulation: pass
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] 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

### 2026-11-11 (score 4)

First indexed and scored.

## MCP tools (7)

### `search_listings` (~439 tokens)

Search Peptide Listings

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.

Input parameters:

- `blend` (boolean): Blends only.
- `coupon` (boolean)
- `form` (string)
- `in_stock` (boolean)
- `limit` (integer): Listings to return (default 25, max 200).
- `max_mg` (number): Maximum mg per vial.
- `max_per_mg` (number): Maximum USD per mg.
- `max_price` (number): Maximum listing price in USD.
- `min_mg` (number): Minimum mg per vial.
- `min_price` (number)
- `min_score` (number): Minimum Finnrick rating (0-100, as Finnrick publishes it).
- `min_verification` (number): Minimum verification score (0-100, computed from checkable evidence; see get_rules). Unscored vendors never match.
- `ordering` (string)
- `page` (integer)
- `passed` (boolean): Only vendors that passed a lab test for this peptide.
- `payment` (string)
- `peptide` (string): Peptide slug or name, e.g. "bpc-157", "Tirzepatide", "BPC-157 + TB-500".
- `q` (string): Words to match in the product name, peptide or vendor.
- `ships_from` (string): ISO-3166 alpha-2 (US, CN, HK, CA, GB, AU…) or EU.
- `single` (boolean): Single peptides only (no blends).
- `sort` (string)
- `tested` (boolean): Only vendors with independent lab tests.
- `text` (string): Free text, e.g. "retatrutide lab tested under $1/mg in stock". Parsed into the filters below.
- `vendor` (string): Vendor slug.

### `search_vendors` (~265 tokens)

Search Peptide Vendors

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.

Input parameters:

- `contact` (string)
- `coupon` (boolean)
- `limit` (integer): Vendors to return (default 25).
- `min_pass` (number): Minimum lab pass rate in percent.
- `min_score` (number): Minimum Finnrick rating (0-100, as Finnrick publishes it).
- `min_verification` (number): Minimum verification score (0-100, computed from checkable evidence; see get_rules). Unscored vendors never match.
- `ordering` (string)
- `payment` (string)
- `peptide` (string): Only vendors that list this peptide (slug).
- `priced` (boolean): Only vendors with published prices.
- `q` (string): Vendor name words.
- `ships_from` (string): ISO-3166 alpha-2 (US, CN, HK, CA, GB, AU…) or EU.
- `sort` (string)
- `tested` (boolean)

### `get_vendor` (~66 tokens)

Get Vendor

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.

Input parameters:

- `slug` (string, required)

### `get_rules` (~65 tokens)

Get Scoring Rules

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.

Input parameters:

- `limit` (integer): Recent score changes to return (default 20).

### `get_peptide` (~37 tokens)

Get Peptide

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

Input parameters:

- `slug` (string, required)

### `list_peptides` (~29 tokens)

List Peptides

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

### `sponsor_vendor` (~78 tokens)

Sponsor a Vendor

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.

Input parameters:

- `email` (string, required): Email for the receipt.
- `vendor` (string, required): Vendor slug.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-profullstack-search-peptides/search#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 72
- 2026-11-19: 71
- 2026-11-18: 56
- 2026-11-17: 70
- 2026-11-16: 70
- 2026-11-15: 70
- 2026-11-14: 69
- 2026-11-13: 69
- 2026-11-12: 68
- 2026-11-11: 4

## 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.

## Links

- Remote endpoint: https://search.peptides.pit.world/mcp
- Website: https://search.peptides.pit.world/
- Changelog RSS feed: https://verifymcp.io/servers/com-profullstack-search-peptides/search.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-profullstack-search-peptides/search/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-profullstack-search-peptides/search.json
- HTML version of this page: https://verifymcp.io/servers/com-profullstack-search-peptides/search
