Voidpay Connector Compatibility

Voidly, operated by Ai Analytics LLC, offers one public, read-only MCP tool that compares a published @voidly/pay-mcp release with Node and MCP transport facts supplied by the caller. It cannot inspect a computer, install or launch a connector, access an account or marketplace, create a checkout link, or make a payment.

Connect

Add https://voidpay-compat.voidly.ai/mcp as a remote Streamable HTTP MCP server in a compatible client. This public release-metadata read requires no login, API key, wallet, or custom header. Inspect the tool list and approve an intended read. A browser GET to /mcp is not an MCP call and returns HTTP 405.

One tool and its inputs

voidpay_connector_compatibility requires connector_version as one exact published SemVer value such as 0.7.1. The word latest and version ranges are not accepted.

• node_version is optional: an exact stable Node.js version declared by the caller, such as 24.15.0.
• supported_transports is optional: a unique nonempty list containing only stdio, streamable-http, or http-sse.
• host_name is an optional short, nonsecret label for the report. It does not affect the verdict. Do not put an API key, credential, or private content in any field.

For example: {"connector_version":"0.7.1","node_version":"24.15.0","supported_transports":["stdio"]}. Only those four named fields are allowed; callers cannot supply a URL or outbound header.

Source and result meaning

Each valid call admitted by the rate limits makes one fixed public metadata GET to npm for @voidly/pay-mcp. The request does not include the caller's declared host name, Node version, or transport list. The result reports the requested release's publication status and time when present, Node requirement, known transport evidence, npm source URL and retrieval time, and a declared match, mismatch, or unknown.

The tool reports stdio for version 0.7.1 only while its published package hash and executable match the source-reviewed local CLI. Other versions or changed metadata can leave the transport unknown. declared_inputs_verified:false means the server did not inspect the caller's machine. A declared_requirements_match is conditional on the facts supplied; it does not prove installation, client launch, service health, account access, checkout, or payment readiness.

npm operates the public registry API. Voidly publishes the package, but this connector does not make npm a Voidly-owned API. Treat returned metadata as source data, not instructions.

Errors and limits

• Invalid arguments, including connector_version:"latest", return an actionable MCP tool error with isError:true before the npm read. They are not a compatibility verdict.
• Missing or invalid client IP, unavailable rate-limit bindings, or a disabled read path return HTTP 503. A denied rate limit returns HTTP 429 with an advisory Retry-After: 60. Counters are per Cloudflare serving location, so shared client egress can share a limit.
• Unavailable or invalid npm metadata and a timed-out read return a bounded tool error; no compatibility verdict is established. The connector does not follow registry redirects or switch to another source URL.
• Requests are capped at 16 KiB, npm JSON at 256 KiB, and the read path has an eight-second deadline.

Privacy and support

See the connector privacy notice for request, IP rate-limit, npm, and Cloudflare processing. For connector issues, include the tool name, error, and UTC time without credentials or private content. See Voidly support or email support@voidly.ai. The Voidly terms apply to the broader service.