Vinted MCP server: let your AI agent search second-hand items

#What your agent gets

The parameters are query (required), price_from and price_to, and order (relevance or lowest price first). In our check, one search read one page with 96 item cards. Each item comes with its brand, size, condition, price, the total with the buyer protection fee and the item link, so your agent can compare what you would pay, not only the listed price. The how-to page has example prompts and the full parameter list.

#Countries

Wield has one search recipe for each Vinted country site below. All seven take the same query, price range and sort parameters, and need no login. In our checks, Vinted answered server requests for all seven, so none is browser only. The terms note is the same for all seven (see Vinted's terms below).

#How a request flows

1. You ask your agent: "Find used Levi's jeans on Vinted under 40 euros, cheapest first."
2. The agent calls find_recipe, then run with vinted.de/search-items, your query, price_to: 40 and order: price_low_to_high.
3. wield-mcp passes the run through a local bridge to the Wield extension.
4. The extension sends the request from a vinted.de tab, so it carries your browser session.
5. The results go back to your agent. Nothing passes through wield.run.

#What leaves your computer

A search makes one request to the Vinted site you pick (www.vinted.de, www.vinted.fr or www.vinted.co.uk). Passwords and cookies never leave your computer. Wield logs the request on your computer only, without the body or query values. Buying and messaging stay on the Vinted site you search.

#Vinted's terms, in plain words

The robots.txt of each Vinted country site disallows ClaudeBot and sets the Content-Signal preference ai-input=no, which asks that the site's content not be used as AI input. Vinted's terms prohibit scraping. Wield runs this recipe only when you ask, in your own browser, one catalogue page per call: no bulk collection, no buying and no messaging. We have not completed a review of the terms for this recipe, so read them before you automate anything else.

#Limits and what is not working yet

• Reads the results page. Vinted's older JSON API returns 404, so the recipe reads the item cards on the results page. A change to the page layout can break it.
• The browser agent did well here. On vinted.de, Vinted did not block the browser agent in our runs. It passed 7 of 8 runs, but with a median of 136.5 seconds, against 0.9 seconds for the recipe.
• One search at a time. The recipe is meant for searches you start yourself, not for bulk collection.

#FAQ

#Which Vinted countries work?

Seven country sites have a search recipe: vinted.de (Germany), vinted.fr (France), vinted.co.uk (UK), vinted.it (Italy), vinted.es (Spain), vinted.nl (the Netherlands) and vinted.pl (Poland). The Countries table above gives each recipe id. The parameters are the same in each, and none needs a login.

#Is there an official Vinted MCP server?

Not that we know of as of 7 November 2026. Wield provides this search as a recipe that runs in your browser.

#Which AI apps work with it?

Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. The AI apps page lists each one.

#Does it need a login?

No. Search needs no account.

#How fast is it compared with a browser agent?

In our benchmark on vinted.de, as of 7 Nov 2026 (preliminary, still running), the recipe passed 9 of 9 runs with a median of 920 milliseconds. Browser Use driving Claude Sonnet 5.5 passed 7 of 8 runs (88%), with a median of 136.5 seconds and about $0.20 per run. The browser agent was not blocked in these runs. The benchmark page has the method and raw logs.