DealOracle — OracleNet Deal Discovery Protocol Reference

io.tooloraclePublished by tooloracle.ioOfficial publisherv1.1.0Updated Oct 25, 2026

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

The publisher's own server: Accessoracle

VerifiedStreamable HTTPWeb executableDeveloper ToolsBusiness & Commerce

Overview

AI-generated overview

A draft specification and reference endpoint for OracleNet, a permissioned deal-discovery protocol that lets agents declare, discover and exchange commercial, a

What you can do
The manifest lists no tools, so capabilities come from the description and README. It documents a permissioned commercial matching layer for autonomous agents: declaring what an agent offers and seeks, discovering counterparties under opt-in policies and opt-out registries, exchanging cryptographically verifiable proposals, and surfacing observed demand. It also sets conformance rules such as publishing a signed deal policy, honouring do-not-contact lists, verifying signatures and running a gate chain with an append-only audit. The README states it is not a cold-outreach channel, not a general agent messaging protocol and not a directory.
When to use it
For people evaluating or implementing the OracleNet deal-discovery protocol, or checking whether an agent conforms to its draft rules. Not for assistants that need ready-made deal or matching tools, since no tools are listed.
Requirements
A remote streamable HTTP endpoint at tooloracle.io with OAuth authentication required. No packages, environment variables or headers are declared. Reading the specification and reference artefacts needs network access.
Before you install
The README calls this a Draft v1.1 that may change materially and says it is not a published release, not a code library and not a registry. The protocol involves commercial proposals between agents, signature verification and an append-only audit retained at least 12 months; proposals may be delivered to participating inboxes. OAuth credentials are required.

Installation

In SourceWeft

  1. Open DealOracle — OracleNet Deal Discovery Protocol Reference in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.tooloracle%2Fdealoracle/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "dealoracle-oraclenet-deal-discovery-prot": {
      "type": "http",
      "url": "https://tooloracle.io/deal/mcp/"
    }
  }
}

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.

Source: README.md at commit 9291ccb

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.1.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Tooloracle integrations

Accessoracle

io.tooloracleOfficial publisher

AccessOracle is a remote MCP server with 10 tools for tracking IAM and privileged access compliance, including MFA coverage, recertification, SoD conflicts and,

Streamable HTTPWeb executable
Security & Monitoring10 toolsOct 24, 2026

Zkevidenceoracle

io.tooloracleOfficial publisher

A remote MCP server offering 14 zero-knowledge proof tools for compliance evidence, including Groth16 and PLONK.

Streamable HTTPWeb executable
Security & MonitoringNot indexed yetOct 24, 2026

Yieldoracle

io.tooloracleOfficial publisher

Remote DeFi yield intelligence server that gives an assistant access to a large pool dataset with risk-adjusted APY and RWA yield data.

Streamable HTTPWeb executable
FinanceNot indexed yetOct 24, 2026

Trustlayer

io.tooloracleOfficial publisher

A remote MCP server offering ten cross-server trust tools for signing, anchoring and verifying data.

Streamable HTTPWeb executable
Security & MonitoringNot indexed yetOct 24, 2026

Tonoracle

io.tooloracleOfficial publisher

A remote MCP server giving assistants 11 read-only TON blockchain tools for jettons, wallets, DeFi yields, protocols, stablecoins, bridges and network stats.

Streamable HTTPWeb executable
FinanceNot indexed yetOct 24, 2026