A
licenseA
qualityC
maintenanceEnables an LLM to search AliExpress and inspect product listings (including prices, ratings, and specs) without an API key, using direct HTTP and headless browser fallbacks to bypass anti-bot measures.
2
2
1
MIT
OneFindMe
Server Details
Search AliExpress and eBay in any language: real listings with price, rating, delivery and links.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over 22 days
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
TDQS
A3.9/5.0
Scored across 1 tool
Disambiguation5/5
With only one tool, there is no possibility of confusion or misselection among tools. Its purpose—natural-language product search across AliExpress and eBay—is clearly stated and distinct.
Naming Consistency5/5
The single tool follows a clean, predictable verb_noun convention (search_products) that would scale well if more tools were added. No inconsistent casing or vague verbs.
Tool Count3/5
One tool is thin for a product-discovery server that spans two marketplaces; search-only surfaces typically pair with detail/lookup operations. It is defensible if the scope is intentionally search-only, but borders on too narrow.
Completeness3/5
Search covers the core use case well, returning rich listing data (price, rating, orders, store, link) plus eBay results. However, there is no tool to fetch a single product's details, refine/filter results, or browse by category, leaving agents at a dead end after the initial search.
Available Tools
1 toolsearch_productsSearch AliExpress and eBay productsARead-onlyIdempotentInspect
Search AliExpress for products using the shopper's own words in any language (Hebrew, Arabic, German, Spanish, Japanese, …) — no need to know the English product name. Returns real listings with price, rating, order count, store and a link. Prices are for delivery to the given country. When eBay has matching new, fixed-price listings that ship to that country, they are returned as a separate list (ebay_results) with price, shipping cost, delivery estimate and where the item ships from, via the official eBay API. Links are affiliate links (OneFindMe may earn a commission; the price is the same for the buyer).
| Name | Required | Description | Default |
|---|---|---|---|
| query | Yes | What the shopper is looking for, in any language, e.g. "מעיל חם לפעוט" or "wireless earbuds for running". | |
| country | No | ISO 3166-1 alpha-2 code of the delivery country, e.g. US, GB, DE, IL, SA. Default US. | |
| language | No | Language of the query and of the returned titles (ISO 639-1, e.g. en, he, ar, de). Default: detected from the query script, else en. | |
| max_price | No | Maximum price in the country's currency. | |
| min_price | No | Minimum price in the country's currency. | |
| max_results | No | How many products to return (1-20). Default 8. | |
| free_shipping | No | Only products with free shipping. |
TDQS
A3.9/5.0
Behavior4/5
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
Annotations already cover safety (readOnly, idempotent, non-destructive, openWorld), but the description adds substantial extra context: the returned fields, that prices reflect delivery to the given country, that eBay results arrive as a separate ebay_results list sourced from the official API, and an affiliate-link/commission disclosure. It stops short of describing pagination or result-count behavior.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Conciseness4/5
Is the description appropriately sized, front-loaded, and free of redundancy?
It is a single dense paragraph with essentially no wasted clauses — each sentence covers a distinct fact (multilingual query, AliExpress results, eBay results, affiliate disclosure). It is a little long and could be split for front-loading, but nothing is filler.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Completeness4/5
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
With no output schema, the description carries the return-shape burden and does so well by listing listing fields for both sources. The main gap is the absence of any note on empty-result or fallback behavior when eBay has no matches.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Parameters3/5
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
Schema description coverage is 100%, so every parameter is already documented. The description only reinforces the language/country/price-for-delivery semantics, adding no syntax or format detail beyond the schema, so the baseline of 3 applies.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Purpose5/5
Does the description clearly state what the tool does and how it differs from similar tools?
It names a specific verb (search) and resource (products) plus the concrete sources (AliExpress, and conditionally eBay) and the notable capability of natural-language queries in any language. An agent knows exactly what this does without opening the schema.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Usage Guidelines3/5
Does the description explain when to use this tool, when not to, or what alternatives exist?
Usage context is implied via 'shopper's own words in any language' and 'no need to know the English product name', and it explains the condition under which eBay results appear. There is no explicit when-not-to-use guidance or named alternative, though none exists among siblings.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
1 tool update
- First observed
search_products
Related MCP Connectors
Search AliExpress with real prices, live promo codes and the true post-cashback cost.
Search AliExpress by keyword: price, discount, exact order count, rating, shipping, best sellers.
1AliExpress search results as JSON: price, discount, rating, units sold. Runs on Apify.
Products, prices and sellers from Amazon, Taobao/Tmall, AliExpress, TikTok Shop and Idealo (EU).
Related MCP Servers
datawebot MCP serverofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to search products across online shops worldwide and retrieve each seller's price, shipping total, delivery note, rating, and direct product link.3MIT- AlicenseAqualityDmaintenanceSearch eBay and get real price data, straight from an AI agent.31MIT
- AlicenseAqualityCmaintenanceEnables LLM agents to access live aliexpress.ru storefront data, including variant-specific ruble prices, order-accurate coupons, delivery quotes to Russian cities, seller info, and paginated buyer reviews with filters.4MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.