AbaPay vs AgentPay VN
AbaPay is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑15.
AbaPay is a plugin bundle for AI coding tools published by Masonode Technologies Limited. No marketplace we read lists it any more. AgentPay VN is an MCP server published by phuocdu. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  AgentPay VN | |
|---|---|---|
| Community marketplace investorphem/abapay | Removed on 2026-10-15 Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.0 Downloads/month (PyPI): 114 Downloads/week (PyPI): 35 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 | AbaPayno longer listed · | AgentPay VN |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | Not published | 2026-10-21 |
| Where it runs (differs) | Remote server (agents.abapays.com/api/mcp) | On your machine (agentpay-vn) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/investorphem/abapay | github.com/phuocdu/agentpay-vn |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of AbaPay
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Nigeria Payments (Paystack — bank transfer / USSD)
Nigeria payments for AI agents — bank transfer / USSD via Paystack. Never holds funds.
-
Ghana Payments (Paystack — MTN MoMo)
Ghana payments for AI agents — MTN MoMo via Paystack. Never holds funds.
-
paystack-mcp io.github.tracentdev/paystack-mcp
Agent-callable Paystack for African commerce. Ten tools, integer-kobo money, NDPA-compliant.
-
Ivory Coast Payments (Paystack — Orange Money / MTN MoMo)
Ivory Coast payments for AI agents — Orange Money / MTN MoMo via Paystack. Never holds funds.
-
Zambia Payments (Flutterwave — mobile money)
Zambia payments for AI agents — mobile money via Flutterwave. Never holds funds.
-
Kenya Payments (Flutterwave — M-Pesa)
Kenya payments for AI agents — M-Pesa via Flutterwave. Never holds funds.
What each says it does
AbaPay
Pay bills with stablecoins: Nigerian airtime, data, electricity, cable TV and education, plus international airtime and data in 140+ countries.
AgentPay VN
Let AI agents collect VietQR payments — generate a QR and auto-confirm settlement.
How to run each
AbaPay
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
AgentPay VN As a local MCP server: PyPI package
claude mcp add --env "AGENTPAY_API_KEY=<YOUR_AGENTPAY_API_KEY>" --transport stdio agentpay-vn -- uvx agentpay-vnRequires: AGENTPAY_API_KEY (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
The marketplaces of AbaPay publish no settings it asks for, so we do not compare settings.
What it can do: AbaPay · What it can do: AgentPay VN · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. 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.