A
actimod/onaa-protocol
Open directory of stores where AI agents reached checkout (payment not tested), plus payment, escrow and shipping providers.
updated 2026-11-17
View on GitHub ↗Direct link · no redirect page
We have neither an install command nor a public remote endpoint from this repository, so we do not print a config. A made-up one is worse than none. How each client wires MCP up →
- Star count
- 0 ★ · actimod/onaa-protocol · read from the GitHub search API · (checked 2026-11-19 20:00:48)
- Source
- collected from the punkpeye/awesome-mcp-servers list · type: MCP server
- Harvest history
- first seen 2026-11-18 · last seen 2026-11-20 · seen 3× · listed by 3 sources
- Score
- score 300 · 3 sources · mcp
FAQ (answers come from our records)
Who is it for?
We filed it under these tags: MCP servers. The tags come from the entry itself, not a taxonomy we imposed.
Who maintains it?
repository
actimod/onaa-protocol;first catalogued 2026-11-18;last seen 2026-11-20。There is no official certification or quality rating here — we record sources and dates only.README excerpt (English, untranslated) · Read the full README on GitHub →
# ONAA Protocol — Open Network for AI Agents
Excerpted from the repository README (abridged)
Open directory of stores where AI agents reached checkout (payment not tested), plus payment, escrow and shipping providers. Links only; ONAA never pays.
> Building a shopping agent? Start with examples/buyer-store-preflight: it checks real stores with ONAA and stops before checkout (python3 preflight.py --offline runs with no network; payment is never tested). It is different from examples/direct-trade-demo, a mock agent-to-agent trade.
More broadly, ONAA is an open, hybrid peer-to-peer network for AI agents. A shared directory lets buyer, seller and service agents find each other and check trust signals. The actual conversation and trade happen directly between the agents, over open protocols (A2A and MCP). Escrow, payment, shipping, insurance, inspection, dispute, identity and hosting providers join the same directory as equal, discoverable participants.
What ONAA is and is not. ONAA is a discovery and trust-metadata directory. It does not execute orders, hold
funds, process payments, run escrow, or relay negotiation messages: agents contact each other directly at the
endpoints they publish. Store and marketplace lookup (where an AI buying agent reached checkout, and how; payment is never tested) is one
specialised discovery feature of the directory, not a checkout service: purchases happen at the store itself.
> Status: early draft (ONAA Protocol v0.1.3). This repository holds the protocol specification, a reference directory API, a Python SDK, a buyer-store preflight example and a runnable direct-trade demo. A development directory runs at https://api.onaa.net (agent instructions: https://api.onaa.net/llms.txt, remote MCP: https://api.onaa.net/mcp). It is not a production service: there is no real money movement and no hosted trade agent, and the demo uses a mock escrow. ONAA is a working project name; no trademark is claimed. Canonical facts (tool counts, field meanings, retention, tested countries): docs/CANONICAL_FACTS.md.
## What is in this repository
| Path | What it is |
| specs/ | Draft specifications: the commerce extension for A2A (RFQ / QUOTE / escrow handoff), JSON Schemas for directory and certification records, the directory OpenAPI document, and the standards baseline (pinned A2A / MCP versions). |
| apps/api/ | Reference directory API (FastAPI): registration, search, endpoint verification and separate trust levels. |
| apps/mcp-registry/ | MCP server source (Python, official mcp SDK): directory search, shopping guidance and trust lookups for MCP clients, over stdio or Streamable HTTP. Read-only by default. |
| packages/sdk-python/ | Python SDK for directory discovery and registration. |
| examples/buyer-store-preflight/ | Shopping-agent preflight against real stores: find_stores → can_i_buy_here → how_to_buy → the store's own catalog, then stops before checkout. Runs offline with --offline. Never pays. |
| examples/direct-trade-demo/ | End-to-end demo: buyer agent → directory search → direct A2A RFQ/QUOTE with a seller agent → directory escrow search → mock escrow handoff. |
| docs/PRINCIPLES.md | The design principles the code and specs follow. |
| docs/ADR/ | Architecture decision records. |
> Building a shopping agent? Start with examples/buyer-store-preflight: it checks real stores with ONAA and stops before checkout (python3 preflight.py --offline runs with no network; payment is never tested). It is different from examples/direct-trade-demo, a mock agent-to-agent trade.
More broadly, ONAA is an open, hybrid peer-to-peer network for AI agents. A shared directory lets buyer, seller and service agents find each other and check trust signals. The actual conversation and trade happen directly between the agents, over open protocols (A2A and MCP). Escrow, payment, shipping, insurance, inspection, dispute, identity and hosting providers join the same directory as equal, discoverable participants.
What ONAA is and is not. ONAA is a discovery and trust-metadata directory. It does not execute orders, hold
funds, process payments, run escrow, or relay negotiation messages: agents contact each other directly at the
endpoints they publish. Store and marketplace lookup (where an AI buying agent reached checkout, and how; payment is never tested) is one
specialised discovery feature of the directory, not a checkout service: purchases happen at the store itself.
> Status: early draft (ONAA Protocol v0.1.3). This repository holds the protocol specification, a reference directory API, a Python SDK, a buyer-store preflight example and a runnable direct-trade demo. A development directory runs at https://api.onaa.net (agent instructions: https://api.onaa.net/llms.txt, remote MCP: https://api.onaa.net/mcp). It is not a production service: there is no real money movement and no hosted trade agent, and the demo uses a mock escrow. ONAA is a working project name; no trademark is claimed. Canonical facts (tool counts, field meanings, retention, tested countries): docs/CANONICAL_FACTS.md.
## What is in this repository
| Path | What it is |
| specs/ | Draft specifications: the commerce extension for A2A (RFQ / QUOTE / escrow handoff), JSON Schemas for directory and certification records, the directory OpenAPI document, and the standards baseline (pinned A2A / MCP versions). |
| apps/api/ | Reference directory API (FastAPI): registration, search, endpoint verification and separate trust levels. |
| apps/mcp-registry/ | MCP server source (Python, official mcp SDK): directory search, shopping guidance and trust lookups for MCP clients, over stdio or Streamable HTTP. Read-only by default. |
| packages/sdk-python/ | Python SDK for directory discovery and registration. |
| examples/buyer-store-preflight/ | Shopping-agent preflight against real stores: find_stores → can_i_buy_here → how_to_buy → the store's own catalog, then stops before checkout. Runs offline with --offline. Never pays. |
| examples/direct-trade-demo/ | End-to-end demo: buyer agent → directory search → direct A2A RFQ/QUOTE with a seller agent → directory escrow search → mock escrow handoff. |
| docs/PRINCIPLES.md | The design principles the code and specs follow. |
| docs/ADR/ | Architecture decision records. |
Listed badge (optional)
Copy this line into the README if you want the listing mark. Optional, and it does not affect being listed.
[](https://anclum.com/en/s/actimod-onaa-protocol/)
- Source
- awesome · https://github.com/actimod/onaa-protocol
- Browse by field
- MCP servers
- Listed by
- 3 independent sources
- added
- today
More MCP servers
Filed under
Every tag opens the full list for that filter. Counts are the live catalogue figures.