Discovery
Let an agent search Nexbid’s open marketplace to discover advertiser products and offers before you embed commerce in your build.
Overview
dev.nexbid/discovery is an MCP server for the Idea phase that lets agents search and discover advertiser products through Nexbid’s open marketplace endpoint.
What is this MCP server?
- Hosted MCP at https://mcp.nexbid.dev/mcp (streamable-http)
- Search and discover advertiser products via an open marketplace protocol
- Built for AI agents as first-class consumers of catalog data
- Catalog version 1.0.1; open-source protocol repo on GitHub (nexbid-dev/protocol-commerce)
- Remote-only registration—no npm stdio package in catalog entry
- Server version 1.0.1
- Remote URL: https://mcp.nexbid.dev/mcp (streamable-http)
- Source repository: github.com/nexbid-dev/protocol-commerce
What problem does it solve?
Builders waste time manually hunting advertiser catalogs when an agent could explore offers programmatically during early product research.
Who is it for?
Indie builders prototyping agentic shopping, affiliate discovery, or ad-marketplace features who want MCP-native search early.
Skip if: Teams that need finalized affiliate contracts, payment capture, or full ecommerce ops without a separate commerce stack.
What do I get? / Deliverables
After you add the Nexbid Discovery MCP URL, your agent can query marketplace products to inform positioning, prototypes, and commerce feature specs.
- Configured Nexbid Discovery remote MCP connection
- Agent-retrieved advertiser product discovery results for specs and prototypes
Recommended MCP Servers
Journey fit
Product and offer discovery happens while you are still exploring what to build or promote, which aligns with the Idea phase shelf. The server is explicitly for search and discovery across an advertiser marketplace—not checkout or ops—so discover is the canonical subphase.
How it compares
Marketplace discovery MCP—not a storefront builder skill or payment processor integration.
Common Questions / FAQ
Who is dev.nexbid/discovery for?
Solo builders and agent developers researching advertiser product catalogs via MCP during ideation and early validation.
When should I use dev.nexbid/discovery?
In Idea/Discover when you need agent-driven search across Nexbid’s open marketplace before committing to a commerce integration design.
How do I add dev.nexbid/discovery to my agent?
Register remote MCP https://mcp.nexbid.dev/mcp (streamable-http) in your Claude Code, Cursor, or compatible client, then call discovery tools from the agent.