DBA MCP server: let your AI agent search second-hand listings

#What your agent gets

The tool takes one required input, query, for example cykel, sofa or iphone 13. The optional inputs are min_price and max_price in DKK, condition, seller, type, sort and page.

condition takes new (unopened), like_new, good, used (visibly used) or needs_repair. seller takes any (the default), private or business. type takes for_sale (the default), giveaway (free items) or wanted (people looking to buy). sort takes relevance (the default), newest, oldest, price_low or price_high. Each page holds 53 listings.

The result has query, total, page, last_page and listings. Each listing has title, price, currency, location, published_at (in UTC), seller, shipping, buy_now, latitude, longitude, image and url. The shipping field says whether shipping is offered. The result has no shipping cost field.

#How a request flows

1. You ask your agent: "Find used bikes on DBA under 2,000 DKK, newest first, from private sellers."
2. The agent calls find_recipe, then run with dba.dk/search-marketplace, query set to cykel, max_price set to 2000, sort set to newest and seller set to private.
3. wield-mcp passes the run through the local bridge to the Wield extension.
4. The extension sends the request from a DBA tab in your browser, so the search runs in your own browser.
5. The listings go back to your agent. Nothing passes through wield.run.

In our check on 7 November 2026, a cykel search up to 2,000 DKK, newest first, passed all 6 checks in one request and 0.6 s. A sofa search for giveaways from private sellers returned 384 listings at 0 DKK. A nonsense query returns near matches, because the search is fuzzy.

#What leaves your computer

A search makes one request to www.dba.dk, the same search the DBA page makes. The recipe never sends messages, makes offers or saves favourites. Wield logs the request on your computer only, with method, host, path, status and timing. It never logs bodies or query values. Telemetry is off by default. Wield never reads, copies or sends your cookies or passwords.

#DBA's terms, in plain words

DBA's robots.txt allows the search and its API. It disallows URLs with sort= for bots. The recipe sends sort= only when you ask for an order other than relevance, so a search in the default order sends none. Each call makes one request, the same search the page makes.

The scope is simple. Wield runs this recipe when you ask for it, for one search per call, from your own browser. It does not run bulk jobs, and it does not buy anything.

Our review of these terms is not finished, and this is not legal advice. Read DBA's terms and its robots.txt yourself before you use the recipe in any other way.

#Limits and what is not working yet

• Read only. The recipe searches. It does not message sellers, make offers or save favourites.
• Fuzzy search. A nonsense query returns near matches. Check the title before you act on one.
• Times are in UTC. published_at is given in UTC.
• 53 listings per page. Use page to read more, one search per call.
• No shipping cost. The result has a shipping flag only.
• Run limits apply. A run has at most 12 steps, 40 requests, 5 MB per response and 60 seconds.

#FAQ

#Can the agent message a seller or make an offer?

No. The recipe only searches. It does not send messages, make offers or save favourites.

#Does the result show the shipping cost?

No. It shows a shipping flag for each listing. Open the listing url to see the seller's terms.

#Does it need a DBA login?

No. Search works without an account.

#Which AI apps work with it?

Any MCP client. npx -y wield-mcp init sets up Claude Desktop, Claude Code, Cursor and Codex. Other MCP clients work with the standard stdio config.

#Where do the results go?

To your agent, on your own computer. The results never pass through wield.run.