SoldFetch vs Ebid
A side-by-side look at the SoldFetch and Ebid MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
S
SoldFetchE-CommerceSearch eBay sold and active listings, browse categories, and retrieve item details.47FairAuth: api key requiredVerdict: choose SoldFetch for e-commerce work; choose Ebid for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
SChoose SoldFetch when
- You need dedicated capabilities in the E-Commerce domain.
- Its auth model fits you: API key required.
- You have the keys it needs:
SOLDFETCH_API_KEY. - You want tools like
search_ebay_sold, search_ebay_category, get_ebay_item.
Choose Ebid when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | S SoldFetch | |
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 47/100 · Fair | 28/100 · Emerging |
| Install command | Not confirmed yet | Confirmed |
| Transport | — | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | SOLDFETCH_API_KEY | None listed |
| Verified owner | Community listing |
Tools & capabilities
SoldFetch tools 3
search_ebay_soldSold or active listing searchsearch_ebay_categoryCategory listingsget_ebay_itemPublic item details
Ebid tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
SoldFetch
No confirmed install command for SoldFetch yet — follow the setup steps linked from its listing page rather than a guessed package name.
Ebid
{
"mcpServers": {
"ebid": {
"command": "npx",
"args": [
"-y",
"@pipeworx/mcp-ebid"
]
}
}
}
Frequently asked questions
SoldFetch is categorized under E-Commerce and uses an install path we have not confirmed yet. Ebid belongs to E-Commerce and uses a local stdio subprocess. Pick SoldFetch for e-commerce work and Ebid for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. SoldFetch has no confirmed install command yet — follow its own setup instructions.
SoldFetch has no declared pricing — check the project's own site. Auth: api key required. Ebid has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add soldfetch and ebid as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, SoldFetch has a quality signal of 47/100 (Fair) with 0 views, 0 installs and 0 GitHub stars. Ebid has 28/100 (Emerging) with 0 views, 0 installs and 0 GitHub stars.