Nexbid MCP server
Commit Sep 4, 2026Enables AI agents to search, browse, and purchase products through an open, standardized commerce marketplace.
Also known as nexbid-dev/protocol-commerce, protocol-commerce
- Stars
- 1
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 1.0.1
- Last commit
- Sep 4, 2026
- License
- MIT
What is Nexbid MCP?
Nexbid enables AI agents to search, browse, and purchase products through an open, standardized commerce marketplace.
Summary generated from the project's README
About Nexbid MCP server
Discovery provides an open infrastructure for agent-native commerce, allowing AI agents to search, browse, and purchase products through a standardized marketplace. It functions as a bridge between LLMs and commerce protocols, using the Agentic Discovery Commerce Protocol (AdCP) to ensure interoperability. Developers can integrate this via the Nexbid reference implementation, which connects to any MCP-compatible model like Claude, GPT-4, or Gemini using a streamable-http transport.
To use the service, developers configure the server with a specific URL and an API key. The system utilizes a TypeScript SDK for client implementation and includes a WebMCP browser integration to expose commerce tools through the navigator.modelContext interface. Unlike proprietary alternatives, this server relies on mathematically proven security properties verified via Lean 4 and uses a transparent scoring formula based on bid, relevance, and quality to determine product results.
What you can do with it
- 1Product Search and PurchaseAn AI agent can find specific items and execute a transaction based on user intent.
- 2Localized Commerce DiscoveryA developer can instruct an agent to find products within a specific geographic region.
- 3Browser-Based Agent IntegrationDevelopers can expose commerce capabilities to AI agents running directly in a web browser.
Written from the project's README. Every use case is checked against a quote from it.
How to install Nexbid MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall Nexbid MCP in Claude Code
$ claude mcp add --transport http protocol-commerce https://mcp.nexbid.dev/mcpInstall Nexbid MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"protocol-commerce": {
"url": "https://mcp.nexbid.dev/mcp"
}
}
}Install Nexbid MCP in VS Code
.vscode/mcp.json
{
"servers": {
"protocol-commerce": {
"type": "http",
"url": "https://mcp.nexbid.dev/mcp"
}
}
}Install Nexbid MCP in VS Code CLI
$ code --add-mcp '{"name":"protocol-commerce","type":"http","url":"https://mcp.nexbid.dev/mcp"}'Install Nexbid MCP in Codex
$ codex mcp add protocol-commerce --url https://mcp.nexbid.dev/mcpInstall Nexbid MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.protocol-commerce] url = "https://mcp.nexbid.dev/mcp"
Install Nexbid MCP in Gemini CLI
$ gemini mcp add -s user --transport http protocol-commerce https://mcp.nexbid.dev/mcpInstall Nexbid MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"protocol-commerce": {
"url": "https://mcp.nexbid.dev/mcp",
"type": "http"
}
}
}Automated checks
Ran Nov 15, 2026Full report →Not verified yet. A server needs a score of 80, no serious finding, and enough data for us to check. How checks work · What to fix for more points
- Source repository linked and reachablenexbid-dev/protocol-commerce is public and reachablegithub.com/nexbid-dev/protocol-commerce ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)MITspdx.org/licenses/MIT.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-09-04github.com/nexbid-dev/protocol-commerce ↗Pass
- OpenSSF ScorecardNot checked
- Package name not close to a popular packageNot checked
- No critical advisory in the package or its dependenciesNot checked
- No hidden instructions to the model0 tool descriptions and the README read; no override phrases, credential paths or hidden charactersPass
- Destructive tools are labelledNot checked
- Remote endpoint answers the MCP handshakeinitialize answered with protocol 2025-06-18 in 633 msPass
README
View on GitHubProtocol 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
| Directory | Description |
|---|---|
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
- Open by Default — MIT-licensed, auditable, forkable
- Publisher Parity — Publishers are first-class protocol participants
- Privacy Native — Context signals, not user profiles
- Transparent Scoring — Public formula:
score = 0.4×bid + 0.4×relevance + 0.2×quality
Reference Implementation: Nexbid
Nexbid is the production-grade reference implementation of Protocol Commerce, built by digital opua GmbH (CHE-435.289.702, Switzerland).
| Metric | Status |
|---|---|
| MCP Integration | Native — full commerce lifecycle |
| Formal Verification | Lean 4 — core security properties proven |
| Privacy | Cookie-free, Swiss-hosted, nDSG + GDPR compliant |
| AI Scoring | Multi-provider, model-agnostic |
| Phase | Production-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
| Sponsor | Role |
|---|---|
| Nexbid | Initiator, reference implementation, initial maintainer |
License
MIT — Use it, fork it, build on it. No strings attached.
Links
Nexbid MCP questions
How do I add Nexbid MCP to Claude Code?
Run claude mcp add --transport http protocol-commerce https://mcp.nexbid.dev/mcp in your terminal. Add --scope user to make it available in every project.
How do I add Nexbid MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
What can AI agents do with Nexbid?
Any MCP-compatible LLM can directly search, browse, and purchase products through the Nexbid marketplace.
How is the security of the platform ensured?
The platform uses Lean 4 formal verification to mathematically prove core security properties are correct for all possible inputs.
What is the scoring formula used for products?
The public scoring formula is calculated as score = 0.4×bid + 0.4×relevance + 0.2×quality.