Ebay MCP server

Created By
CooKey-Monstera year ago
Overview

what is Ebay MCP Server?

Ebay MCP Server is a simple server that allows users to fetch auctions from Ebay.com using the official MCP Python SDK for protocol communication and server interactions.

how to use Ebay MCP Server?

To use the Ebay MCP Server, install the required UV package, set up your environment variables with your Ebay client ID and secret, and then use the provided tool to scan for auctions based on your search queries.

key features of Ebay MCP Server?

  • Fetch auctions from Ebay.com using specific queries.
  • Utilizes the official MCP Python SDK for seamless integration.
  • Provides a simple command-line interface for auction searches.

use cases of Ebay MCP Server?

  1. Finding specific auctions for collectibles like comics or toys.
  2. Automating the process of searching for items on Ebay.
  3. Integrating auction data into other applications or services.

FAQ from Ebay MCP Server?

  • What do I need to run the Ebay MCP Server?

You need to install the UV package and set your Ebay API credentials.

  • Can I customize the search queries?

Yes! You can specify any search query you want when using the list_auction tool.

  • Is there a limit to the number of auctions I can fetch?

You can specify the amount of results you want to retrieve, with a default of 0.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
CooKey-Monster
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

8 hours ago