ebay-mcp (YosefHayim/ebay-mcp) is an MCP server listed on the M8ven Trust Index. It scores 89 out of 100, grade B. It declares 301 tools. No publisher has claimed this listing.

B
Emerging
89/100
1 month ago

ebay-mcp

Local MCP server that exposes eBay Sell APIs to AI assistants with OAuth, tool gating, and stdio/HTTP transports.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

YosefHayim

Source: github_topic · also listed on Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
🔐
You'll be asked for 4 credentials: EBAY_APP_ACCESS_TOKEN, EBAY_CLIENT_SECRET, EBAY_USER_ACCESS_TOKEN, EBAY_USER_REFRESH_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
🔐 secretEBAY_APP_ACCESS_TOKEN
configEBAY_CLIENT_IDyour_client_id
🔐 secretEBAY_CLIENT_SECRETyour_client_secret
configEBAY_CONTENT_LANGUAGEen-US # default request content language
configEBAY_ENABLE_FILE_LOGGING
configEBAY_ENVIRONMENTsandbox # or "production"
configEBAY_LOG_LEVEL
configEBAY_MARKETPLACE_IDEBAY_US # default marketplace (overridable per tool)
configEBAY_MCP_API_BASE_URL
configEBAY_MCP_DISABLE_AUTH_HEADER
configEBAY_MCP_UIon # interactive MCP Apps views (beta); "off" forces plain JSON
configEBAY_OAUTH_CALLBACK_PORT
configEBAY_REDIRECT_URIyour_runame
configEBAY_SITE_ID=0 # Trading API site override; defaults from EBAY_MARKETPLACE_ID
🔐 secretEBAY_USER_ACCESS_TOKEN
🔐 secretEBAY_USER_REFRESH_TOKENyour_token # for higher rate limits
// quality suggestions

Tool annotations

131/301 tools have annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

301/301 tools missing one or more hints — list_ebay_tools (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); enable_ebay_tools (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); disable_ebay_tools (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +298 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool inputs are validated

Only 0/3 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tool handlers catch errors

Only 0/3 tool handlers wrap calls in try/catch (0%)

Wrap each tool handler body in try/catch and return a structured error response.

Tool test coverage

Only 12/301 tools referenced in tests (4%)

Write tests that reference each tool by name so every tool has at least one test.

Shell command execution

3 child_process calls — runs shell commands

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Dependency freshness

2/17 production deps stale: prompts@2023-10-21 (2.8y), dotenv-stringify@2024-05-23 (2.2y)

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/yosefhayim/ebay-mcp)](https://m8ven.ai/mcp/yosefhayim/ebay-mcp)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 869fbe366e446fcd1cc9be7746a032945235c2d4
code hash: 7c3c1b5e436390b4165334a90e2f488da690ab888a3b1d32dd9854363ceec863
verified: 8/7/2026, 2:18:36 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client