OpenNodes MCP server

OpenNodes Protocol (ONP) — Draft 0.1

An open standard for discovering, invoking, and paying AI inference endpoints ("AI Nodes") across vendors — from frontier labs to a university GPU cluster — with bridges to MCP and WebMCP.

Status: Draft 0.1 (working proposal, 2026-08-20) — not affiliated with any standards body yet. Home: opennodes.io

The one-sentence pitch

MCP standardized how AI applications reach tools; the OpenAI API shape standardized how they invoke models; x402 standardized how machines pay each other — but nothing standardizes how a client finds an inference endpoint it doesn't already know about: what model it serves, how big it is, what hardware backs it, how well it benchmarks, what it costs per token, and whether it's up. ONP fills exactly that gap and composes the rest from existing standards.

Documents

Start here

• 00 — Project overview — the concept, architecture, implementation status, completed development stages, and next steps in one document.

Research (why this standard, and why now)

• 01 — Protocol & standards landscape — MCP + Registry, WebMCP, A2A, AGNTCY, ANP, NANDA, OpenAI-compatible APIs, DIDs/VCs, x402, UCAN, model cards, MLPerf; full gap analysis.
• 02 — Market landscape & demand evidence — OpenRouter, HF Inference Providers, gateways, DePIN/decentralized compute, OS-level AI runtimes, payment rails; viability assessment.
• 04 — Universal AI client landscape — AI browsers, branded assistants, neutral/BYOK clients, multi-homing data, distribution economics; assessment of the "primary access point" client idea.

Specification suite

• ONP-1 — Overview, terminology, architecture, conformance
• ONP-2 — The Node Card — self-description document at /.well-known/open-node.json
• ONP-3 — Registry & Discovery API — registration, verification, search, health, ranking, federation
• ONP-4 — Invocation profiles — bindings for text, image/diffusion, embeddings, agents
• ONP-5 — Settlement — price advertisement, payment schemes (x402 / prepaid / free), signed usage receipts
• ONP-6 — Bridging — connecting discovered nodes to MCP servers, WebMCP sites, and conventional web data

Development requirements

• REQ-001 — Discovery Service (registry) — MVP registry: registration, admission battery, search, estimation, MCP surface; acceptance criteria.
• REQ-002 — Test client — CLI + OpenAI-compatible gateway + MCP modes; compatibility matrix (Cursor, VS Code, Open WebUI…).
• REQ-003 — Node Kit — reverse-proxy wrapper turning vLLM/Ollama/TGI into a conforming node: card generation, receipts, registration, self-test.

Install (published packages)

npx @opennodes/cli mcp --print-config   # discovery + advisor tools for Cursor / VS Code / Claude Desktop
npx @opennodes/cli gateway --port 4141  # OpenAI-compatible gateway with onp/auto routing; base URL http://127.0.0.1:4141/v1
npx @opennodes/registry                 # run a registry: web app + API + MCP on http://127.0.0.1:4300
npx @opennodes/ollama-router            # OpenNodes for Ollama: one Ollama endpoint over local + LAN + verified public models
pipx install onp-node                   # Node Kit: turn a vLLM / Ollama / TGI deployment into a conforming node

Shortened. The full README is on GitHub.