Home / MCP registry index / io.github.X-PACT/pdao-agent-exchange

PrivateDAO Agent Exchange

io.github.X-PACT/pdao-agent-exchange in the official MCP registry. Endpoint https://agents.privatedao.org/mcp. Source: github.com/X-PACT/PrivateDAO.

The registry describes it as: Solana Mainnet verification, intelligence, machine receipts, and agent logistics through MCP.

We read its 27 tools on 2026-10-21. Nothing in them matched our tool-poisoning rules.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Tools it advertises

exchange_overview pdao_services product_catalog service_recommendation provider_integrations payment_guide execution_guide privatepay_status privatepay_challenge privatepay_prepare privatepay_verify privatepay_settle verify_basic receipt_verify create_paid_job submit_payment job_status get_receipt search_agents register_agent agent_match logistics_request network_stats external_services seller_update_services seller_replace_endpoint seller_retire

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-x-pact-pdao-agent-exchange/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-x-pact-pdao-agent-exchange)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.