English Français العربية

dev.nexbid/discovery

Registre officiel Recherche et web

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

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

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

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  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.

Questions fréquentes

Qu'est-ce que dev.nexbid/discovery ?

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

Comment installer dev.nexbid/discovery ?

Il fonctionne comme serveur distant. Dans Claude Code : claude mcp add --transport http discovery 'https://mcp.nexbid.dev/mcp'. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour dev.nexbid/discovery ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

dev.nexbid/discovery est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient dev.nexbid/discovery ?

Il est publié par nexbid-dev. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.