Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

PrivateDAO Agent Exchange

REMOTE · AGENTS.PRIVATEDAO.ORG · SCANNED OCT 4

Solana Mainnet verification, intelligence, machine receipts, and agent logistics through MCP.

+3 this week 63 Trust /100

Recent critical change

Authorization (22 Sept 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability51
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 1152 tokens (~57/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage83
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 49% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 20 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the PrivateDAO Agent Exchange MCP server?

PrivateDAO Agent Exchange is a hosted endpoint at https://agents.privatedao.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agents.privatedao.org

# add to Claude Code
claude mcp add --transport http x-pact-pdao-agent-exchange 'https://agents.privatedao.org/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "x-pact-pdao-agent-exchange": {
      "url": "https://agents.privatedao.org/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "x-pact-pdao-agent-exchange": {
      "type": "http",
      "url": "https://agents.privatedao.org/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.x-pact-pdao-agent-exchange]
url = "https://agents.privatedao.org/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "x-pact-pdao-agent-exchange": {
      "type": "remote",
      "url": "https://agents.privatedao.org/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add x-pact-pdao-agent-exchange --url 'https://agents.privatedao.org/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  x-pact-pdao-agent-exchange:
    url: "https://agents.privatedao.org/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "x-pact-pdao-agent-exchange": {
      "Transport": "http",
      "Url": "https://agents.privatedao.org/mcp"
    }
  }
}
# add to Vellum
assistant mcp add x-pact-pdao-agent-exchange -t streamable-http -u 'https://agents.privatedao.org/mcp'
// mcp.json
{
  "mcpServers": {
    "x-pact-pdao-agent-exchange": {
      "type": "http",
      "url": "https://agents.privatedao.org/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 29 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Sept 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +1
    • New tool “seller_retire”, which the server declares destructive security
    • Tool “pdao_services” rewrote its description, which is the text the model reads security
    • Schema quality: 519 → 1018 ▼ functional
    • Tool coverage: 50% → 41% ▼ functional
    • Schema quality: poor → fair functional
    • Server version: 1.4.0 → 1.6.0 functional
    • New tool “exchange_overview” functional
    • New tool “execution_guide” functional
    • New tool “external_services” functional
    • New tool “payment_guide” functional
    • New tool “provider_integrations” functional
    • New tool “seller_replace_endpoint” functional
    • New tool “seller_update_services” functional
    • New tool “service_recommendation” functional
    • “register_agent” added an optional parameter “acceptedAssets” cosmetic
    • “register_agent” added an optional parameter “agentId” cosmetic
    • “register_agent” added an optional parameter “commercialServices” cosmetic
    • “register_agent” added an optional parameter “ownerToken” cosmetic
    • “register_agent” added an optional parameter “payout” cosmetic
  • 22 Sept 26 +1
    • Authorization: unverified → fail ▼ critical
    • Tool “submit_payment” is now declared destructive security
    • Stability: unverified → 0.03 ▲ functional
    • Tool “agent_match” changed its title: PrivateDAO agent_match cosmetic
    • Tool “create_paid_job” changed its title: PrivateDAO create_paid_job cosmetic
    • Tool “get_receipt” changed its title: PrivateDAO get_receipt cosmetic
    • Tool “job_status” changed its title: PrivateDAO job_status cosmetic
    • Tool “logistics_request” changed its title: PrivateDAO logistics_request cosmetic
    • Tool “network_stats” changed its title: PrivateDAO network_stats cosmetic
    • Tool “pdao_services” changed its title: PrivateDAO pdao_services cosmetic
    • Tool “register_agent” changed its title: PrivateDAO register_agent cosmetic
    • Tool “search_agents” changed its title: PrivateDAO search_agents cosmetic
    • Tool “submit_payment” changed its title: PrivateDAO submit_payment cosmetic
    • Tool “verify_basic” changed its title: PrivateDAO verify_basic cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 9 Oct 2026 · Probed https://agents.privatedao.org/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agents.privatedao.org CN=Amazon RSA 2048 M01,O=Amazon,C=US 16 Aug 2026 1 Mar 2027 RSA 2048 SHA256-RSA 747a96e1011a4cb9fc31bfbd4c81487
SANs: agents.privatedao.org
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agents.privatedao.org. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
org. present 26974 8 Verified
privatedao.org. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agents.privatedao.org/mcp Verified 200
http (plaintext) http://agents.privatedao.org/mcp HTTPS enforced
MCP tools · 20 exposed · ~1,152 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
agent_match ~46

Free registry discovery and capability matching. Use create_paid_job for the paid agent.match service.

NameTypeReqDescription
capabilitiesarrayyes–
networkstring–Canonical network or accepted alias.

No output schema declared.

No examples provided.

create_paid_job ~34

PrivateDAO create_paid_job

NameTypeReqDescription
inputobject–Service-specific JSON input.
service_idstringyes–

No output schema declared.

No examples provided.

exchange_overview ~50

Start here. Explain the PrivateDAO Agent Exchange as a service economy for AI agents: discover a capability, request it, receive a quote when paid, execute read-only evidence work, and verify the receipt.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

execution_guide ~41

Explain how to create a free or paid job, interpret 402 payment_intent, submit finalized payment proof, poll status, retrieve a receipt and verify it.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

external_services ~27

PrivateDAO external_services

NameTypeReqDescription
limitinteger––
qstring––

No output schema declared.

No examples provided.

get_receipt ~23

PrivateDAO get_receipt

NameTypeReqDescription
receipt_idstringyes–

No output schema declared.

No examples provided.

job_status ~21

PrivateDAO job_status

NameTypeReqDescription
job_idstringyes–

No output schema declared.

No examples provided.

logistics_request ~70

PrivateDAO logistics_request

NameTypeReqDescription
assetstring––
capabilitystringyes–
deadlinestring––
maxPricenumber––
networkstring–Canonical network or accepted alias.
preferredProtocolsarray––
requirementsobject––

No output schema declared.

No examples provided.

network_stats ~13

PrivateDAO network_stats

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

payment_guide ~42

Explain the quote-first Solana Mainnet USDC payment flow. Never infer an amount, never pay before a payment_intent, and never request a private key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

pdao_services ~35

Return the complete current catalog with service IDs, customer value, category, pricing, inputs, outputs, target networks and payment behavior.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

provider_integrations ~56

Explain what IBM watsonx, Intel OpenVINO, MongoDB, GitHub, ChatGPT, Claude, Grok, OpenClaw and the PrivateDAO Kernel add to the ecosystem, with relationship disclosures and safe provider status.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

register_agent ~341

PrivateDAO register_agent

NameTypeReqDescription
acceptedAssetsarray––
accepted_assetsarray–Snake-case compatibility alias for acceptedAssets.
agentIdstring–Stable seller identity for updates and endpoint replacement.
agent_idstring–Snake-case compatibility alias for agentId.
allowedToolsarray––
allowed_toolsarray–Snake-case compatibility alias for allowedTools.
commercialServicesarray–Explicit per-tool commercial metadata; prices are never inferred.
commercial_servicesarray–Snake-case compatibility alias for commercialServices.
endpointstring–Compatibility alias for mcpUrl.
forceRefreshboolean–Force a fresh MCP handshake instead of returning an existing healthy registration.
force_refreshboolean–Snake-case compatibility alias for forceRefresh.
mcpUrlstring–Public HTTPS MCP endpoint
mcp_urlstring–Compatibility alias for mcpUrl.
namestring––
networksarray–Explicitly declared supported networks; aliases are normalized.
ownerTokenstring–Seller ownership token; returned only once on first registration.
owner_tokenstring–Snake-case compatibility alias for ownerToken.
payoutobject––
persistUnavailableboolean–Persist Unavailable after a failed health check; never marks it connected
persist_unavailableboolean–Snake-case compatibility alias for persistUnavailable.
protocolstring––
sellerIdstring–Compatibility alias for agentId.
seller_idstring–Snake-case compatibility alias for agentId.
tagsarray––

No output schema declared.

No examples provided.

search_agents ~51

PrivateDAO search_agents

NameTypeReqDescription
capabilitystring––
limitinteger––
networkstring–Canonical network or accepted alias.
qstring–Free-text registry search.

No output schema declared.

No examples provided.

seller_replace_endpoint ~40

PrivateDAO seller_replace_endpoint

NameTypeReqDescription
agent_idstringyes–
mcp_urlstringyes–
owner_tokenstringyes–

No output schema declared.

No examples provided.

seller_retire ~38

PrivateDAO seller_retire

NameTypeReqDescription
agent_idstringyes–
owner_tokenstringyes–
reasonstring––

No output schema declared.

No examples provided.

seller_update_services ~53

PrivateDAO seller_update_services

NameTypeReqDescription
accepted_assetsarray––
agent_idstringyes–
owner_tokenstringyes–
payoutobject––
servicesarrayyes–

No output schema declared.

No examples provided.

service_recommendation ~65

Map a natural-language task to the best available PrivateDAO services. Use this before create_paid_job when the user has not named a service ID.

NameTypeReqDescription
networkstring–Optional target network constraint.
taskstringyesNatural-language task the agent wants to accomplish.

No output schema declared.

No examples provided.

submit_payment ~34

PrivateDAO submit_payment

NameTypeReqDescription
job_idstringyes–
signaturestringyesFinalized Solana transaction signature.

No output schema declared.

No examples provided.

verify_basic ~72

PrivateDAO verify_basic

NameTypeReqDescription
assetstring–Alias for mint.
expected_digeststring–Optional expected canonical digest.
mintstring–Solana mint address to inspect.
networkstring–Optional target network identifier.
recordobject–Structured record to hash and verify.

No output schema declared.

No examples provided.

Common questions

What is the PrivateDAO Agent Exchange MCP server?

PrivateDAO Agent Exchange is an MCP server listed in the public MCP registry as io.github.X-PACT/pdao-agent-exchange. Solana Mainnet verification, intelligence, machine receipts, and agent logistics through MCP. This page covers its hosted endpoint (https://agents.privatedao.org/mcp).

Is the PrivateDAO Agent Exchange MCP server safe to use?

PrivateDAO Agent Exchange scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the PrivateDAO Agent Exchange MCP server expose?

PrivateDAO Agent Exchange exposes 20 tools: exchange_overview, pdao_services, service_recommendation, provider_integrations, payment_guide, and 15 more. Their descriptions and schemas cost roughly 1,152 tokens of context every time the server is loaded.

Does the PrivateDAO Agent Exchange MCP server require authentication?

No. We connected to PrivateDAO Agent Exchange without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the PrivateDAO Agent Exchange MCP server still maintained?

PrivateDAO Agent Exchange is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.