dev.nexbid/discovery

Official registry Search and web

Search and discover advertiser products through an open marketplace for AI agents.

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code
claude mcp add --transport http discovery 'https://mcp.nexbid.dev/mcp'
JSON configuration (Claude Desktop, Cursor, VS Code)
{
    "mcpServers": {
        "discovery": {
            "type": "http",
            "url": "https://mcp.nexbid.dev/mcp"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. Protocol Commerce
  2. Contents
  3. Quick Start
  4. The Problem
  5. Key Principles
  6. Reference Implementation: Nexbid
  7. Sponsors
  8. License
  9. Links

Protocol Commerce

The open infrastructure for agent-native commerce.

Protocol Commerce is an open initiative to create standardized, auditable, and interoperable protocols for AI agent-driven commerce. This repository contains the specification, SDKs, and technical manifesto.

Contents

DirectoryDescription
manifesto/Why open protocols matter for commerce — principles, landscape analysis, and rationale
adcp-spec/AdCP v0.1.0 — Agentic Discovery Commerce Protocol specification, JSON schemas, and examples
adcp-sdk-typescript/TypeScript SDK: types, validators, client, and scoring reference implementation
webmcp-reference/WebMCP browser integration: expose commerce tools to in-browser AI agents via navigator.modelContext
amdp-spec/AMDP v0.1.0 — Agent Mandate Discovery Protocol: cross-vertical authorization spec, JSON schemas, and example mandates
agentic-kit/Agentic Kit — the trust layer: building blocks for verifiable + auditable AI agents
lean-verification/Lean 4 formal verification — 47 theorems proving auction/budget/wallet/policy correctness, lake build-checkable

Quick Start

npm install @protocol-commerce/adcp-sdk
import { AdcpClient } from '@protocol-commerce/adcp-sdk';

const client = new AdcpClient({
  serverUrl: 'https://mcp.nexbid.dev',
  apiKey: 'your-api-key',
});

const results = await client.search({
  query: 'organic olive oil',
  intent: 'purchase',
  geo: 'CH',
});

The Problem

AI agents are becoming the primary interface for product discovery and purchase. The protocols powering this shift — OpenAI's ACP, Google's UCP — are proprietary and platform-controlled. Publishers have no representation. There is no open standard.

Protocol Commerce fills this gap.

Read the full Technical Manifesto →

Key Principles

  1. Open by Default — MIT-licensed, auditable, forkable
  2. Publisher Parity — Publishers are first-class protocol participants
  3. Privacy Native — Context signals, not user profiles
  4. Transparent Scoring — Public formula: score = 0.4×bid + 0.4×relevance + 0.2×quality

All 7 principles →

Reference Implementation: Nexbid

Nexbid is the production-grade reference implementation of Protocol Commerce, built by digital opua GmbH (CHE-435.289.702, Switzerland).

MetricStatus
MCP IntegrationNative — full commerce lifecycle
Formal VerificationLean 4 — core security properties proven
PrivacyCookie-free, Swiss-hosted, nDSG + GDPR compliant
AI ScoringMulti-provider, model-agnostic
PhaseProduction-grade closed beta
Connect Any LLM
{
  "mcpServers": {
    "nexbid": {
      "url": "https://mcp.nexbid.dev/mcp",
      "transport": "streamable-http"
    }
  }
}

Any MCP-compatible LLM (Claude, GPT-4, Gemini) can directly search, browse, and purchase products through the Nexbid marketplace.

Why Formal Verification?

Nexbid is the only commerce platform whose core security properties are mathematically proven in Lean 4 — not just tested, but proven correct for all possible inputs.

→ Technology details · How Nexbid compares

Sponsors

SponsorRole
NexbidInitiator, reference implementation, initial maintainer

License

MIT — Use it, fork it, build on it. No strings attached.

Frequently asked questions

What is dev.nexbid/discovery?

Search and discover advertiser products through an open marketplace for AI agents.

How do I install dev.nexbid/discovery?

It runs as a remote server. In Claude Code: claude mcp add --transport http discovery 'https://mcp.nexbid.dev/mcp'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does dev.nexbid/discovery need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is dev.nexbid/discovery open source?

Yes. Its code is on GitHub under the MIT license.

Who maintains dev.nexbid/discovery?

It is published by nexbid-dev. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.