mcpbeat Sign in

AbaPay MCP Server

by investorphem Your server? Claim it
not responding

AbaPay is listed as active in the registry but did not answer our last check. It exposes 10 tools. Last commit 18 Sep 2026.

Non-custodial stablecoin bill-pay rails on Celo & Base for AI agents, settled on-chain via MCP.

Uptime history 7 days of history · worst day 8%
7 days agonow
12.6%
Uptime 24h
23 of 182 checks
10
Tools
read from the server
960 ms
Response time
average over 24h
1
Stars
last commit 18 Sep 2026

What changed 2

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 17 September 2026. No other catalogue keeps this.

17 Sep 2 tool descriptions were rewritten list_international_options, pay_bill

What the code does

We read the source, 20 h ago · tools taken from the live server · rules 3dff92dd89df

Capabilities

What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.

Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.

This code can reach further than it looks

We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 7 min ago.

run in your terminal
claude mcp add abapay --transport http https://www.abapays.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "abapay": {
      "url": "https://www.abapays.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.abapay]
url = "https://www.abapays.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "abapay": {
      "url": "https://www.abapays.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "abapay": {
      "url": "https://www.abapays.com/api/mcp"
    }
  }
}

This server publishes 1 more address. The block above uses the one we reach during checks; the full list is under Endpoints below, and the author may intend a particular one for your client.

Available tools 10

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

pay
pay_bill
Pay a real bill — Nigerian (airtime, data, electricity, cable TV, a WAEC/JAMB education PIN) or international airtime/data across 140+ countries — from the linked wallet, settled on-chain and delivered via the same pipeline as the AbaPay app. For DATA, CABLE (when changing package), and EDUCATION, call list_plans first and use a real variation_code from it. For service: INTERNATIONAL, call list_international_options first and pass back its exact country/product_type_id/operator_id/variation_code — never guess any of these. ALWAYS requires the PIN — including when this connector is authorized via OAuth; ask the human for it every time and never guess or reuse a remembered one. The api_key is only needed when OAuth is not in use. Money moves for real — only call this once the human has clearly confirmed the exact amount, provider, and account. EXECUTES IMMEDIATELY, with no delay/schedule parameter of any kind — there is no way to queue this call for later on this connection. If the human asks to pay "in N minutes", "later today", "tomorrow", or any other future time, do NOT call this now: ask them to confirm they want it sent immediately instead, or tell them delayed/recurring automations can only be set up from the AbaPay app or by messaging the AbaPay agent on Telegram/WhatsApp/X — never silently pay right away when a delay was requested.
pay_bill_batch
Pay airtime or data to multiple recipients in ONE call — the same multi-recipient batch Telegram/WhatsApp/X support ("send 500 to X and 1000 to Y"). One PIN authorizes the whole batch. Recipients are grouped by (chain, token); each group's capacity (balance + approved agent limit) is checked against that group's own subtotal — but if ANY group is short, the ENTIRE batch is refused before anything moves (all-or-nothing on capacity; paying 6 of 8 recipients because the 7th was under-funded is worse than one clear error up front). Once capacity clears, recipients are paid one at a time and the response reports each individually, since a single vend failure partway through must not be reported as if the whole batch failed. AIRTIME and DATA only — electricity, cable, education, and international are not batchable; call pay_bill for those, one at a time. For DATA, call list_plans first and give each recipient needing one its own real variation_code. EXECUTES IMMEDIATELY: no delay/schedule option, same as pay_bill — for a delayed/recurring batch, call schedule_bill once per recipient instead.
balance
check_balance
Check a linked wallet's stablecoin balances and remaining agent spending allowance. Works with no arguments once this connector is authorized via OAuth; otherwise pass the api_key created in the AbaPay app's Agent Hub (MCP).
cancel
cancel_schedule
Cancel one or more active schedules for the linked wallet. Call list_schedules first to get a real id. Pass id to cancel exactly one; pass provider to cancel every active schedule for that provider; omit both to cancel ALL active schedules for this wallet. No PIN required, matching chat.
describe
describe_capabilities
List what AbaPay can pay (airtime, data, electricity, cable, etc.), any services currently paused, and example requests. Call this first if unsure what is supported.
international
list_international_options
Browse the REAL, live international top-up catalogue (140+ countries) one level at a time. Call with no country to see supported countries. Add country to see its product types. Add product_type_id to see operators. Add operator_id too to see real, currently purchasable plans with their exact codes, foreign-currency price, and NGN-equivalent cost. ALWAYS call this before pay_bill with service: INTERNATIONAL, and pass back the exact country/product_type_id/operator_id/variation_code shown — never guess any of them. Only plans marked fixed-price can be paid via pay_bill right now; flexible-amount plans must be completed in the AbaPay app.
plans
list_plans
List the REAL, currently purchasable plans for a service that needs one — DATA bundles, CABLE packages, or EDUCATION products (WAEC/JAMB) — with their exact codes and current VTpass prices. ALWAYS call this before pay_bill for these three services and pass back one of the returned codes as variation_code. Never guess a plan, a code, or a price — if this returns nothing usable, say so rather than inventing one.
schedule
schedule_bill
Set up a recurring or future one-off bill payment — daily/weekly/monthly airtime, data, electricity, or cable — the same automation Telegram/WhatsApp/X support. Validates exactly like pay_bill (call list_plans first for DATA, or CABLE when changing package, to get a real variation_code) and ALWAYS requires the PIN, since this creates a standing spend. Nothing is charged when this tool runs — money only moves later, when the schedule actually fires, and only if the wallet still has a funded on-chain allowance at that time. If the approved agent limit already covers the amount right now, the schedule is created to auto-pay itself each time it is due; otherwise it is saved as notify-only and someone must call pay_bill manually when it comes due — the response says which. EDUCATION and INTERNATIONAL cannot be scheduled; pay those directly with pay_bill. Use list_schedules to see what is set up and cancel_schedule to remove one.
schedules
list_schedules
List active recurring/one-off bill schedules for the linked wallet — same data as the AbaPay app and Telegram/WhatsApp "show my schedules". Read-only, no PIN required. Returns each schedule's id — pass that to cancel_schedule to remove one.
transaction
transaction_history
List recent real transactions for the linked wallet — same data as the AbaPay app's History tab (service, provider, amount, status, tx hash). Read-only, no PIN required. The interactive card's own Next/Previous buttons page through results by re-calling this tool with a different offset — pass offset yourself only when asked for something like "the next page" or "transactions before that" in plain text.

Endpoints

URLTransportStateLatencyChecked
https://www.abapays.com/api/mcp streamable-http answering 89 ms 7 min ago
https://agents.abapays.com/api/mcp streamable-http answering 137 ms 7 min ago

Alternatives to AbaPay

same job, measured the same way
Xenarch MCP
by xenarch-ai

Xenarch — x402 MCP server for AI agent payments. Non-custodial, USDC on Base L2.

120 installs/wk local only
Agentpay
by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets and payments on 17 chains.

121 installs/wk local only
multichain-mcp
by wkalidev

MCP server for AI agents — Stacks, Celo, and Base in one npm package.

51 installs/wk local only
Clawpay
by up2itnow0822

Non-custodial x402 payment MCP server for AI agents. Wallets, payments, and commerce on 17 chains.

local only
ClawPay MCP — Non-Custodial x402 Payments for AI Agents
by up2itnow0822

Non-custodial x402 payments for AI agents. Sign locally, spend limits, Base network.

53 installs/wk local only
Agentic Endpoints
by oliverkiss

Pay-per-call tools for autonomous agents, settled in USDC on Base via x402.

20 tools answering
Forge Treasury
by forgetreasury

Non-custodial USDC yield vaults on Base mainnet with 9 MCP tools for AI agent treasury.

9 tools answering
SaturnZap
by lqwdtech

Non-custodial Bitcoin Lightning (LDK) wallet for AI agents — pays L402 APIs from CLI or MCP.

49 installs/wk local only

AbaPay — questions

Answers built from our own checks of this server.

What can AbaPay do?
It exposes 10 tools, read directly from the server on our last check. Among them: cancel_schedule, check_balance, describe_capabilities, list_international_options, list_plans, list_schedules and 4 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is AbaPay working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 23 of 182 checks got a reply (12.6%), average response time 960 ms. The bar chart above shows every period we have measured.
The registry lists AbaPay as active — why does it not respond?
The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.
How do I connect AbaPay?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does AbaPay need an API key?
No. AbaPay completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 10 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is AbaPay?
It answers our handshake in 960 ms on average, which is faster than 9% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is AbaPay open source?
Yes — it is published under the MIT licence, written in TypeScript and 1 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.