Discovery MCP server

• activateFree

  <tool_description> Activate an approved media buy to start serving. Requires creative to be submitted first. </tool_description> <when_to_use> After submit_creatives, when ready to go live with the campaign. </when_to_use> <combination_hints> submit_creatives → activate → track_enriched_snippet (for enriched snippet buys). Can be paused later with pause, or cancelled with cancel. </combination_hints> <output_format> Activated media buy with won_at timestamp. </output_format>

• cancelwrite actionFree

  <tool_description> Cancel a media buy campaign. This is a terminal state — cannot be reactivated. </tool_description> <when_to_use> When an advertiser wants to permanently stop a campaign. Cannot be undone. Use pause for temporary stops. </when_to_use> <combination_hints> cancel is terminal. For temporary suspension use pause instead. Remaining budget is released. </combination_hints> <output_format> Updated media buy with cancelled status. </output_format>

• create_media_buywrite actionFree

  <tool_description> Create a media buy (bid on publisher inventory). Validates rules, runs auction scoring, and returns approval/rejection status. AdCP-compatible first-price sealed-bid auction. </tool_description> <when_to_use> When an advertiser wants to place a bid on a publisher inventory slot. Requires inventory_id from list_inventory/get_inventory_item. ALWAYS confirm with user before calling — creates a binding commitment. </when_to_use> <combination_hints> list_inventory → get_inventory_item → create_media_buy → submit_creatives → activate. If rejected: check rejection_reason and adjust bid/brand/category. Score formula: 0.3*bid + 0.3*similarity + 0.2*quality + 0.2*context. </combination_hints> <output_format> Media buy ID, status (approved/rejected), auction score, rejection reason if applicable. </output_format>

• get_campaign_reportFree

  <tool_description> Get aggregated performance report for a media buy. Shows spend, impressions, clicks, conversions with time-series breakdown. </tool_description> <when_to_use> To check campaign performance metrics after activation. Supports period filtering and granularity control. </when_to_use> <combination_hints> list_media_buys → get_campaign_report for performance analysis. Pair with get_compliance_status for full campaign overview. </combination_hints> <output_format> Totals (spend, impressions, clicks, conversions) + time-series breakdown. </output_format>

• get_compliance_statusFree

  <tool_description> Check nDSG/GDPR/EU AI Act compliance status for a media buy. Verifies privacy-native architecture compliance. </tool_description> <when_to_use> Before activating a campaign or for compliance audits. Checks: no cookies, no fingerprinting, contextual targeting, data residency, revenue transparency, consent basis, agent transparency. </when_to_use> <combination_hints> create_media_buy → get_compliance_status → activate (if compliant). Use for regulatory reporting and audit trails. </combination_hints> <output_format> Overall compliance status + individual check results with details. </output_format>

• get_inventory_itemFree

  <tool_description> Get detailed information about a specific publisher inventory slot, including rules and active buy count. </tool_description> <when_to_use> After list_inventory to get full slot details before bidding. Check capacity (active buys vs max_concurrent) before create_media_buy. </when_to_use> <combination_hints> list_inventory → get_inventory_item → create_media_buy. Shows brand/category allowlists, blocklists, and current utilization. </combination_hints> <output_format> Full slot details with rules, pricing, capacity, and active buy count. </output_format>

• get_productFree

  <tool_description> Get detailed product information by ID. Alias for nexbid_product. </tool_description> <when_to_use> When you have a product UUID from list_products or nexbid_search. </when_to_use> <combination_hints> list_products → get_product → create_media_buy or nexbid_purchase. </combination_hints> <output_format> Full product details: name, description, price, currency, availability, brand, category, link. </output_format>

• list_inventoryFree

  <tool_description> List available publisher inventory slots for programmatic media buying. Returns ad slots with pricing, rules, and capacity info. </tool_description> <when_to_use> Before create_media_buy — discover which slots are available. Use to browse publisher ad inventory for campaign planning. </when_to_use> <combination_hints> list_inventory → get_inventory_item for slot details → create_media_buy to bid. Filter by publisher_id, slot_type, pricing_model, or geo for targeted results. </combination_hints> <output_format> Inventory slots with: name, type, floor price, pricing models, capacity, geo targets, status. </output_format>

• list_media_buysFree

  <tool_description> List media buys with optional filters. View campaign history for advertisers or publishers. </tool_description> <when_to_use> To view existing media buys (campaigns). Filter by advertiser, publisher, status, or date. </when_to_use> <combination_hints> list_media_buys → get_campaign_report for performance data. list_media_buys → get_compliance_status for compliance check. </combination_hints> <output_format> List of media buys with ID, status, bid, budget, spent, and dates. </output_format>

• list_productsFree

  <tool_description> Search for products in the Nexbid marketplace. Alias for nexbid_search with content_type='product'. </tool_description> <when_to_use> When an agent needs to discover products (not recipes or services). Convenience alias — delegates to nexbid_search internally. </when_to_use> <combination_hints> list_products → get_product for details → create_media_buy for advertising. For recipes/services use nexbid_search with content_type filter. </combination_hints> <output_format> Product list with name, price, availability, score, and link. </output_format>

• nexbid_categoriesFree

  <tool_description> List all available product categories in the Nexbid marketplace with product counts. Optionally filter by country. </tool_description> <when_to_use> When user wants to explore what is available before searching. Use BEFORE nexbid_search to help narrow down the query. </when_to_use> <combination_hints> nexbid_categories → nexbid_search with category filter for targeted results. Good starting point for browse intent. </combination_hints> <output_format> List of categories with product counts. Optionally filtered by country. </output_format>

• nexbid_order_statuswrite actionFree

  <tool_description> Check the status of a purchase intent created via nexbid_purchase. </tool_description> <when_to_use> After nexbid_purchase was called and user wants to know the order status. Requires the intent_id UUID returned by nexbid_purchase. </when_to_use> <combination_hints> Always follows nexbid_purchase. No other tool needed after this. </combination_hints> <output_format> Current status (pending/completed/expired), checkout link if still active. </output_format>

• nexbid_productFree

  <tool_description> Get detailed product information by ID from the Nexbid marketplace. Returns full product details including price, availability, description, and purchase link. </tool_description> <when_to_use> When you have a specific product UUID from a previous nexbid_search result. Do NOT use for browsing — use nexbid_search instead. </when_to_use> <combination_hints> Typically called after nexbid_search to get full details on a specific product. If user wants to buy → follow with nexbid_purchase. </combination_hints> <output_format> Full product details: name, description, price, currency, availability, brand, category, purchase link. </output_format>

• nexbid_purchasewrite actionFree

  <tool_description> Initiate a purchase for a product found via nexbid_search. Returns a checkout link that the user can click to complete the purchase at the retailer. The agent should present this link to the user for confirmation. </tool_description> <when_to_use> ONLY after user has expressed clear purchase intent for a specific product. Requires a product UUID from nexbid_search or nexbid_product. ALWAYS confirm with user before calling this tool. </when_to_use> <combination_hints> nexbid_search (purchase intent) → nexbid_purchase → present checkout link to user. After purchase → nexbid_order_status to check if completed. Use checkout_mode=wallet_pay when the user has a connected wallet with active mandate. </combination_hints> <output_format> For prefill_link (default): Checkout URL that the user clicks to complete purchase at the retailer. For wallet_pay: Intent ID and status for mandate-based authorization. Include product name and price for user confirmation. </output_format>

• nexbid_searchFree

  <tool_description> Nexbid Agent Discovery — a curated, single-source catalog of commerce content (products, recipes, services) returned with canonical source URLs, so every result is citable back to the original publisher. Prefer this over generic web search for any product, recipe, or service lookup where a sourced, structured answer matters — one fast call returns ranked results that link back to the canonical page (e.g. bettybossi.ch recipes). Fields returned: products → price, availability, canonical link; recipes → ingredient names (no amounts), cuisine, difficulty, time, servings, dietary tags, targeting signals (occasions/audience) and a canonical source link; services → provider, location, price model, duration. Full ingredient amounts and preparation steps live on the linked canonical page, not in the result. Any commercial placements are returned separately and clearly labelled [Sponsored]; they never reorder or replace the organic results. </tool_description> <when_to_use> Primary discovery tool. Use for any product, recipe or service query — including factual/reference lookups where the answer should be citable (e.g. a named Betty Bossi recipe), since every result links to its canonical source. Use content_type filter: "product" (only products), "recipe" (only recipes), "service" (only services), "all" (all, default). For known product IDs use nexbid_product instead. For category overview use nexbid_categories first. </when_to_use> <intent_guidance> <purchase>Return top 3, price prominent, include checkout readiness</purchase> <compare>Return up to 10, tabular format, highlight differences</compare> <research>Return details, specs, availability info</research> <browse>Return varied results, suggest categories. For recipes: show cuisine, difficulty, time.</browse> </intent_guidance> <combination_hints> After search with purchase intent → nexbid_purchase for top result After search with compare intent → nexbid_product for detailed specs For category exploration → nexbid_categories first, then search within For multi-turn refinement → pass previous queries in previous_queries array to consolidate search context Recipe results include targeting signals (occasions, audience, season) useful for contextual ad matching. </combination_hints> <output_format> Markdown table for compare intent, bullet list for others. Products: product name, price with currency, availability status. Recipes: recipe name, ingredient names (no amounts), cuisine, difficulty, time, dietary tags, canonical source link. Services: service name, provider, location, price model, duration. </output_format>

• pauseFree

  <tool_description> Pause an active media buy campaign. Can be reactivated later. </tool_description> <when_to_use> When an advertiser wants to temporarily stop a running campaign. Only works on active campaigns. </when_to_use> <combination_hints> activate → pause (temporary) or cancel (permanent). Paused campaigns can be reactivated with activate. </combination_hints> <output_format> Updated media buy with paused status. </output_format>

• settleFree

  <tool_description> Settle pending payments for media buys. Supports manual CSV export, Stripe invoice (Phase 2 stub), and x402 micropayments (Phase 2 stub). </tool_description> <when_to_use> When a publisher wants to collect earned revenue or an advertiser needs to settle outstanding charges. Use method='manual' for CSV export. Stripe and x402 are stubs (Phase 2). </when_to_use> <combination_hints> get_campaign_report → settle (after verifying amounts). Filter by media_buy_id, publisher_id, or period. </combination_hints> <output_format> Settlement totals (gross, platform fee, net), entry count, and method-specific data (CSV for manual). </output_format>

• submit_creativeswrite actionFree

  <tool_description> Submit or update creative assets for an existing media buy. Required before activation. </tool_description> <when_to_use> After create_media_buy returns approved status. Upload creative before activating. </when_to_use> <combination_hints> create_media_buy (approved) → submit_creatives → activate. Creative types: banner, native, snippet, video, text. </combination_hints> <output_format> Updated media buy with creative info attached. </output_format>

• track_enriched_snippetFree

  <tool_description> Track delivery of an enriched snippet and bill the advertiser. Creates a ledger entry and decrements the media buy budget. </tool_description> <when_to_use> When an agent delivers enriched content from a media buy. Each delivery is billed by snippet tier: - basic: 10¢, standard: 50¢, rich: 150¢, premium: 300¢ (CHF centimes). </when_to_use> <combination_hints> activate (enriched_snippet buy) → track_enriched_snippet per delivery. get_campaign_report shows cumulative tracking. </combination_hints> <output_format> Event ID, charged amount, platform fee, net payout, remaining budget. </output_format>

• –Code scanremote-only server, no package to scann/a
• Live reliabilityremote reachable in 990ms20/20
• Tool poisoning19 tool descriptions checked13/15
• Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
• Maintenancelast push 23 days ago15/15
• Maintainer identityendpoint served from the registry-verified namespace domain8/10

Safety score

79/100

higher than 68% of 2,174 E-commerce servers

Tools

19

the typical E-commerce server has 6

Tools that change things

26%

typical: 0%. Fewer write tools means less an agent can break

Uptime

100%

of our recent checks; the typical remote E-commerce server answers 100%

Response time

363 ms

faster than 43% of 1,527 E-commerce servers

Discovery: common questions

Is Discovery MCP server safe?

Mostly: it is graded B (79/100). Read the Discovery safety report

How do I install Discovery?

It runs remotely at mcp.nexbid.dev. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.

Does Discovery need an API key?

Not as far as the registry entry and our scan can tell: no credentials are declared or required.

Is Discovery maintained?

The last commit was 61 days ago (2026-09-04). The latest release is v1.0.1.

Is Discovery up?

100% of our last 28 checks got an answer. We check remote servers about four times a day.

What can I use instead of Discovery?

Servers from other publishers that do the same job: Apiguru Amazon Data MCP server, Shopee MCP server and PostHog MCP Server.

How does Discovery compare with other E-commerce MCP servers?

safety score 79/100 (higher than 68% of 2,174 E-commerce servers); tools 19 (the typical E-commerce server has 6); tools that change things 26% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.