DealOracle — OracleNet Deal Discovery Protocol Reference

io.tooloracle由 tooloracle.io 发布官方发布者v1.1.0更新于 Oct 25, 2026

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

发布方自己的服务:Accessoracle

已验证Streamable HTTP可网页运行开发者工具商业与电商

概览

AI 生成的概览

OracleNet 协议的草案规范与参考端点,让智能体在许可前提下声明、发现并交换商业合作提案。

可以做什么
清单未列出任何工具,能力依据描述与 README。它描述一个面向自主智能体的许可式商业撮合层:声明智能体提供与寻求的内容,在选择性加入策略与退出登记表下发现对方,交换可加密验证的提案,并呈现观察到的需求。它还规定一致性要求,例如发布签名的交易策略、遵守禁止联系清单、验证签名,以及运行带只追加审计的闸门链。README 明确说明它不是冷启动外联渠道、不是通用智能体消息协议,也不是目录。
适用场景
适合评估或实现 OracleNet 交易发现协议的人,或检查某个智能体是否符合其草案规则。不适合需要现成交易或撮合工具的助手,因为未列出任何工具。
运行要求
位于 tooloracle.io 的远程 streamable HTTP 端点,要求 OAuth 认证。未声明任何软件包、环境变量或请求头。阅读规范与参考材料需要网络访问。
安装前请注意
README 称其为可能大幅变动的草案 v1.1,并说明它不是正式发布、不是代码库、也不是注册表。该协议涉及智能体之间的商业提案、签名验证以及至少保留 12 个月的只追加审计;提案可能投递到参与方的收件箱。需要 OAuth 凭据。

安装

在 SourceWeft 中

  1. 打开 控制台中的 DealOracle — OracleNet Deal Discovery Protocol Reference,将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.tooloracle%2Fdealoracle/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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.

来源:README.md,提交 9291ccb

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.1.0最新Sep 16, 2026

评分

已满足适用检查项的 75%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

    请在仓库或注册中心条目中声明许可证。

其他 Tooloracle 集成