PrivateDAO Agent Exchange

Name: PrivateDAO Agent Exchange
Author: X-PACT

作者：X-PACT版本 1.7.2i★ –i在云端运行

注册名称io.github.X-PACT/pdao-agent-exchange

安装

概览

作者提供的说明（英文原文）

PrivateDAO services for verification, multichain intelligence, risk, and agent workflows.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i3 项中通过 3 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在云端运行
传输方式: Streamable HTTP
分类: 加密货币与区块链

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：3 项中通过 3 项
在作者的服务器上运行：你向它提出的内容会经过他们的服务器。
可以做 17 件事（工具） get_workflow_guide, list_catalog, discover_agents, get_provider_integrations …
注册中心没有列出需要填写的密钥。

你需要

在云端运行无需安装任何东西，通过互联网连接

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

适用于网页版、桌面版和手机版 Claude：

打开 Settings → Connectors
点击 Add custom connector
粘贴下面的地址，然后点击 Add
如果要求登录，请登录作者的服务

https://agents.privatedao.org/mcp

在终端中运行这条命令

claude mcp add --transport http pdao-agent-exchange https://agents.privatedao.org/mcp

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "pdao-agent-exchange": {
      "url": "https://agents.privatedao.org/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "pdao-agent-exchange": {
      "type": "http",
      "url": "https://agents.privatedao.org/mcp"
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

ChatGPT 只能连接互联网上的服务器：

打开网页版 ChatGPT → Settings → Connectors (Apps)
点击 Create 或 Add（部分套餐需要先在 Advanced 中开启 Developer mode）
粘贴下面的地址，起个名字，然后保存
如果要求登录，请登录作者的服务

https://agents.privatedao.org/mcp

菜单名称可能因套餐和版本不同而略有差异。

你的选择通过 Cookie 保存在这台设备上，无需账户。

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

工具名称和描述与服务器在 2026年11月7日报告的完全一致。这些内容由作者撰写，不是我们写的；我们以纯文本形式显示。

get_workflow_guide
Return the overview, execution, or payment workflow guide. Use this instead of separate guide tools when you need lifecycle context; it is free, read-only, and returns the selected next steps without executing or paying.
list_catalog
List services, products, external capabilities, or network metadata with optional filters. This is free and read-only; use discover_agents for a task-specific match and create_paid_job only after selecting a service.
discover_agents
Match a natural-language requirement or structured capabilities to first-party services and registered agents. Returns ranked matches without side effects or cost; use list_catalog for exact schemas and prices, and create_paid_job to execute selected paid work.
get_provider_integrations
Return provider roles and integration metadata for planning. This is free and read-only; use list_catalog for purchasable capabilities and discover_agents for matching.
service_recommendation
Translate a business or product objective into the most relevant PrivateDAO capabilities and a practical next step.
privatepay_status
Read the current PrivatePAY x402 readiness, MagicBlock private-rail configuration, facilitator state, PDAO entry requirement, and public-chain privacy boundary. Call this first; it is free and read-only, creates no challenge, and never moves funds.
privatepay_challenge
Create a fresh PrivatePAY x402 v2 challenge for a resource and quoted USDC amount. Call this before privatepay_verify; it returns exact payment requirements and the PDAO private-settlement rule, but never signs, broadcasts, or charges a wallet.
privatepay_checkout
Create a MagicBlock PrivatePAY checkout or request the payment-required challenge for an existing checkout. Use this to begin a private checkout instead of create_paid_job with direct USDC; it returns commercial terms only and never signs, broadcasts, or moves funds.
privatepay_prepare
Prepare an unsigned MagicBlock deposit, private transfer, or withdrawal for a local wallet to inspect and sign. Call this after privatepay_checkout and before wallet authorization; PrivateDAO never receives a private key and this tool never broadcasts.
privatepay_verify
Verify an x402 v2 PrivatePAY payload through the configured facilitator against the exact original requirements. Call this after privatepay_challenge or privatepay_checkout and before privatepay_settle; it is read-only, fail-closed, and returns redacted evidence without spending
privatepay_settle
Settle an already verified x402 v2 PrivatePAY payload through the configured facilitator and return redacted settlement evidence. Call this only after privatepay_verify with unchanged requirements; this is the payment-moving action and may create facilitator-side or on-chain sett
privatepay_job_payment
Apply a finalized PrivatePAY x402 payment to an existing paid job and execute it once. Use this instead of submit_payment for a job created with payment_mode=privatepay; it consumes supplied payment proof, may settle funds, and returns workflow evidence.
verify_receipt
Verify an asset/record or retrieve and validate a PrivateDAO receipt. Returns structured evidence and hashes; it is free and read-only, never pays or executes work, and replaces the separate basic, receipt, and get-receipt paths.
create_paid_job
Create a selected paid PrivateDAO capability request and return an immediate result or exact quote-first payment intent. Use discover_agents or list_catalog first; payment_mode=privatepay starts the PrivatePAY flow, while direct uses ordinary USDC. This call never spends funds.
submit_payment
Confirm an authorized payment reference for a selected request and return the payment/execution result. Use this after create_paid_job and only with the exact returned quote; it may write payment state and never accepts a guessed amount.
job_status
Read the current state, exact payment intent, result, or receipt reference for a request. Poll this after create_paid_job, privatepay_job_payment, or submit_payment; it is free and read-only, never retries payment, and never executes work again.
cancel_job
Cancel an unpaid pending request before execution and return its updated status. It records cancellation only, never spends or refunds funds, and must not be used after payment or execution has started.

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 X-PACT 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
✓ 通过
端点有响应
在 436 毫秒内响应（HTTP 200）
– 不适用
使用 OAuth 登录
无需登录
✓ 通过
工具描述中没有隐藏指令
已读取 17 个工具描述，未发现针对 AI 的隐藏指令

与“加密货币与区块链”中的其他服务器比较i

星标数多于此分类中其他 1612 个服务器的 0%
发布到注册中心的时间比此分类中其他 1612 个服务器的 78% 更新
基础检查结果等于或优于此分类中其他 1612 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

PrivateDAO Agent Exchange 安全吗？

它在 3 项适用的基础检查中通过了 3 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

注册中心没有列出必需的密钥，不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端？

它在作者的云端运行。通过互联网连接，无需安装，但你发送的内容会经过作者的服务器。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（1.7.2）于14天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接，所以接受远程 MCP 服务器的应用也可以使用，例如开启开发者模式的 ChatGPT。

有什么可以替代它？

同一分类中有：NEMO x402 Micro-Services, Crypto Derivatives Data: Perp Funding Rates, Open Interest, Basis, IV, Agent Data Tools: Prices and DeFi

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

NEMO x402 Micro-Services

作者：floortomproductions-droid

34 paid tools: site/SEO, weather, crypto+markets, podcasts, YouTube, Polymarket. x402/MPP/Stripe.

在云端运行今天更新

安装

Crypto Derivatives Data: Perp Funding Rates, Open Interest, Basis, IV

作者：derivs.duoleads.com

Perp funding rates, open interest, futures basis, IV, liquidations, order books on 8 exchanges

在云端运行今天更新

安装

Agent Data Tools: Prices and DeFi

作者：Nutshell2000

50 tools: token prices, wallet and contract risk, liquidity pools, FX. 25 free calls.

在云端运行今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

PrivateDAO

Private decisions. Verifiable outcomes.

PrivateDAO is a privacy-first operating layer for organizations that need to run sensitive work without making every detail public. It helps teams define rules, run workflows, approve actions, execute through the appropriate infrastructure, and share evidence of the outcome.

PrivateDAO is built for organizations entering Web3 as well as organizations that never intend to become crypto companies. A business can keep its existing operating model and add verifiable Web3 capability only where it is useful: private payroll, controlled treasury actions, governance, procurement, and verification. Privacy is the product principle; blockchain, wallets, and cryptography are execution infrastructure behind that principle.

Product direction

The project is organized around six core organizational workflows:

Confidential Payroll - pay people without publishing salary records.
Treasury Coordination - approve and reconcile sensitive spending.
Private Governance - make and prove decisions without exposing every discussion.
Confidential Auctions - run sealed procurement and competitive bids.
Blind Verification - prove that a condition was met without revealing the underlying information.
Record Verification - prove that a document, event, or result is valid without publishing private fields.

These workflows share the PrivateDAO Kernel, policy controls, execution adapters, receipts, and reconciliation boundaries. The public product surface is intentionally simple; technical network details remain available for builders, reviewers, and operators.

Next milestone: PDAO Wallet

The next product milestone is PDAO Wallet, an account and policy layer for organizations rather than a single consumer wallet. The planned wallet suite will support:

corporate accounts for the six core workflows and institution management;
an autonomous AI wallet for bounded, policy-controlled agent operations;
a B2B wallet for organizations, counterparties, and service settlement;
role-based permissions, approval thresholds, spending policies, signing boundaries, receipts, reconciliation, and audit-ready evidence.

PDAO Wallet will be developed as a capability layer above the PrivateDAO Kernel. It will remain independent from any single chain or provider, while each network adapter is required to provide real implementation and evidence before it is described as supported.

Quantum-security roadmap

PrivateDAO plans a quantum-resilience layer above the Kernel and PDAO Wallet. This work will evaluate current post-quantum and hybrid cryptographic libraries, key-agility patterns, signing policies, migration paths, and hardware-backed execution as the standards and production libraries mature. The implementation will use maintained, independently reviewed libraries and explicit compatibility gates. This roadmap is not a claim that PrivateDAO is currently quantum-safe, certified, or externally audited for post-quantum security.

Ecosystem programs and technology partners

PrivateDAO is participating in the following programs based on accepted program communications and the partnership records maintained by the project owner:

Organization	Program or relationship	PrivateDAO use in this project
MongoDB	MongoDB Partner Program and MongoDB for Startups	Evidence-history storage, search, and startup infrastructure validation
IBM	IBM Partner Plus	Enterprise AI and watsonx integration evaluation
AMD	AMD AI Developer Program	AI workload, accelerator, and performance validation
Intel	Intel Partner Plus	OpenVINO inference and performance validation
GitHub	GitHub Developer Program	Developer tooling, repository provenance, and integration testing
DigitalOcean	DigitalOcean developer infrastructure access	Cloud compute, storage, and deployment experimentation

These program relationships do not by themselves mean endorsement of every PrivateDAO product, certification, customer reference, grant award, or joint commercial offering. Product capabilities remain subject to the evidence and status recorded in the repository. The supporting acceptance emails and public announcements are retained by the project owner; this repository records the program names and their intended technical role without reproducing private correspondence.

The PDAO Wallet roadmap will use these relationships for storage, AI inference, hardware/performance testing, developer tooling, and operational validation as the relevant integrations are enabled. See the ecosystem program record for the technical scope and disclosure boundary.

Evidence language

This repository distinguishes three states:

Verified - backed by current source, runtime, or independently checkable execution evidence.
Planned - an approved product or engineering milestone that is not yet a completed production capability.
Historical - retained material that explains prior work but is not a current product claim.

Network configuration, an address, a UI label, or a passing unit test alone is not evidence of a live product execution path. See the capability matrix and linked evidence for the status of each network and workflow.

Live Testnet program: EP9xE8MJZ6FfyEwLqns6HDdUZBknEa7WGYs1Jzsecuva

Historical Devnet proof registry program: 5AhUsbQ4mJ8Xh7QJEomuS85qGgmK9iNvFqzF669Y7Psx (docs/proof-registry.json); this is retained as provenance and is not the current Testnet deployment.

An organization does not need to become a Web3 or crypto company to use PrivateDAO. A company, institution, financial team, DAO, data provider, or Web3 operator can start with a familiar business workflow and add wallets, networks, settlement, or verifiable Web3 capability only where it creates value.

What PrivateDAO provides

Private operations

Confidential Payroll - prepare payroll, apply tax and deduction rules, collect approvals, settle through a supported private-payment path, and produce a verifiable result without exposing employee records.
Treasury Coordination - manage spending requests, budgets, approvals, execution, reconciliation, and evidence for sensitive financial operations.
Private Governance - coordinate proposals, committees, delegation, and decisions while keeping sensitive discussion and voting context private where the workflow requires it.

Private transactions and markets

Confidential Auctions - protect competing bids until the agreed close, then produce a fair and checkable result.
Private Settlement Workflows - move an approved operation through a supported settlement provider and retain a receipt with clear lifecycle status.

Verification

Blind Verification - prove that a condition or policy was satisfied without revealing the underlying data.
Record Verification - create a shareable, tamper-evident record for a document, event, approval, or business result without publishing private fields.
Private Identity Verification - support selective confirmation of identity, entity, jurisdiction, or authorization requirements while keeping the source material private.

Agent and community products

PrivateDAO Agent Exchange - an MCP-compatible service marketplace for verification, blockchain intelligence, market context, agent discovery, and verifiable receipts.
PDAO Worlds - an independent community game about privacy, trust, evidence, and coordination. It is a separate product and does not define the commercial workflow runtime.

Community

PDAO Worlds is the community layer for education, experimentation, and shared participation around PrivateDAO. It is separate from the organization workflow products and does not change the evidence or security requirements of the Kernel, PDAO Wallet, or settlement paths.

PDAO token surface

The current published token surface is documented in docs/pdao-token.md and the machine-readable attestation is docs/pdao-attestation.generated.json. The documented Testnet governance token is PDAO with mint DFYvBdivHCe4bSErgCiKm2RhwGEcZYbBPFQzLNr37Bie and a published initial supply of 1,000,000 PDAO. These references describe the current evidence surface; they do not claim Mainnet launch, market liquidity, or speculative returns.

How it works

Choose the workflow

-> define rules and participants -> run privately -> approve and execute -> reconcile the result -> share only the evidence that others need

The customer-facing workflow comes first. Wallets, providers, networks, RPC clients, cryptography, and settlement details remain behind the product boundary until execution requires them.

Agent Exchange

The production Agent Exchange is available at:

Marketplace: https://agents.privatedao.org/
MCP endpoint: https://agents.privatedao.org/mcp
Connection hub: https://agents.privatedao.org/connect
Agent card: https://agents.privatedao.org/.well-known/agent-card.json

The endpoint is designed for standard MCP clients and exposes discovery, verification, intelligence, agent matching, job lifecycle, payment-aware receipts, and marketplace capabilities. Free discovery and read-only tools are separate from paid service execution. A client must use the published schemas and receipts; a frontend response is not payment proof.

Current payment and network claims are capability-specific. Where a service requires payment, the active payment rail and supported target network are returned by the service catalog. Do not infer that every advertised target network has the same execution or payment capability.

Kernel and runtime architecture

The current separation between the six enterprise products and the external Agent Exchange is documented in docs/architecture/enterprise-kernel-boundary-20261014.md.

The repository contains provider-neutral runtime contracts in packages/privatedao-runtime. The Kernel and Protocol layers provide common boundaries for:

product capabilities and permissions;
provider selection and lifecycle states;
wallet-signing boundaries;
preparation, submission, confirmation, and receipts;
reconciliation, idempotency, normalized errors, and telemetry;
MCP, REST, SDK, and agent-facing contracts.

Network-specific transaction construction belongs behind adapters. The runtime package does not store private keys, contain a wallet signer, or invent a successful receipt. A configured network is not considered supported merely because it appears in a UI or configuration file; it needs a real adapter and independent evidence.

Review and operating references

The repository keeps security, release, runtime, and operating evidence available for reviewers. These documents describe engineering evidence and boundaries; they are not claims of incorporation, certification, partnership, or mainnet readiness unless the referenced document says so explicitly.

Security review
Threat model
Security coverage map
Failure modes
Replay analysis
Live proof
Devnet release manifest
Verification gates
[Mainnet readiness](do

只显示了开头部分；其余内容请在仓库中阅读

PrivateDAO Agent Exchange

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“加密货币与区块链”中的其他服务器比较i

常见问题

替代选择

NEMO x402 Micro-Services

Crypto Derivatives Data: Perp Funding Rates, Open Interest, Basis, IV

Agent Data Tools: Prices and DeFi

作者的 README

PrivateDAO

Product direction

Next milestone: PDAO Wallet

Quantum-security roadmap

Ecosystem programs and technology partners

Evidence language

What PrivateDAO provides

Private operations

Private transactions and markets

Verification

Agent and community products

Community

PDAO token surface

How it works

Agent Exchange

Kernel and runtime architecture

Review and operating references