English Français العربية

DealOracle — OracleNet Deal Discovery Protocol Reference

Official registry E-commerce

OracleNet Deal Discovery Protocol — permissioned commercial matching for MCP/A2A agents.

Source code Website Documentation

Install

Add this to your client's MCP configuration (Claude Desktop: claude_desktop_config.json; Cursor: .cursor/mcp.json; VS Code and others use the same "mcpServers" shape).

Remote (streamable-http)
Claude Code 
claude mcp add --transport http dealoracle-oraclenet-deal-discovery-prot 'https://tooloracle.io/deal/mcp/'
JSON configuration (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "dealoracle-oraclenet-deal-discovery-prot": {
            "type": "http",
            "url": "https://tooloracle.io/deal/mcp/"
        }
    }
}

Documentation

From the project's README on GitHub, refreshed weekly. Links open on GitHub.

Contents
  1. OracleNet Deal Discovery Protocol
  2. Repository layout
  3. Conformance at a glance
  4. Reference implementation
  5. What this repository is not
  6. Contact
  7. License

OracleNet Deal Discovery Protocol

Status: Draft v1.1 — published for public review.

Specification and reference artefacts for a permissioned commercial matching layer for autonomous agents. This protocol defines how two software agents can:

  • Declare what they offer and seek (curated intent).
  • Discover one another without spam (opt-in policies, opt-out registries, subscribable Atom broadcast).
  • Exchange cryptographically verifiable proposals (W3C VCs).
  • Surface emergent demand observed from real agent traffic (separate from declared intent).
  • Enforce anti-spam governance through a strict client-side gate chain and append-only audit.

It is explicitly not a cold-outreach channel, not a general A2A messaging protocol, and not a directory. See SPEC.md §1.5 "Scope: What This Protocol Is Not".

Repository layout

.
├── SPEC.md                                # The normative specification (= RFC-0001 v1.1-draft)
├── CHANGELOG.md                           # Version history
├── CONTRIBUTING.md                        # How to propose changes
├── CODE_OF_CONDUCT.md                     # Standard conduct rules
├── LICENSE                                # CC BY 4.0 (specification text)
├── schemas/                               # JSON Schemas (normative)
│   ├── deal-policy.v1.json
│   ├── deal-proposal-card.v1.json
│   ├── deal-vc-v1.jsonld
│   └── deal-emergence.v1.json
├── examples/                              # Minimal conformant artefacts
│   ├── minimal-deal-policy.json
│   ├── minimal-do-not-contact.json
│   ├── minimal-deal-feed.atom
│   ├── proposal-card.json
│   └── deal-emergence.json
├── registry/                              # Draft registry submission material
│   ├── README.md                          # Submission policy
│   ├── protocol-descriptor.json           # Machine-readable pointer
│   ├── a2a-registry-entry.md              # Draft for A2A-style registries
│   └── mcp-registry-note.md               # Draft for MCP-server registries
├── docs/                                  # Rendered HTML + markdown copy
│   ├── index.html
│   ├── rfc-0001.html
│   └── rfc-0001.md
└── reference/                             # Pointer to the live reference deployment
    └── README.md

Conformance at a glance

A conformant implementation MUST:

  1. Publish a signed deal-policy.json at /.well-known/deal-policy.json.
  2. Treat an empty or missing inbox.accepts as a refusal to receive proposals.
  3. Verify cryptographic signatures on every inbound proposal.
  4. Publish and honour a do-not-contact.json (own-side and outgoing).
  5. Run the full gate chain in SPEC.md §10.3 before every outbound proposal, and log every decision in an append-only audit retained ≥ 12 months.

Additional RECOMMENDED layers: Atom broadcast (deal-feed.atom), W3C VC wire format for proposals, deal-emergence.json for observed demand, HTTP Link headers for discovery.

Reference implementation

A live reference implementation is running at:

  • https://feedoracle.io/.well-known/deal-policy.json
  • https://tooloracle.io/.well-known/deal-policy.json

With auxiliary layers at:

  • https://tooloracle.io/.well-known/do-not-contact.json
  • https://tooloracle.io/.well-known/deal-feed.atom
  • https://tooloracle.io/.well-known/deal-emergence.json
  • https://tooloracle.io/deal/intelligence?limit=20
  • https://tooloracle.io/deal/public-stats.json

The full, hosted specification is at https://tooloracle.io/docs/deal-protocol/rfc-0001.

What this repository is not

  • Not a published release. The Draft may change materially before leaving Draft.
  • Not a code library. This repository carries the specification. The reference implementation lives elsewhere and is linked from reference/README.md.
  • Not a registry. The registry/ folder contains draft submission material for external registries. Nothing in this repo has been submitted anywhere.

Contact

Inbound proposals (on a conformant deal-policy basis) may be delivered to any participating inbox listed in reference/README.md. General protocol discussion: via GitHub issues on this repository once it is published, or by email to the addresses listed on the reference origins.

License

Specification text: CC BY 4.0. See LICENSE.

Frequently asked questions

What is DealOracle — OracleNet Deal Discovery Protocol Reference?

OracleNet Deal Discovery Protocol — permissioned commercial matching for MCP/A2A agents.

How do I install DealOracle — OracleNet Deal Discovery Protocol Reference?

It runs as a remote server. In Claude Code: claude mcp add --transport http dealoracle-oraclenet-deal-discovery-prot 'https://tooloracle.io/deal/mcp/'. For other clients, paste the JSON configuration from this page into their MCP settings.

Does DealOracle — OracleNet Deal Discovery Protocol Reference need an API key?

Its registry entry lists no required key or secret. Some features may still need an account with the service it connects to.

Is DealOracle — OracleNet Deal Discovery Protocol Reference open source?

Its code is public on GitHub, but the repository does not declare a standard license.

Who maintains DealOracle — OracleNet Deal Discovery Protocol Reference?

It is published by ToolOracle. AI.tn lists it but does not maintain or endorse it.

From the official MCP Registry. Listing is not an endorsement: review a server's code and permissions before giving it access to your data.