PrivateDAO Agent Exchange

Name: PrivateDAO Agent Exchange
Author: X-PACT

by X-PACTversion 1.7.2i★ –iRuns in the cloud

Registry nameio.github.X-PACT/pdao-agent-exchange

Install

Overview

Description from the maker (original English)

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

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

User voiceiNo reviews yetReviews open together with accounts in a later step
Our basic checksi3 of 3 passedChecked from public information; code not scanned yet
UsageiNot measured yet★ –

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

Connection: Runs in the cloud
Transport: Streamable HTTP
Category: Crypto & blockchain

Install

Pick the AI app you use, then copy the settings.

Before you install

Basic checks: 3 of 3 passed
Runs on the maker’s server: what you ask it goes through their server.
Can do 17 things (tools) get_workflow_guide, list_catalog, discover_agents, get_provider_integrations …
The registry lists no key to fill in.

You need

Runs in the cloudNothing to install; it connects over the internet

Which app do you use?

ClaudeClaude CodeCursorVS CodeChatGPT

Pick your app above. We remember it, so next time the button says “Install in …”.

Works in Claude on the web, desktop and mobile:

Open Settings → Connectors
Press Add custom connector
Paste the address below and press Add
If it asks you to sign in, sign in with the maker

https://agents.privatedao.org/mcp

Run this in your terminal

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

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

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

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

ChatGPT connects only to servers on the internet:

Open ChatGPT on the web → Settings → Connectors (Apps)
Press Create or Add (some plans need Developer mode under Advanced first)
Paste the address below, give it a name and save
If it asks you to sign in, sign in with the maker

https://agents.privatedao.org/mcp

Menu names can differ slightly by plan and over time.

Your choice stays on this device in a cookie; no account needed.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Tool names and descriptions exactly as the server reported them on Nov 7, 2026. The maker wrote them, not us; we show them as plain text.

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.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026

✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account X-PACT, which owns the repo
… Not checked yet
Still maintained
We have not read this repo from GitHub yet
… Not checked yet
Has a licence
We have not read this repo from GitHub yet
✓ Pass
Endpoint responds
Responded in 436 ms (HTTP 200)
– Not applicable
Sign-in with OAuth
No sign-in needed
✓ Pass
No hidden instructions in tool descriptions
Read 17 tool descriptions and found no hidden instructions to the AI

Compared with others in Crypto & blockchaini

More stars than 0% of the other 1611 servers in this category
Published to the registry more recently than 79% of the other 1611 servers in this category
Basic checks equal to or better than 100% of the other 1611 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is PrivateDAO Agent Exchange safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.

Is it still maintained?

The GitHub repo last changed –, and the latest version (1.7.2) reached the registry 14 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.

What can I use instead?

In the same category: Crypto Derivatives Data: Perp Funding Rates, Open Interest, Basis, IV, Agent Data Tools: Prices and DeFi, Agent Data Tools: Chain data

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

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

by derivs.duoleads.com

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

Runs in the cloudUpdated today

Install

Agent Data Tools: Prices and DeFi

by Nutshell2000

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

Runs in the cloudUpdated today

Install

Agent Data Tools: Chain data

by Nutshell2000

360 tools: balances, blocks, gas, txs and logs on 5 EVM chains, plus Bitcoin. 25 free calls.

Runs in the cloudUpdated today

Install

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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

Only the beginning is shown; read the rest in the repo

PrivateDAO Agent Exchange

Overview

PopNx MCP’s three pillars

What you can do with it

Install

Before you install

What it can do

Basic checksi

Maker matches the repo

Still maintained

Has a licence

Endpoint responds

Sign-in with OAuth

No hidden instructions in tool descriptions

Compared with others in Crypto & blockchaini

Common questions

Alternatives

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

Agent Data Tools: Prices and DeFi

Agent Data Tools: Chain data

README from the maker

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