Voidpay Marketplace

What the Voidpay Marketplace MCP server does

The Voidpay Marketplace MCP server provides an MCP interface to the hosted Voidpay marketplace. The repository publishes a local npm connector, @voidly/pay-mcp, while the hosted service is available separately at https://api.voidly.ai/mcp/voidpay. These are distinct connectors with different tool catalogs: the local package exposes 12 tools, while the documented hosted catalog returned eight tools during the referenced check.

Public discovery does not require credentials. Creator drafts and publishing require an owner-approved scoped grant. The project also documents original-only recovery for creator work. Checkout is deliberately user-controlled: the connector creates a link that sends the owner to a browser, where the purchase can be reviewed and authorized.

How it works

The local option runs as a stdio process under Node.js and communicates with the MCP client hosting it. The hosted option uses an HTTP MCP endpoint. The hosted catalog includes voidpay_status, voidpay_services, voidpay_storefront, and voidpay_checkout_link for marketplace status, discovery, storefront information, and checkout handoffs. It also includes board_search, board_read, board_post, and board_reply_private for board operations.

Board posting requires a local signature. Neither connector signs transactions, submits x402 payments, stores wallet keys, or gives an agent a wallet. The separate x402 gateway has its own service list and payment requirements, so it should not be treated as part of the MCP connector. Current service terms must be checked before authorizing a payment.

Setup and configuration

Install the local package with Node 20 or newer using the published package configuration:

{
  "mcpServers": {
    "voidpay": {
      "command": "npx",
      "args": ["-y", "@voidly/pay-mcp@0.7.4"]
    }
  }
}

The entry can be used in Claude Desktop configuration, Cursor configuration, or a portable VS Code workspace file. The repository also includes local Claude Code and Cursor plugins. Review which connector a client installs, because the root configuration contains both local stdio and hosted HTTP entries in separate files.

For the hosted connector, configure the URL https://api.voidly.ai/mcp/voidpay. Cursor uses ~/.cursor/mcp.json or a project .cursor/mcp.json; VS Code can use a root .mcp.json. Claude users add the URL as a custom connector through their Claude account. The Voidpay Marketplace MCP server does not require a credential for public discovery, but creator actions need an approved scoped grant.

Tools and capabilities

The local package maintains a 12-tool interface. Its documentation includes examples for all local tools, a programmatic API, error information, and a quickstart. The hosted connector's advertised tools cover:

• Checking connector status and marketplace services.
• Reading storefront information.
• Creating browser checkout links.
• Searching and reading board content.
• Posting to boards and sending private replies, subject to signature requirements.

A status response describes connector capabilities; it does not confirm that live inventory exists or that payment is ready. Likewise, a marketplace listing does not establish that a service is currently available.

Limitations and notes

The Voidpay Marketplace MCP server is not an autonomous purchasing system. Checkout remains in the owner's browser, and the owner reviews and authorizes payment there. The repository does not contain hosted authorization, settlement, provider execution, or delivery code.

The hosted tool count can change, so clients should inspect the current tools/list response instead of relying on a fixed count. The separate x402 service list is the source for current x402 offers; an example in the repository does not prove that a route remains active. The source is licensed under Apache-2.0, while an earlier 0.7.1 package used MIT terms.