DopamineDesk x402 Marketplace MCP Server

Decision-ready machine-to-machine reports paid per request with the x402 Payment Protocol on Base Mainnet.

No API key. No account. No subscription. Buy one current answer in USDC when a workflow needs it. The catalog includes transaction preflight, vendor onboarding risk, live x402 opportunity research, company intelligence, endpoint verification, website due diligence, VIN safety, market checks, security research, and atomic EVM reads.

Every billable route accepts ?preview=true. The preview is a live contract proof showing the source, freshness, required inputs, and response shape. It deliberately withholds the decision-ready values delivered by the paid call.

Buyer-ready outcomes

These are complete paid deliverables, not teaser text. The lower-level catalog remains available for workflows that need a single chain read, filing, sanctions check, quote, or verification result.

Related MCP server: hyperd-mcp

Install

npx -y dopaminedesk-ai-data-marketplace-mcp

Use it from any stdio-compatible MCP client:

{
  "mcpServers": {
    "dopaminedesk-data-marketplace": {
      "command": "npx",
      "args": ["-y", "dopaminedesk-ai-data-marketplace-mcp"]
    }
  }
}

Official MCP Registry name: io.github.jblaz6335/ai-data-marketplace.

Inspect a live contract

curl "https://ai-data-marketplace-1042299154756.us-central1.run.app/api/v1/company_intelligence?preview=true&domain=example.com"

The proof includes source, freshness, request parameters, top-level fields, response shape, and a purchase block. Decision-ready values remain in the paid result.

Optional one-call purchasing

The current GitHub source release, version 2.9.0, can complete the x402 challenge, authorization, retry, and settlement automatically. The npm latest tag still points to version 2.8.3, so install the source release directly until 2.9.0 is published to npm:

npx -y github:jblaz6335/mcp-server-aidatamarketplace

The buyer key stays inside the local MCP process and is never sent to the marketplace. Use a dedicated low-balance Base wallet, not a primary wallet.

{
  "mcpServers": {
    "dopaminedesk-data-marketplace": {
      "command": "npx",
      "args": ["-y", "github:jblaz6335/mcp-server-aidatamarketplace"],
      "env": {
        "X402_AUTO_PAY": "true",
        "X402_EVM_PRIVATE_KEY": "YOUR_DEDICATED_BUYER_WALLET_KEY",
        "X402_MAX_PAYMENT_USDC": "0.25"
      }
    }
  }
}

Call a product with auto_pay: true. The adapter refuses disabled, conflicting, invalid, or over-cap purchases. It never falls back to an uncapped payment.

Verification and engineering scope

The public verification hub and machine verification record expose the production evidence.

I built this adapter around these constraints:

• the production OpenAPI contract is the source of truth for tool discovery;

• live contract proofs verify the source and schema without replacing the paid product;

• automatic purchasing is opt-in, locally signed, and protected by a hard per-call cap;

• conflicting, malformed, disabled, and over-cap payment attempts fail closed;

• settlement details stay attached to the delivered result for reconciliation.

Run the verification suite locally:

npm ci
npm test

Production contracts

• Store: https://ai-data-marketplace-1042299154756.us-central1.run.app/

• OpenAPI: https://ai-data-marketplace-1042299154756.us-central1.run.app/openapi.json

• Postman: https://ai-data-marketplace-1042299154756.us-central1.run.app/postman.json

• LLM manifest: https://ai-data-marketplace-1042299154756.us-central1.run.app/llms.txt

• x402 manifest: https://ai-data-marketplace-1042299154756.us-central1.run.app/.well-known/x402

• x402scan: https://www.x402scan.com/server/8dd63536-ba25-40f4-b36a-7d05ed18d007

The MCP adapter builds its tool list from the production OpenAPI document. Counts, prices, availability, data mode, and source declarations come from the live contract instead of a hand-written endpoint list.

Every billable product uses x402 v2 exact payments on Base mainnet through the Coinbase CDP facilitator:

1. Call the endpoint and read the base64 PAYMENT-REQUIRED response header.

2. Sign the exact authorization with a compatible x402 buyer client.

3. Retry with PAYMENT-SIGNATURE.

4. Read settlement details from PAYMENT-RESPONSE.

See PAYMENT_FLOW.md for the manual and legacy confirmed-transaction paths.

Published distribution

• npm package

• Official MCP Registry

• Smithery

• x402scan

License

MIT License. Open-source MCP buyer adapter and marketplace client.