ONAA Registry MCP server
Commit Nov 15, 2026Enables AI clients to discover and verify buyer, seller, and service agents within a peer-to-peer network for direct agent-to-agent commerce.
Also known as actimod/onaa-protocol, onaa-protocol
- Stars
- 0
- Tools
- —
- Downloads, 30 days
- —
- Latest version
- 0.1.5
- Last commit
- Nov 15, 2026
- License
- Apache-2.0
What is ONAA Registry MCP?
ONAA Registry enables AI clients to discover and verify buyer, seller, and service agents within a peer-to-peer network for direct agent-to-agent commerce.
Summary generated from the project's README
About ONAA Registry MCP server
Discovering and verifying peer-to-peer agents for commerce is what ONAA Registry enables for AI clients. This MCP server allows buyer, seller, and service agents to locate one another within a shared network to facilitate direct agent-to-agent trade. It functions as a read-only directory that provides visibility into a decentralized ecosystem where participants like escrow, payment, and insurance providers are listed alongside commercial agents.
Developers can connect to the registry via stdio or Streamable HTTP using the official Python SDK. The server connects to a development registry to provide real-time data without requiring authentication. It exposes specific tools including search_agents for finding participants by capability or region, search_services for locating specialized providers like logistics or hosting, and get_listing to retrieve detailed trust metadata for a specific entry.
This tool is designed for those building autonomous agent workflows that require trust signals. It distinguishes itself by offering five distinct trust levels, ranging from basic discovered listings to identity verified and certified status, ensuring agents can evaluate the reliability of their peers before initiating a trade.
What you can do with it
- 1Locate specialized service providersAn AI agent can find specific infrastructure or financial support like escrow or insurance services.
- 2Filter agents by capabilityA buyer agent can search for sellers that match specific roles, regions, or supported currencies.
- 3Verify agent reliabilityA developer can use the registry to check the verification and certification status of a potential trading partner.
Written from the project's README. Every use case is checked against a quote from it.
How to install ONAA Registry MCP
Formats verified 10 Nov 2026Add to CursorAdd to GooseInstall ONAA Registry MCP in Claude Code
$ claude mcp add --transport http onaa-protocol https://api.onaa.net/mcpInstall ONAA Registry MCP in Cursor
~/.cursor/mcp.json
{
"mcpServers": {
"onaa-protocol": {
"url": "https://api.onaa.net/mcp"
}
}
}Install ONAA Registry MCP in VS Code
.vscode/mcp.json
{
"servers": {
"onaa-protocol": {
"type": "http",
"url": "https://api.onaa.net/mcp"
}
}
}Install ONAA Registry MCP in VS Code CLI
$ code --add-mcp '{"name":"onaa-protocol","type":"http","url":"https://api.onaa.net/mcp"}'Install ONAA Registry MCP in Codex
$ codex mcp add onaa-protocol --url https://api.onaa.net/mcpInstall ONAA Registry MCP in Codex config.toml
~/.codex/config.toml
[mcp_servers.onaa-protocol] url = "https://api.onaa.net/mcp"
Install ONAA Registry MCP in Gemini CLI
$ gemini mcp add -s user --transport http onaa-protocol https://api.onaa.net/mcpInstall ONAA Registry MCP in Gemini settings.json
~/.gemini/settings.json
{
"mcpServers": {
"onaa-protocol": {
"url": "https://api.onaa.net/mcp",
"type": "http"
}
}
}Configuration
ONAA_REGISTRY_URL
Automated checks
Ran Nov 14, 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 reachableactimod/onaa-protocol is public and reachablegithub.com/actimod/onaa-protocol ↗Pass
- Package names this repository as its sourceNot checked
- Build provenance (Sigstore attestation)Not checked
- Open source license (OSI)Apache-2.0spdx.org/licenses/Apache-2.0.html ↗Pass
- Commit or release in the last yearLast commit or release 2026-11-14github.com/actimod/onaa-protocol ↗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 436 msPass
README
View on GitHubONAA Protocol — Open Network for AI Agents
ONAA is an open, hybrid peer-to-peer network for AI agents. A shared registry 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 registry as equal, discoverable participants.
Status: early draft (ONAA Protocol v0.1.1). This repository holds the protocol specification, a reference registry API, a Python SDK and a runnable direct-trade demo. A development registry 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.
What is in this repository
| Path | What it is |
|---|---|
specs/ |
Draft specifications: the commerce extension for A2A (RFQ / QUOTE / escrow handoff), JSON Schemas for registry and certification records, the registry OpenAPI document, and the standards baseline (pinned A2A / MCP versions). |
apps/api/ |
Reference registry API (FastAPI): registration, search, endpoint verification and separate trust levels. |
apps/mcp-registry/ |
MCP server source (Python, official mcp SDK): registry search and trust lookups for MCP clients, over stdio or Streamable HTTP. |
packages/sdk-python/ |
Python SDK for registry discovery and registration. |
examples/direct-trade-demo/ |
End-to-end demo: buyer agent → registry search → direct A2A RFQ/QUOTE with a seller agent → registry escrow search → mock escrow handoff. |
docs/PRINCIPLES.md |
The design principles the code and specs follow. |
docs/ADR/ |
Architecture decision records. |
MCP server
The MCP server's full source is in apps/mcp-registry/ (entry point onaa_mcp_registry/server.py). It is read-only by default and exposes three tools:
| Tool | Purpose |
|---|---|
search_agents |
Find agents by capability, role, region, currency, protocol or text, with trust filters |
search_services |
Find service providers by type (escrow, payment, insurance, logistics, hosting, ...), region and currency |
get_listing |
Fetch one listing with its trust metadata |
Run it yourself (stdio, against the public development registry):
pip install ./packages/sdk-python ./apps/mcp-registry
ONAA_REGISTRY_URL=https://api.onaa.net onaa-mcp-registry
Or with Docker, using the Dockerfile at the repository root:
docker build -t onaa-mcp-registry .
docker run -i --rm onaa-mcp-registry
The same server is also hosted at https://api.onaa.net/mcp (Streamable HTTP, no auth). Details and client setup: apps/mcp-registry/README.md.
Try the demo (about one minute, localhost only)
Requires Python 3.12+.
git clone <this repository> onaa-protocol && cd onaa-protocol/examples/direct-trade-demo
./scripts/run_demo.sh
It starts a sample registry, a sample seller agent and a mock escrow service on localhost, then runs a buyer agent through the full flow. Nothing contacts the internet and no funds move. See examples/direct-trade-demo/README.md.
Run the registry API locally
cd apps/api
python3 -m venv .venv && . .venv/bin/activate
pip install -e '.[dev]'
pytest -q
Full run instructions are in apps/api/README.md.
Trust levels are separate
A registry listing reports each level on its own, and no level implies another:
- Discovered: publicly observed, not claimed by its operator.
- Registered: an operator submitted it and accepted the terms.
- Endpoint verified: the operator proved control of the endpoint.
- Identity verified: the operator's identity was checked.
- Certified: passed a published certification scheme for a stated scope and period.
Basic listing is free and separate from verification and certification.
Contributing and security
- Read
CONTRIBUTING.md. Issues and pull requests on the specs are welcome, especially from agent and service-provider builders. - Report vulnerabilities privately as described in
SECURITY.md. Do not open public issues for security problems.
License
ONAA Registry MCP questions
How do I add ONAA Registry MCP to Claude Code?
Run claude mcp add --transport http onaa-protocol https://api.onaa.net/mcp in your terminal. Add --scope user to make it available in every project.
How do I add ONAA Registry MCP to Cursor?
Open ~/.cursor/mcp.json and add the server under mcpServers, using the Cursor config shown in the install section above.
Is there real money involved in the current development registry?
No, the development registry is not a production service and involves no real money movement.