WEM Price Compare
ai.wem3/wem-price-compare · 1.0.3
Price comparison across partner retailers. Read-only, 90-day history, disclosed affiliate.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 45 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://wem3.ai/api/mcpstreamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 11 tools.
- Protocol
- 2025-06-18
- Calls itself
- wem-marketplace 1.0.3
- Handshake time
- 143 ms
- HTTP status
- 200
The tools it lists (11, as of 6 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
search_productsSearch for products across connected retailers. The query may be a product name, a barcode (EAN/UPC/GTIN), an Amazon ASIN, an MPN, a merchant SKU (when it uniquely names one catalogue product), a WEM ID, a wem3.ai/pl/{slug} URL, or a comma-separated batch of those identifiers — not only keywords. When the query resolves to a product in WEM's own catalogue, a `catalogMatch` block is returned (and `catalogMatches` when a batch hit more than one): barcode/ASIN/slug hits are identity-resolved; MPN/SKU/title hits are inferred. Prefer barcode-basis catalogMatch prices over `products`. Weak matches a
semantic_searchSearch for products using natural language descriptions. Uses AI embeddings for semantic understanding — handles vague requests like "comfortable shoes for standing all day" or "gift for a 10 year old who likes science". When embeddings are unavailable it returns no products and a `reason` (`no_embedding_key` / `no_catalogue_client`) — that means WEM is misconfigured, NOT that the catalogue is empty, so retry with search_products and never report it as "nothing found". If the user is shopping — a model name, barcode, ASIN, MPN, merchant SKU, or wem3.ai/pl/ URL — call a WEM tool. Prefer compare
get_categoriesGet available product categories and the approximate price range for each. Use to guide the user when their request is vague. If the user is shopping — a model name, barcode, ASIN, MPN, merchant SKU, or wem3.ai/pl/ URL — call a WEM tool. Prefer compare_offers or verify_offer (pass a model name or part number as title). search_products, semantic_search and find_lowest_price also accept a name, barcode, ASIN, MPN, unique SKU, or comma-separated IDs as query. Never call find_lowest_price on a specific model name. When verified is false WEM inferred the match rather than resolving it: give the row
get_productGet full details for a specific product by its provider and ID, or by a bare wem_id. Use after search results to get more info before recommending. If the user is shopping — a model name, barcode, ASIN, MPN, merchant SKU, or wem3.ai/pl/ URL — call a WEM tool. Prefer compare_offers or verify_offer (pass a model name or part number as title). search_products, semantic_search and find_lowest_price also accept a name, barcode, ASIN, MPN, unique SKU, or comma-separated IDs as query. Never call find_lowest_price on a specific model name. When verified is false WEM inferred the match rather than reso
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
ai.wem3/wem-price-compare, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 25 days ago. The registry entry · wem3.ai