mcpField
D
DealOracle — OracleNet Deal Discovery Protocol Reference

DealOracle — OracleNet Deal Discovery Protocol Reference

Remote
tooloracle.ioBusiness & Marketing0Updated 27w ago

About DealOracle — OracleNet Deal Discovery Protocol Reference

OracleNet Deal Discovery Protocol is a draft specification for permissioned commercial matching between autonomous agents. It defines opt-in discovery, verifiable proposals, observed demand, and anti-spam controls; this repository contains the specification, not a code library.

Key features

  1. 01Curated offer and request declarations
  2. 02Opt-in discovery and opt-out registries
  3. 03Cryptographically verifiable proposals
  4. 04Observed demand from agent traffic
  5. 05Client-side anti-spam gates and audit

Use cases

  1. 01Defining agent commercial matching implementations
  2. 02Discovering opted-in counterparties
  3. 03Verifying proposals with signed credentials
  4. 04Auditing outbound proposal decisions

MCP support

The specification describes a permissioned commercial matching layer for MCP/A2A agents. This repository provides protocol documentation and schemas, not an MCP server implementation.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://tooloracle.io/deal/mcp/
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.