MCP.Market

PrivateDAO Agent Exchange MCP server

online · 100% uptime
by X-PACT·io.github.X-PACT/pdao-agent-exchange·v1.7.2·2 stars

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

B80/100grade B
What users say
No reviews yet
Be the first
Safety scan
B80/100

full report

Adoption
Growing

2 stars

Reviews

Write one

Nobody has reviewed PrivateDAO Agent Exchange yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

PrivateDAO Agent Exchange tools (17, 5 write)

write = sends, deletes, buys or posts
  • cancel_jobwrite actionFree

    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.

  • create_paid_jobwrite actionFree

    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.

  • discover_agentsFree

    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_integrationsFree

    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.

  • get_workflow_guideFree

    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.

  • job_statusFree

    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.

  • list_catalogFree

    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.

  • privatepay_challengewrite actionFree

    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_checkoutwrite actionFree

    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_job_paymentFree

    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.

  • privatepay_prepareFree

    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_settleFree

    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 settlement.

  • privatepay_statusFree

    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_verifyFree

    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 funds.

  • service_recommendationFree

    Translate a business or product objective into the most relevant PrivateDAO capabilities and a practical next step.

  • submit_paymentwrite actionFree

    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.

  • verify_receiptFree

    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.

Public scan report

scanner v0.1.10 · 2026-11-03 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1988ms20/20
  • Tool poisoning17 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 5 write-action tools with no auth3/15
  • Maintenancelast push 1 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 80/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How PrivateDAO Agent Exchange compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
80/100
higher than 60% of 4,460 AI and agents servers
Tools
17
the typical AI and agents server has 6
Tools that change things
29%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
414 ms
faster than 33% of 2,331 AI and agents servers
GitHub stars
2
more than 65% of 2,711 AI and agents servers

What its tools let an agent do: 12 read · 1 create · 3 change · 1 delete

Release history: 2 versions in the registry since 2026-08-17, latest 2026-10-24, typically one every 68 days.

Install PrivateDAO Agent Exchange in Claude Code, Cursor or VS Code

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

What the publisher says

From the PrivateDAO Agent Exchange repository's README, as published. We do not edit it. Read it on GitHub

<!-- SPDX-License-Identifier: AGPL-3.0-or-later -->

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:

discussion.

  1. Confidential Payroll - pay people without publishing salary records.
  2. Treasury Coordination - approve and reconcile sensitive spending.
  3. Private Governance - make and prove decisions without exposing every

the underlying information.

  1. Confidential Auctions - run sealed procurement and competitive bids.
  2. Blind Verification - prove that a condition was met without revealing

without publishing private fields.

  1. Record Verification - prove that a document, event, or result is valid

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:

boundaries, receipts, reconciliation, and audit-ready evidence.

  • 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

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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Grade history

  • 2026-11-03restoreD → Bscore 80: Write-action tools reachable without authentication

PrivateDAO Agent Exchange: common questions

Is PrivateDAO Agent Exchange MCP server safe?
Mostly: it is graded B (80/100). Read the PrivateDAO Agent Exchange safety report
How do I install PrivateDAO Agent Exchange?
It runs remotely at agents.privatedao.org. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does PrivateDAO Agent Exchange need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is PrivateDAO Agent Exchange maintained?
The last commit was 2 days ago (2026-11-02). The latest release is v1.7.2.
Is PrivateDAO Agent Exchange up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of PrivateDAO Agent Exchange?
Servers from other publishers that do the same job: Agent Lsp MCP server, Skillsmith MCP server and Tetrees MCP server.
How does PrivateDAO Agent Exchange compare with other AI and agents MCP servers?
safety score 80/100 (higher than 60% of 4,460 AI and agents servers); tools 17 (the typical AI and agents server has 6); tools that change things 29% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to PrivateDAO Agent Exchange

Same job from other publishers: the closest match first, then the best rated.

  • Agent Lsp
    Orchestrates language servers into 65 code-intelligence tools across 32 languages, token-optimized.
    A
  • Skillsmith
    Share agent skills across your team, scan them for risk, and track what's actually used.
    B
  • Tetrees MCP
    Own, grow and trade portable agent intelligence via TAIP/1 Packs and MCP.
    A