My-Pepts

com.my-peptsPublished by my-pepts.comOfficial publisherv1.0.0Updated Nov 7, 2026

Run your My-Pepts research peptide store: products, orders, stock, shipping and settings.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server for running a My-Pepts research peptide store: products, orders, stock, shipping and settings.

What you can do
  • Manage the store's product catalog.
  • Handle customer orders.
  • Track and adjust stock levels.
  • Manage shipping details.
  • Change store settings.
  • No individual tools are documented, so the exact actions available are not specified.
When to use it
Useful if you operate a My-Pepts research peptide store and want an assistant to help with day-to-day store administration such as products, orders, stock and shipping.
Requirements
A remote endpoint at my-pepts.com reached over streamable HTTP. OAuth authentication is required, so you need a My-Pepts account authorized for the store. No environment variables or headers are declared.
Before you install
The server can change store data, including products, orders, stock, shipping and settings, so review actions before they are applied. It is a commercial storefront for research peptides; check that purchasing and handling comply with the rules that apply to you. Access is granted through OAuth to your store account.

Installation

In SourceWeft

  1. Open My-Pepts in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.my-pepts%2Fstore/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "my-pepts": {
      "type": "http",
      "url": "https://my-pepts.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestNov 7, 2026

Score

83% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.