# DealOracle — OracleNet Deal Discovery Protocol Reference [Health: Active]

**Category:** 🤝 Agreements & Coordination  
**Repository:** https://github.com/ToolOracle/oraclenet-deal-protocol  
**GitHub Stars:** 0  
**Views:** 2  
**Installs:** 0  
**Upvotes:** 0  
**Directory Page:** https://allmcps.com/mcp/dealoracle-oraclenet-deal-discovery-protocol-reference

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

## Claude Desktop Quick Installation
No confirmed install details yet, so no config is published. Follow the setup steps in the repository above.

## Documentation

## What DealOracle — OracleNet Deal Discovery Protocol Reference MCP server does

DealOracle — OracleNet Deal Discovery Protocol Reference MCP server describes a permissioned commercial matching layer for autonomous agents. Its scope covers how agents declare what they offer and seek, find compatible participants under opt-in rules, exchange verifiable proposals, and report demand inferred from real agent activity.

The repository is primarily a specification package, not an executable code library or a directory of businesses. Its central normative document is `SPEC.md`, identified as RFC-0001 v1.1-draft. Supporting files include JSON Schemas for policies, proposal cards, verifiable credentials, and demand observations, along with minimal conformant examples.

The protocol is deliberately narrower than cold outreach, general agent-to-agent messaging, or an open listing service. Participation depends on published policies and contact restrictions.

## How it works

A conformant participant publishes a signed `deal-policy.json` at `/.well-known/deal-policy.json`. An empty or absent `inbox.accepts` value means the participant refuses proposals. Implementations must verify cryptographic signatures on inbound proposals and publish and respect a `do-not-contact.json` for both incoming and outgoing activity.

Before sending a proposal, the client runs the complete gate chain defined in section 10.3 of the specification. Each decision is written to an append-only audit log retained for at least 12 months. These controls provide the protocol’s spam-prevention and accountability model.

Discovery can use an Atom feed, HTTP `Link` headers, and other policy-linked mechanisms. Proposal data can use the W3C Verifiable Credentials format. A separate `deal-emergence.json` representation reports demand observed from traffic instead of demand explicitly declared by an agent.

## Setup and configuration

DealOracle — OracleNet Deal Discovery Protocol Reference is useful as a protocol reference when implementing a compatible service or reviewing conformance. The repository does not document an installable MCP package, startup command, client configuration, or environment variables.

The live reference deployment is hosted outside the repository. The README points to policy documents at `feedoracle.io` and `tooloracle.io`, plus auxiliary do-not-contact, Atom feed, demand, intelligence, and public-statistics endpoints on `tooloracle.io`. These hosted endpoints are reference artefacts, not evidence of a local installation procedure.

Implementers should consult `SPEC.md`, the normative schemas, and the included examples. The draft may change before publication, so compatibility should be assessed against the version under review.

## Tools and capabilities

The documented capabilities are protocol-level functions rather than named MCP tools:

- Declare offers and requirements through curated intent.
- Discover participants using opt-in policies and optional Atom broadcasts.
- Exchange cryptographically verifiable proposal data.
- Represent observed demand separately from declared intent.
- Apply do-not-contact rules and a pre-send gate chain.
- Retain append-only decisions for governance and review.

## Limitations and notes

The repository is not the live implementation, not a registry, and not a general messaging protocol. Registry files contain draft submission material only.

The specification text is licensed under CC BY 4.0. The reference implementation is linked separately through `reference/README.md`. Because the draft can change materially, implementations should not assume that the current schemas or conformance requirements are final.

_Full upstream README: https://allmcps.com/mcp/dealoracle-oraclenet-deal-discovery-protocol-reference/readme_