Ebid MCP server

@pipeworx/ebid

eBid MCP — listings, ended-listing search, bid history and categories from the eBid.net online marketplace and auction site, via the official eBid Trading API v2. eBid runs 20+ country sites (us, uk, ca, au, de, fr, …); it is a small marketplace next to eBay, so treat it as a secondary listings/price source.

Part of Pipeworx — an MCP gateway connecting AI agents to 1576+ live data sources.

Tools

• ebidsearch(keyword?, site?, categoryid?, minprice?, maxprice?, condition?, buynowonly?, closed?, username?, country?, search_descriptions?, sort?, start?, rows?) — search live listings, or ended ones with closed: true (where realized sale prices live). Max 75 rows/page (API cap).
• ebidlisting(listingid, site?, shipto?) — one listing in full, with shipping calculated to shipto.
• ebidlistingbids(listing_id, site?) — bid history; on an ended auction the highest bid is the realized price.
• ebidcategories(categoryid?, site?) — category tree with per-category item counts.

Auth

commands — is rejected upstream without an AppId/AppKey pair (error 003). Register free at the eBid developer portal , then pass both as one argument: _apiKey: "AppId:AppKey".

• BYO only: every eBid API command — including the documented no-login read

application's AppId and AppKey at signup but activates the application separately, so a freshly minted pair authenticates and still answers nothing: error 116 application is not active on every command. Pipeworx holds such a pair (fleet #1284, minted 2026-09-07) and the pack therefore stays BYO-only — PLATFORMEBIDKEY is deliberately NOT declared until a live call succeeds, because a declared key that cannot answer makes the router keep choosing a pack that is guaranteed to fail.

• Registering is not the same as being able to call. eBid issues an

Telling the four credential failures apart

eBid reports all of them at HTTP 200, and three share code 116. Probed live 2026-09-07 against api.ebid.net/trading:

The pack maps each to its own message. Only the first one tells the caller to pass a key — the other three mean they already did, and the fix is elsewhere.

Data sources

POST with the command in the body. Docs: .

• https://api.ebid.net/trading — eBid Trading API v2; single endpoint, JSON

upstream code and description rather than the status line.

• Failures come back as HTTP 200 with an Error array; the pack surfaces the

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "ebid": {
      "url": "https://gateway.pipeworx.io/ebid/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/ebid/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, search_within, remember/recall and the rest of the gateway-wide set. So the tool count you see is larger than this table: a single-pack endpoint currently lists roughly 30 shared tools alongside the pack's own. The connection's initialize response states its exact scope, and is the authoritative answer for a given day.

Shortened. The full README is on GitHub.