AbaPay
by investorphem · remote · no sign-in to list tools · v1.1.0 · published by GitHub user investorphem
Non-custodial stablecoin bill-pay rails on Celo & Base for AI agents, settled on-chain via MCP.
11 tools: 3 can delete or cancel things, 2 change things and 6 only read.
Scanned Oct 21, 2026
- Deletes or cancels3Claude Code: deny: see these tools
- Can't be undone0Claude Code: ask
- Changes things2Claude Code: ask: see these tools
- Only reads6Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http abapay https://agents.abapays.com/api/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
11 tools
Deletes or cancels 3Claude Code: deny
cancel_scheduleCancel active schedules for the linked wallet.No findings
Why it is in this group
- The name "cancel_schedule" says "cancel": a word for removing or ending something.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Cancel active schedules for the linked wallet. Call list_schedules first to get a real id. Pass id to cancel exactly one (no PIN needed). Cancelling several at once — provider for every schedule of that provider, or all: true for every schedule on this wallet — requires the PIN, asked from the human each time. Calling with none of id/provider/all is refused rather than cancelling everything.
Annotations the server declares
- title: Cancel Schedule
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: true
pay_billPay 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 o…No findings
Why it is in this group
- The name "pay_bill" says "pay": a word that usually means money moves, which cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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. 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.
Annotations the server declares
- title: Pay Bill
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
pay_bill_batchPay 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").No findings
Why it is in this group
- The name "pay_bill_batch" says "pay": a word that usually means money moves, which cannot be taken back.
- The input addresses people (input.recipients): what it sends cannot be taken back.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- title: Pay Bill Batch
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: true
Changes things 2Claude Code: ask
check_balanceCheck a linked wallet's stablecoin balances and remaining agent spending allowance.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it Check a linked wallet's stablecoin balances and remaining agent spending allowance. Works with no arguments once this connector is authorized via OAuth.
Annotations the server declares
- title: Check Balance
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
schedule_billSet up a recurring or future one-off bill payment — daily/weekly/monthly airtime, data, electricity, or cable — the same automation Telegram/WhatsApp/X support.No findings
Why it is in this group
- The name "schedule_bill" says "schedule": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Schedule Bill
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 6Claude Code: allow
describe_capabilitiesList what AbaPay can pay (airtime, data, electricity, cable, etc.), any services currently paused, and example requests.No findings
Why it is in this group
- The name "describe_capabilities" says "describe": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Describe Capabilities
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_payment_statusLook up one payment by its reference — the transaction hash (0x…) or the request id a payment returned — and get its current status in plain words: delivered, still being confirmed…No findings
Why it is in this group
- The name "get_payment_status" says "get": a word for reading.
Description, as the server wrote it Look up one payment by its reference — the transaction hash (0x…) or the request id a payment returned — and get its current status in plain words: delivered, still being confirmed, failed, or refunded, including where any refund stands. Only finds payments made by the linked wallet. Read-only, no PIN required. Use this instead of paying again when a pay_bill result was lost.
Annotations the server declares
- title: Get Payment Status
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_international_optionsBrowse the REAL, live international top-up catalogue (140+ countries) one level at a time.No findings
Why it is in this group
- The name "list_international_options" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List International Options
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_plansList 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 VTpas…No findings
Why it is in this group
- The name "list_plans" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List Plans
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
list_schedulesList active recurring/one-off bill schedules for the linked wallet — same data as the AbaPay app and Telegram/WhatsApp "show my schedules".No findings
Why it is in this group
- The name "list_schedules" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List Schedules
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
transaction_historyList recent real transactions for the linked wallet — same data as the AbaPay app's History tab (service, provider, amount, status, tx hash).No findings
Why it is in this group
- The description's first verb is "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Transaction History
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http abapay https://agents.abapays.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__abapay__describe_capabilities",
"mcp__abapay__list_plans",
"mcp__abapay__list_international_options",
"mcp__abapay__transaction_history",
"mcp__abapay__get_payment_status",
"mcp__abapay__list_schedules"
],
"ask": [
"mcp__abapay__check_balance",
"mcp__abapay__schedule_bill"
],
"deny": [
"mcp__abapay__pay_bill",
"mcp__abapay__cancel_schedule",
"mcp__abapay__pay_bill_batch"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as abapay. Review it before you use it.
