Ext Ops Panel
Open dashboard
Comparison

AbaPay vs io.github.quantumskils-arch/momo-parser-mcp

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. io.github.quantumskils-arch/momo-parser-mcp is an MCP server published by quantumskils-arch. 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

Where each is published
MarketplaceAbaPayio.github.quantumskils-arch/momo-parser-mcp
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.0.0
No figure published
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

AbaPay vs io.github.quantumskils-arch/momo-parser-mcp
FactAbaPayno longer listed · io.github.quantumskils-arch/momo-parser-mcp
Marketplaces that list it (differs)01
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (agents.abapays.com/api/mcp)Remote server (momo.opportunityradar.africa/mcp)
TransportStreamable HTTPStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)1Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/investorphem/abapaygithub.com/quantumskils-arch/momo-parser-mcp
Changes in the last 7 days00
First seen (differs)2026-10-132026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 5 days ago, requires a key

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.

Its card, with similar plugins by marketplace

What each says it does

AbaPay

In its own words, on Community GitHub marketplaces:

Pay bills with stablecoins: Nigerian airtime, data, electricity, cable TV and education, plus international airtime and data in 140+ countries.

io.github.quantumskils-arch/momo-parser-mcp

In its own words, on Official MCP Registry:

Parses MTN MoMo and Airtel Money Uganda SMS into structured JSON.

How to run each

AbaPay

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

io.github.quantumskils-arch/momo-parser-mcp As a remote MCP server

Claude Code
claude mcp add --transport http momo-parser-mcp https://momo.opportunityradar.africa/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only io.github.quantumskils-arch/momo-parser-mcp 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: AbaPay · What it can do: io.github.quantumskils-arch/momo-parser-mcp · 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.

Where the data comes from: how the catalog is built