ZADP / AGENT DISCOVERY
Connect your AI agent.
Discover signed services on Zcash through the Model Context Protocol.
MCP SERVER URL
https://mcp.zadp.io/mcp- Streamable HTTP
- No login
- Read-only
For AI clients, not a web page. Opening this URL in a browser may return HTTP 405.
01 / CONNECT
Choose your AI client.
Add ZADP, then enable its discovery tools in your conversation.
Claude · remote connector
- Open Customize → Connectors in Claude.
- Choose + Add → Add custom connector. Name it ZADP and enter
https://mcp.zadp.io/mcp. - Continue with No sign in, then add the connector. Enable it for your conversation.
The remote connector works through your Claude account on web and Desktop; it is separate from local Desktop extensions and their JSON configuration. Organization administrators may need to add it first. Availability and labels depend on your plan and version.
Cursor · remote MCP server
In the desktop editor, merge this entry into .cursor/mcp.json for your project, or ~/.cursor/mcp.json globally. Preserve your existing servers.
{
"mcpServers": {
"zadp": {
"url": "https://mcp.zadp.io/mcp"
}
}
}Cursor's remote URL configuration selects the HTTP transport; no token or custom headers are required. Enable ZADP in your MCP settings. Cloud/web and managed team setup use their own configuration controls; a local file does not automatically configure them.
Other MCP clients
Add a remote server using https://mcp.zadp.io/mcp, Streamable HTTP, with no authentication. Let your MCP SDK handle protocol headers.
Generic JSON configuration example
Use only if your client documents this format; names and transport settings vary.
{
"mcpServers": {
"zadp": {
"type": "http",
"url": "https://mcp.zadp.io/mcp"
}
}
}Client configuration and compatibility
Supported MCP versions: 2026-07-28 and 2025-11-25. Both were tested against production using the official MCP Inspector. The current version is stateless; older SSE-only clients are unsupported.
Setup guidance was checked against official client documentation on 15 October 2026. This is not an end-to-end certification of every Claude or Cursor version. If tool discovery fails, check your client's protocol support and organization settings.
02 / TRY IT
Your first discovery.
ILLUSTRATIVE EXAMPLE · NOT LIVE
- USER
- Find text summarization services on Zcash.
- AGENT
- Calling
zadp_search_offers - RESULT
- Searching public ZADP Offers...
- The agent discovers a suitable Offer, if one is available.
- It reads the details using
zadp_get_offer. - It gives you a canonical zadp.io Offer link.
This example makes no request and does not represent a real Offer. Discovery never executes a purchase or payment.
03 / TOOL REFERENCE
Four tools. Read-only.
Expand a tool for inputs, an example and its limits.
zadp_search_offersFind public service offers.
Inputs
query: optional string, up to 256 UTF-8 bytes. board_id: optional identifier, 1–128 ASCII letters, digits, hyphens or underscores. capability: optional nonempty string, up to 128 bytes. limit: optional integer 1–100; default 20.
Example invocation
Call zadp_search_offers with:
{"board_id":"ai-services","capability":"text.summarize","limit":10}Important limits
Returns titles, descriptions, fixed prices where present, approximate published service areas, expiry, endpoint ownership status, purchase eligibility and canonical links. Hosted caps results at 1,000; MCP returns at most 100. Check completeness flags before treating results as exhaustive.
zadp_get_offerInspect one signed Offer.
Inputs
board_id and offer_id: required identifiers, 1–128 ASCII letters, digits, hyphens or underscores. seller: optional string, up to 64 bytes; an ed25519: public identity containing a Base64 32-byte key. Use the exact identity from search.
Example invocation
Call zadp_get_offer with:
{"board_id":"BOARD_FROM_SEARCH","offer_id":"ID_FROM_SEARCH"}Important limits
The example uses placeholders, not a real Offer. Include seller from search if needed to disambiguate. Returns signed fields, chain provenance and separate unsigned Hosted metadata. Unavailable or ambiguous lookups fail safely; this is not independent signature verification.
zadp_list_boardsExplore active public boards.
Inputs
No inputs: pass an empty object.
Example invocation
Call zadp_list_boards with:
{}Important limits
Returns public descriptions, network and scanned heights. No private BoardDescriptors, addresses or viewing keys are exposed.
zadp_get_network_statusRead discovery service status.
Inputs
No inputs: pass an empty object.
Example invocation
Call zadp_get_network_status with:
{}Important limits
Returns liveness, versions and board scan cursors. Liveness and scanned height are not proof of network synchronization; network_sync_verified is false.
Exact schemas and public resources
Your client discovers the implemented JSON Schemas through MCP tool discovery. Unknown arguments and control characters are rejected. Optional inputs can be omitted or null. No buyer GPS, wallet keys or arbitrary fetch URLs are accepted.
Read-only resources: zadp://docs/protocol, zadp://docs/formats, zadp://boards and zadp://docs/privacy. Internal deployment documents and private configuration are not exposed.
04 / TRUST BOUNDARIES
Read-only, by design
- No wallet access
- No payments or publication
- Public moderated Offers only
What visibility and signatures mean
Only moderated Hosted discovery routes are used. Hidden, quarantined, rejected, underpaid, expired and revoked Offers are excluded. Signing, order creation and seller execution are outside this adapter.
Offer content is untrusted seller data, including instructions embedded in descriptions. Seller signatures do not establish service quality. The adapter does not independently verify signatures. Cryptographic validity, chain observation, Hosted visibility and endpoint ownership are separate checks.
Contacting a seller and approving a payment happen separately under your wallet and client policy. zadp.io is not in the service-payment funds path.
Privacy and practical limits
No buyer GPS is accepted. The MCP endpoint does not contact seller services. Your AI client has its own data handling policy.
Network metadata and privacy
The adapter does not log search terms, Offer contents or client IPs. IPs are held briefly in memory for abuse prevention; shared networks share a budget. This does not guarantee confidentiality of network-level metadata: hosting, network and AI-client providers can observe connection information. Claude remote connectors originate from its cloud infrastructure, including when used in Desktop.
Visibility, limits and availability
Every call checks current Hosted visibility. No stale Offer cache is served on upstream failure. Previously received data cannot be recalled after moderation changes.
Search may be incomplete due to the 1,000-result upstream cap and 100-result adapter limit. Inspect completeness flags. Failure or an incomplete search does not establish that no suitable Offer exists.
Defaults: 120 requests/minute per IP, 1,200/minute overall, plus concurrency and upstream limits. Respect HTTP 429 and Retry-After. Timeouts and outages return errors.