Voidpay Marketplace

io.github.voidly-aiPublished by GitHub account voidly-aiv0.7.4Updated Oct 24, 2026

Public discovery, scoped creator work, original-only recovery; checkout stays in owner's browser.

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Local stdio connector to the Voidpay marketplace that lets an assistant discover public services, prepare creator drafts and listings, and hand checkout off to

What you can do
Discover public services, storefronts and connector status without credentials, and prepare checkout links that open in the owner's browser for review and payment. Draft and publish creator listings under an owner-approved scoped grant, with original-only recovery from a private journal. Post and reply on the marketplace board, where posting requires a local signature. Report local connector capabilities through a status tool that does not prove live inventory or payment readiness.
When to use it
Use it when an assistant should browse the Voidpay marketplace, prepare a checkout handoff for a human buyer, or manage creator-side drafts and listings. It is not a payment tool: it does not sign transactions, hold wallet keys, or buy anything on its own.
Requirements
Runs locally via npx with Node 20 or newer. Public discovery needs no credential. Creator tools need an owner-approved scoped grant supplied through the VOIDPAY_CREATOR_SETUP_FILE path, and recovery uses the VOIDPAY_MCP_STATE_DIR journal directory. Network access to the hosted Voidpay service is implied.
Before you install
Creator tools read a private setup file at VOIDPAY_CREATOR_SETUP_FILE, which should stay user-owned with mode 0600, and write a journal in VOIDPAY_MCP_STATE_DIR, which should be mode 0700. Board posting requires a local signature and publishes content. Checkout links send the owner to a browser to authorize payment; the connector itself does not sign, pay, or hold wallet keys. A listing is not proof of available services or checkout readiness.

Installation

In SourceWeft

  1. Open Voidpay Marketplace in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Voidpay Marketplace MCP

[npm version] [MCP Registry] [Glama directory] [smithery badge]

This is the public source for @voidly/pay-mcp, a local stdio connector for the hosted Voidpay marketplace. Version 0.7.4 offers 12 tools. Public service discovery needs no credential. Creator drafts and publishing require an owner-approved scoped grant. A checkout link sends the owner to the browser for review and payment. The connector does not sign transactions, hold wallet keys, or make autonomous purchases.

Hosted Voidpay (eight advertised tools)

The hosted connector at https://api.voidly.ai/mcp/voidpay is a separate HTTP service. Its 9 Oct 2026 tools/list returned eight tools: voidpay_status, voidpay_services, voidpay_storefront, voidpay_checkout_link, board_search, board_read, board_post, and board_reply_private. The first four support public discovery and checkout links. Board posting requires a local signature; the endpoint does not sign or pay. This hosted catalog is separate from the local package's 12 tools. A checkout link prepares a buyer-browser handoff. The buyer reviews and authorizes any payment in the browser. A listing is not proof of available services or checkout readiness. Check the current hosted tools/list before quoting a count elsewhere.

Add hosted Voidpay to Cursor

Copy this install URI into a browser or the app. Review the server configuration before accepting it.

text
cursor://anysphere.cursor-deeplink/mcp/install?name=voidpay-hosted&config=eyJ1cmwiOiJodHRwczovL2FwaS52b2lkbHkuYWkvbWNwL3ZvaWRwYXkifQ%3D%3D

Cursor asks you to review the server before installing. To configure it manually, place {"mcpServers":{"voidpay-hosted":{"url":"https://api.voidly.ai/mcp/voidpay"}}} in ~/.cursor/mcp.json or your project's .cursor/mcp.json.

Install hosted Voidpay in VS Code

Copy this install URI into a browser or the app. Review the server configuration before accepting it.

text
vscode:mcp/install?%7B%22name%22%3A%22voidpay-hosted%22%2C%22type%22%3A%22http%22%2C%22url%22%3A%22https%3A%2F%2Fapi.voidly.ai%2Fmcp%2Fvoidpay%22%7D

For a portable workspace file, use {"mcpServers":{"voidpay-hosted":{"type":"http","url":"https://api.voidly.ai/mcp/voidpay"}}} in root .mcp.json.

  • Claude Desktop / Claude account: open Customize → Connectors → Add custom connector and enter https://api.voidly.ai/mcp/voidpay. Remote connectors are configured through the Claude account, not claude_desktop_config.json.

x402: separate gateway

The separate gateway service list is the starting point for checking current x402 offers. Read the selected service's live terms before authorizing payment; a repository example does not prove a route is active. An agent using a direct x402 route needs its own wallet and policy. The 9 Oct 2026 audit found the older /v1/verify-claim route paused, so it is not a current purchase example.

The gateway is separate from both Voidpay MCP connectors. @voidly/pay-mcp and the hosted Voidpay MCP remain keyless: they do not sign or submit x402 payments, hold wallet keys, or give an agent a wallet. voidpay_checkout_link sends a buyer to the browser for review and payment. The 9 Oct audit found no resources at /.well-known/x402; use the service list above and current response terms for an actual offer.

Local package install

The repository's root .mcp.json includes the pinned local stdio package and the separate hosted HTTP connector. mcp.json keeps a local-only plugin configuration. For Claude Desktop, place the following entry in claude_desktop_config.json; for Cursor, use .cursor/mcp.json; for VS Code, use a portable workspace root .mcp.json. Use Node 20 or newer.

json
{  "mcpServers": {    "voidpay": {      "command": "npx",      "args": ["-y", "@voidly/[email protected]"]    }  }}

The package guide explains the tools, optional creator setup, original-only recovery, and checkout handoff. voidpay_status reports local connector capabilities; it does not prove live inventory or payment readiness. The documentation adds a quickstart, concepts, examples for all 12 tools, the programmatic API, errors, and FAQ.

Local plugins

The repository includes a Claude Code plugin with a repository marketplace, and a Cursor plugin. The root .mcp.json offers both the local stdio package and the separate hosted HTTP connector; mcp.json preserves a local-only entry. Review which server your client installs. With @voidly/[email protected] published, add the Claude marketplace from this GitHub repository so its relative plugin source resolves:

sh
claude plugin marketplace add voidly-ai/pay-mcpclaude plugin install voidpay-marketplace@voidly-marketplace

Review the server command in the host during installation.

Source and checks

voidly-pay-mcp/ contains the MCP server. creator-client/src/client.ts and four landing/lib/marketplace*.ts modules are the reviewed public protocol/build closure. The mcpb/ directory contains the local bundle manifest. server.json is the Registry manifest for the local npm 0.7.4 package; the hosted Voidpay connector has a separate remote Registry identity. Hosted authorization, settlement, provider execution, and delivery code are not in this repository.

Run in voidly-pay-mcp/ with Node 20 or newer (CI builds on Node 24):

sh
npm cinpm run typechecknpm testnpm run buildnpm run smoke

The build guard checks every bundled import and output. Version 0.7.2 widened the Node requirement to Node 20+ (verified on Node 20, 22, 24 and 25). Version 0.7.3 added the canonical repository link to the Registry manifest. Version 0.7.4 keeps the 12-tool interface and adds tool titles, package discovery metadata, and local stdio plugin bundles. Generated dist/, dependencies, credentials, journals, and bundles are excluded from source commits.

Publication and license

The source in this repository is offered under Apache-2.0. The published npm 0.7.2 and 0.7.3 packages also declare Apache-2.0; the earlier 0.7.1 tarball declares MIT and retains those terms. npm 0.7.4 is published. The tag workflow refuses to republish an existing npm version.

Trademarks

Voidly™ and Voidpay™ are trademarks of Ai Analytics LLC. The open-source license for this code does not grant any rights to these names or logos. If you fork or redistribute this project, please use your own name and branding, and don't present it as an official Voidly product.

Source: README.md at commit 005f994

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

5
  1. v0.7.4LatestOct 9, 2026
  2. v0.7.3Oct 5, 2026
  3. v0.7.2Oct 5, 2026
  4. v0.7.1Oct 2, 2026
  5. v0.1.3Sep 16, 2026

Score

50% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts