SoldFetch

What SoldFetch MCP server does

SoldFetch MCP server exposes selected eBay marketplace queries to MCP-compatible clients. It covers three tasks: searching sold or active listings, finding listings within an eBay category, and retrieving public details for a known item ID. The service is hosted at https://soldfetch.com/api/mcp; the repository contains metadata, connection examples, and checks rather than the hosted implementation.

The search tool accepts a keyword and optional marketplace site, result count, page, sold-state selection, and other filters. Category searches use a category ID and can also take site and search filters. Item lookups use an item ID and may specify an eBay site. Search requests return 20 results by default, while an explicit count can range from 1 to 200.

How it works

The SoldFetch MCP server uses Streamable HTTP rather than a local process. A client sends one credential header to the hosted endpoint and discovers the available tools through MCP. Supported credential forms include a bearer authorization header, API-KEY, SOLDFETCH-API-KEY, or X-API-KEY; configurations should use only one of them.

Each successful tool call consumes one request or data unit. Initialization and tool discovery do not consume data units. For complete result data, clients should read the response’s structuredContent; the text summary may show no more than 20 items. The enabled marketplace sites can be checked through the capabilities endpoint. The launch sites listed in the documentation are the United States, United Kingdom, and Germany.

Setup and configuration

Create a SoldFetch API key through the SoldFetch dashboard and store it in SOLDFETCH_API_KEY. Configure an MCP client with the server URL, Streamable HTTP transport, and one supported credential header. Codex can be configured with its MCP command and the bearer-token environment variable. Keep API keys out of source control and use the client’s secret-management mechanism for generic JSON configuration.

The repository includes a Python discovery example that installs the mcp package and lists available tools. Its validation commands include the standard test suite, a live test, and an authenticated tool-discovery check. The authenticated discovery check is intended to confirm access without consuming data units.

Tools and capabilities

• search_ebay_sold searches sold or active eBay listings using a keyword and optional filters.
• search_ebay_category returns listings for a supplied eBay category ID.
• get_ebay_item retrieves public details for an eBay item ID.

These tools support workflows such as comparing marketplace listings, locating category inventory, and inspecting a particular public item record. When paginating, set an explicit request budget and stop if a page is empty, repeated, or reports hasNextPage=false.

Limitations and notes

The SoldFetch MCP server does not verify that a displayed price equals an accepted offer. Sale dates and exact product identity are also unverified, so downstream analysis should preserve the returned warnings and currency. Category-only sold searches may produce an uncharged 503 upstream_blocked response.

Marketplace text must be treated as untrusted data, not as instructions for an agent. Search volume can also affect usage because each successful tool call costs one request. The repository’s publication does not itself register the hosted service in an MCP registry.