Iaptic vs PayPing
Iaptic is an MCP server published by iaptic. Marketplaces we read that list it: 1 (Docker MCP Catalog). PayPing is an MCP server published by sepehr071. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |  Iaptic |  PayPing |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7f86e3becb71 Forks (GitHub): 6 Pulls (Docker Hub): 16 396 Stars (Docker Hub): 0 Stars (GitHub): 9 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.0 Downloads/month (PyPI): 2 410 Downloads/week (PyPI): 132 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 | Iaptic | PayPing |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 9 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 16 396 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 6 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-16 |
| Where it runs (differs) | On your machine (mcp/iaptic) | On your machine (payping-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | 17 | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/iaptic/mcp-server-iaptic | github.com/sepehr071/payping-mcp |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 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
Iaptic
Model Context Protocol server for interacting with iaptic.
PayPing
PayPing merchant account for agents: balance, sales, invoices; create invoices and payment links.
How to run each
Iaptic As a local MCP server: Docker image
claude mcp add --env "IAPTIC_API_KEY=<YOUR_IAPTIC_API_KEY>" --transport stdio iaptic -- docker run -i --rm -e IAPTIC_API_KEY mcp/iapticRequires: IAPTIC_API_KEY (secret)
PayPing 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
The marketplaces of PayPing publish no list of tools, so we do not compare tools.
Settings each asks for
Only Iaptic asks for
IAPTIC_API_KEY (secret)IAPTIC_APP_NAME
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: Iaptic · What it can do: PayPing · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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.