Deer Supply

supply.deerPublished by deer.supplyOfficial publisherv2.2.0Updated Nov 7, 2026

Deer Supply (Canada): GLP weight-loss pens, prices, delivery, orders and health. Sign-in required.

VerifiedStreamable HTTPWeb executableLocation & LifestyleBusiness & Commerce

Overview

AI-generated overview

Deer Supply is a remote, sign-in-only MCP endpoint for a Canadian GLP weight-loss pen service, covering prices, delivery, orders and health.

What you can do
  • No tools are listed in the manifest, so the exact actions are unknown.
  • Based on the description, an assistant could look up GLP weight-loss pen products and their prices.
  • It may also cover delivery details, orders and health-related information for the service.
  • All of this is behind a required sign-in.
When to use it
Worth considering only if you already use this Canadian GLP weight-loss pen service and want an assistant to reach its product, price, delivery or order information. Otherwise there is little evidence of what it offers.
Requirements
A remote endpoint at deer.supply reached over streamable HTTP, with OAuth sign-in required. No packages, environment variables or headers are declared.
Before you install
Sign-in is required, so the server is tied to your account with this provider; review what account and health-related data it can read before connecting. Orders or purchases may involve real payments. No tool list is published, so verify its actual capabilities first.

Installation

In SourceWeft

  1. Open Deer Supply 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/supply.deer%2Fdeer-supply/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": {
    "deer-supply": {
      "type": "http",
      "url": "https://deer.supply/api/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

2
  1. v2.2.0LatestNov 7, 2026
  2. v2.1.0Oct 16, 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.