Test Card Hub vs PayPing
Test Card Hub is an MCP server published by eyrockscript. Marketplaces we read that list it: 1 (Official MCP Registry). PayPing is an MCP server published by sepehr071. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-13. 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 |  Test Card Hub |  PayPing |
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.3.0 Downloads/month (PyPI): 2 410 Downloads/week (PyPI): 141 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.3.0 Downloads/month (PyPI): 2 410 Downloads/week (PyPI): 141 Forks (GitHub): 0 Stars (GitHub): 1 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 | Test Card Hub | PayPing |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 2 (better) | 1 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-11-11 (better) | 2026-11-07 (worse) |
| Where it runs (differs) | On your machine (test-card-hub-mcp) | On your machine (payping-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/eyrockscript/test-card-hub | github.com/sepehr071/payping-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-11-10 | 2026-10-11 |
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
Test Card Hub
Sandbox test cards, Playwright tests, real-card scanner and decline codes for LATAM gateways.
PayPing
PayPing merchant account for agents: balance, sales, invoices; create invoices and payment links.
How to run each
Test Card Hub As a local MCP server: npm package
claude mcp add --transport stdio test-card-hub -- npx -y test-card-hub-mcpPayPing As a local MCP server: PyPI package
claude mcp add --env "PAYPING_TOKEN=<YOUR_PAYPING_TOKEN>" --transport stdio payping-mcp -- uvx payping-mcpRequires: PAYPING_TOKEN (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
Only Test Card Hub asks for
TEST_CARD_HUB_BACKUP
Only PayPing asks for
PAYPING_MCP_PROXYPAYPING_TOKEN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Test Card Hub · What it can do: PayPing · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.