eCommerce
peptidesdirect.io
Provides product search, details, lab reports, and shipping rates for the PeptidesDirect research-peptide catalogue.
ENDPOINT 1
https://peptidesdirect.io/mcp
MCP server metadata
- Name
- peptidesdirect-catalog
- Version
- 1.0.0
Known tools 8
search_productsSearch the PeptidesDirect research-peptide catalogue by name/category, with EUR prices and live stock.
Inferred read-onlyget_productFull detail for one PeptidesDirect product by slug: variants, prices, stock, lab reports, FAQs and full description as Markdown.
Inferred read-onlyget_lab_reportsThird-party lab reports (Certificates of Analysis) for a PeptidesDirect product, by slug or by the code printed on a vial label.
Inferred read-onlyget_shipping_ratesFlat shipping rates and free-shipping thresholds, optionally for one country.
Inferred read-onlyget_pageFetch any public peptidesdirect.io page as Markdown, when a Markdown rendering is available for it.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.peptidesdirect-catalog]
url = "https://peptidesdirect.io/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"peptidesdirect-catalog": {
"type": "http",
"url": "https://peptidesdirect.io/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: peptidesdirect-catalog
Remote MCP URL: https://peptidesdirect.io/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"peptidesdirect-catalog": {
"url": "https://peptidesdirect.io/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"peptidesdirect-catalog": {
"type": "http",
"url": "https://peptidesdirect.io/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "peptidesdirect-catalog",
"transport": "streamable-http",
"url": "https://peptidesdirect.io/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 2
https://peptidesdirect.io/mcp/account
Known tools 0
No tool metadata was available in the registry cache.
CONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.peptidesdirect-io]
url = "https://peptidesdirect.io/mcp/account"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Code
.mcp.json
{
"mcpServers": {
"peptidesdirect-io": {
"type": "http",
"url": "https://peptidesdirect.io/mcp/account",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Claude Desktop
Settings → Connectors → Add custom connector
Name: peptidesdirect-io
Remote MCP URL: https://peptidesdirect.io/mcp/account
Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"peptidesdirect-io": {
"url": "https://peptidesdirect.io/mcp/account",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Visual Studio Code
.vscode/mcp.json
{
"servers": {
"peptidesdirect-io": {
"type": "http",
"url": "https://peptidesdirect.io/mcp/account",
"headers": {
"Authorization": "Bearer ${input:mcp-token}"
}
}
},
"inputs": [
{
"type": "promptString",
"id": "mcp-token",
"description": "peptidesdirect-io bearer token",
"password": true
}
]
}
Authentication is required. Replace the placeholder locally and never commit a secret.
Generic MCP
Client-specific MCP configuration
{
"name": "peptidesdirect-io",
"transport": "streamable-http",
"url": "https://peptidesdirect.io/mcp/account",
"headers": {
"Authorization": "Bearer YOUR_BEARER_TOKEN"
}
}
Authentication is required. Replace the placeholder locally and never commit a secret.
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
ENDPOINT 3
https://peptidesdirect.io/ucp/mcp
MCP server metadata
- Name
- peptidesdirect-ucp-catalog
- Version
- 1.0.0
Known tools 3
search_catalogUCP Catalog Search: free-text search over the PeptidesDirect research-peptide catalogue.
Inferred read-onlylookup_catalogUCP Catalog Lookup: batch-resolve product slugs and/or variant SKUs (catalog.ids) to full product and variant data.
Inferred read-onlyget_productUCP Catalog Lookup (single-product retrieval): full detail for one PeptidesDirect product, by product slug or variant SKU (catalog.id).
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.peptidesdirect-ucp-catalog]
url = "https://peptidesdirect.io/ucp/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"peptidesdirect-ucp-catalog": {
"type": "http",
"url": "https://peptidesdirect.io/ucp/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: peptidesdirect-ucp-catalog
Remote MCP URL: https://peptidesdirect.io/ucp/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"peptidesdirect-ucp-catalog": {
"url": "https://peptidesdirect.io/ucp/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"peptidesdirect-ucp-catalog": {
"type": "http",
"url": "https://peptidesdirect.io/ucp/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "peptidesdirect-ucp-catalog",
"transport": "streamable-http",
"url": "https://peptidesdirect.io/ucp/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Trust Data Available
BuiltWith Trust API v2 evidence for peptidesdirect.io was fetched 2026-08-24T08:05:25.640Z.
peptidesdirect.io is assessed as Trusted: Domain runs a meaningful technology spend, consistent with a real business.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.