SafeBay

store.safebayPublished by safebay.storeOfficial publisherv1.0.0Updated Nov 8, 2026

An eBay seller's store in their AI assistant: orders, listings, buyer messages, returns.

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Overview

AI-generated overview

A remote MCP server that brings an eBay seller's store into an AI assistant, covering orders, listings, buyer messages and returns.

What you can do
  • No tools are listed in the manifest. According to the description, the server connects an assistant to an eBay seller's storefront so the seller can work with their shop data from within the assistant.
  • The areas named are orders, listings, buyer messages and returns, suggesting the assistant can review and act on seller-side store activity.
  • Specific operations, permissions and limits are not documented in the supplied material.
When to use it
Worth considering if you run an eBay store and want an assistant to help with day-to-day seller work such as orders, listings, buyer messages and returns without switching between tools.
Requirements
A remote endpoint at safebay.store using streamable HTTP. OAuth authentication is required, so you need a SafeBay account and must complete the OAuth sign-in flow. No environment variables or headers are declared.
Before you install
OAuth grants the server access to your seller store data, which likely includes orders, buyer messages and returns; review the scopes requested during sign-in. The tool list is not published, so it is unclear whether the assistant can change listings, reply to buyers or issue refunds. Buyer and order data would be handled by a third-party service.

Installation

In SourceWeft

  1. Open SafeBay 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/store.safebay%2Fsafebay/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": {
    "safebay": {
      "type": "http",
      "url": "https://safebay.store/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 8, 2026

Score

67% 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

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

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