Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"nexbid": {
"url": "https://mcp.nexbid.dev/mcp",
"transport": "streamable-http"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
The open infrastructure for agent-native commerce.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y '@protocol-commerce/adcp-sdk' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked @protocol-commerce/adcp-sdk against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in ai-ml / ecommerce
Persistent memory using a knowledge graph
Dynamic problem-solving through sequential thought chains
Workspace template + MCP server for Claude Code, Codex CLI, Cursor & Windsurf. Multi-agent knowledge engine (ag-refresh / ag-ask) that turns any codebase into a queryable AI assistant.
Privacy-first. MCP is the protocol for tool access. We're the virtualization layer for context.
MCP Security Weekly
Get CVE alerts and security updates for dev.nexbid/discovery and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
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.
| 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 |
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',
});
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 →
score = 0.4×bid + 0.4×relevance + 0.2×qualityNexbid 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 |
{
"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.
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
| Sponsor | Role |
|---|---|
| Nexbid | Initiator, reference implementation, initial maintainer |
MIT — Use it, fork it, build on it. No strings attached.