PayPing vs Zovo Invoice Ledger
PayPing is an MCP server published by sepehr071. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). Zovo Invoice Ledger is an MCP server published by theluckystrike. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-10. 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 |  PayPing | |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.0 Downloads/month (PyPI): 2 410 Downloads/week (PyPI): 141 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.0 No figure published Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.3.0 Downloads/month (PyPI): 2 410 Downloads/week (PyPI): 141 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
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 | PayPing | Zovo Invoice Ledger |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 | No figure on GitHub |
| Forks (GitHub) (differs) | 0 | No figure on GitHub |
| Last release (differs) | 2026-11-07 | Not published |
| Where it runs (differs) | On your machine (payping-mcp) | Remote server (invoice-ledger.zovo.one/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/sepehr071/payping-mcp | Not stated |
| Changes in the last 7 days | 2 | 2 |
| First seen (differs) | 2026-10-11 | 2026-11-08 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 18 h 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
PayPing
PayPing merchant account for agents: balance, sales, invoices; create invoices and payment links.
Zovo Invoice Ledger
Put a batch of supplier invoices into one spreadsheet with net, tax and gross totals.
How to run each
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)
Zovo Invoice Ledger As a remote MCP server
claude mcp add --transport http invoice-ledger https://invoice-ledger.zovo.one/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Zovo Invoice Ledger 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
The marketplaces of Zovo Invoice Ledger publish no settings it asks for, so we do not compare settings.
What it can do: PayPing · What it can do: Zovo Invoice Ledger · 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.