io.github.szarl/payments-ai-mcp vs Voidpay (hosted)
io.github.szarl/payments-ai-mcp is an MCP server published by szarl. Marketplaces we read that list it: 1 (Official MCP Registry). Voidpay (hosted) is an MCP server published by voidly-ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Voidpay (hosted) | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.3 Downloads/month (npm): 853 Downloads/week (npm): 243 Not marked · First seen |
Listed Version: 0.7.4 Forks (GitHub): 1 Stars (GitHub): 0 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | io.github.szarl/payments-ai-mcp | Voidpay (hosted) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@payments-ai/mcp) | Remote server (api.voidly.ai/mcp/voidpay) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/paymentsai/pai-managed | github.com/voidly-ai/pay-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 5 days ago |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
io.github.szarl/payments-ai-mcp
Launch products and branded checkouts on Payments AI, the Merchant of Record for AI-built apps.
Voidpay (hosted)
Hosted, no install: find agent services and storefronts, prepare owner-approved checkout links.
How to run each
io.github.szarl/payments-ai-mcp As a local MCP server: npm package
claude mcp add --transport stdio payments-ai-mcp -- npx -y @payments-ai/mcpVoidpay (hosted) As a remote MCP server
claude mcp add --transport http voidpay https://api.voidly.ai/mcp/voidpayCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Voidpay (hosted) has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: io.github.szarl/payments-ai-mcp · What it can do: Voidpay (hosted) · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.