Pink Agentic AI Payments (by PinkWallet): lets Claude, ChatGPT, Cursor pay vendor invoices within company spending rules (budgets, caps, allow-lists, human approval). Sandbox preview, test money.
Nothing to run from here
AbaPay is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
11
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
Non-custodial stablecoin bill-pay rails on Celo & Base for AI agents, settled on-chain via MCP.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http abapay-mcp https://agents.abapays.com/api/mcp
# 2 — ask your agent for something these tools do
# describe_capabilities, check_balance, list_plans and 8 more
AbaPay costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
INAll 1 server
investorphem1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http abapay-mcp https://agents.abapays.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
No parameter schema on file.
Check a linked wallet's stablecoin balances and remaining agent spending allowance. Works with no arguments once this connector is authorized via OAuth.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | AbaPay MCP API key (starts with aba_mcp_). NOT needed when the connector is authorized via OAuth — omit it entirely in that case; only supply it if this server asked you to authenticate and OAuth is u |
| chain | string | no | Defaults to the chain approved when the key was created. |
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 i
| Parameter | Type | Required | Notes |
|---|---|---|---|
| service | string | yes | Which service to list plans for. Electricity and airtime are free-amount and have no plan list. |
| provider | string | yes | e.g. mtn, airtel, glo, 9mobile (data); dstv, gotv, startimes (cable); waec, waec-registration, jamb (education) |
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: INT
| Parameter | Type | Required | Notes |
|---|---|---|---|
| country | string | no | Country name or ISO code, e.g. "Ghana" or "GH". Omit to list all supported countries. |
| product_type_id | string | no | A product_type_id returned for this country — e.g. which kind of top-up (airtime vs a data bundle). Omit to list the country's product types. |
| operator_id | string | no | An operator_id returned for this country + product_type_id — the network to top up. Omit to list operators. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case. |
| limit | number | no | How many recent transactions to return. Defaults to 10, max 25. |
| offset | number | no | How many of the most recent transactions to skip before listing — 0 (default) starts at the newest. Used for paging: offset=10 with the default limit gets the next 10 after the first page. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case. |
| reference | string | yes | The transaction hash (0x…) or request id of the payment. |
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_in
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case. |
| pin | string | yes | The PIN set when the API key was created (6 digits for new keys). Required on EVERY payment, including over an OAuth connection — ask the human for it each time. |
| idempotency_key | string | no | Optional, strongly recommended: a unique id you choose for THIS payment (8-128 chars, e.g. a UUID). Retrying with the same key returns the first result instead of paying again; reusing it with differe |
| service | string | yes | Which kind of bill |
| provider | string | no | e.g. mtn, airtel, glo, ikeja-electric, dstv, gotv, startimes, waec, waec-registration, jamb. Not used for service: INTERNATIONAL — use country/product_type_id/operator_id instead. |
| account_number | string | yes | Phone number (airtime/data), meter number (electricity), smartcard/IUC number (cable), JAMB profile ID (education: jamb), the buyer's phone number (education: waec), or the destination phone number ab |
| amount_ngn | number | no | Amount in Naira. Not needed for service: INTERNATIONAL — the NGN-equivalent is derived from the live plan you picked via list_international_options. |
| chain | string | no | Defaults to the chain approved when the API key was created. Only override this if the default chain lacks balance/allowance and check_balance shows funds on the other one. |
| token | string | no | Which stablecoin to pay with. Defaults to the token approved when the API key was created. If that one is short on balance or on-chain allowance, call check_balance first to see what else is available |
| variation_code | string | no | Plan/bundle/product code — required for DATA, EDUCATION, and INTERNATIONAL, and for CABLE when changing package (not needed to renew the current one) |
| meter_type | string | no | Required for ELECTRICITY |
| customer_name | string | no | Optional — used for the receipt if known |
| customer_email | string | no | Required for service: INTERNATIONAL (the receipt goes here). Optional otherwise. |
| country | string | no | Required for service: INTERNATIONAL — country name or ISO code, from list_international_options. |
| product_type_id | string | no | Required for service: INTERNATIONAL — from list_international_options. |
| operator_id | string | no | Required for service: INTERNATIONAL — from list_international_options. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case. |
| pin | string | yes | The PIN set when the API key was created (6 digits for new keys). Required to create a schedule, same as pay_bill. |
| idempotency_key | string | no | Optional, strongly recommended: a unique id you choose for THIS payment (8-128 chars, e.g. a UUID). Retrying with the same key returns the first result instead of paying again; reusing it with differe |
| service | string | yes | Which kind of bill to schedule. EDUCATION and INTERNATIONAL are not schedulable — use pay_bill directly for those. |
| provider | string | no | e.g. mtn, airtel, glo, 9mobile, ikeja-electric, dstv, gotv, startimes |
| account_number | string | yes | Phone number (airtime/data), meter number (electricity), or smartcard/IUC number (cable) |
| amount_ngn | number | yes | Amount in Naira to charge each time the schedule runs. |
| variation_code | string | no | Plan/bundle/product code — required for DATA, and for CABLE when changing package (not needed to renew the current one). Get a real one from list_plans first. |
| meter_type | string | no | Required for ELECTRICITY |
| frequency | string | yes | How often this runs. "once" fires exactly one time, schedule_in_minutes from now. |
| day_of_week | number | no | Required when frequency is "weekly" — 0 (Sunday) through 6 (Saturday). |
| day_of_month | number | no | Required when frequency is "monthly" — 1 through 28. |
| schedule_in_minutes | number | no | Required when frequency is "once" — minutes from now to run it a single time. |
| chain | string | no | Defaults to the chain approved when the API key was created. |
| token | string | no | Defaults to the token approved when the API key was created. |
| customer_email | string | no | Where to send a notification when this runs. MCP has no persistent channel to message back into a conversation — without this, you'll need to poll list_schedules or transaction_history yourself to see |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case. |
| id | string | no | The exact schedule id from list_schedules. Cancels only that one schedule. No PIN needed. |
| provider | string | no | Cancel every active schedule for this provider, e.g. "mtn". Requires pin. Ignored if id is also given. |
| all | boolean | no | Set true to cancel EVERY active schedule on this wallet. Requires pin. Never inferred — must be passed explicitly. |
| pin | string | no | The PIN set when the API key was created. Required with provider or all; not needed for a single id. |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| api_key | string | no | AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case. |
| pin | string | yes | The PIN set when the API key was created (6 digits for new keys). Required once for the whole batch. |
| idempotency_key | string | no | Optional, strongly recommended: a unique id you choose for THIS payment (8-128 chars, e.g. a UUID). Retrying with the same key returns the first result instead of paying again; reusing it with differe |
| recipients | array | yes | At least 2 recipients (a single recipient should just use pay_bill), at most 20 per call — split a larger batch across several calls. |
| chain | string | no | Default chain for recipients that don't set their own. Falls back to the chain approved when the API key was created. |
| token | string | no | Default token for recipients that don't set their own. Falls back to the token approved when the API key was created. |
| customer_email | string | no | Optional — used for receipts if known, applies to the whole batch. |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install AbaPay or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither: the repository linked on this page is where this record was collected from, not a copy of what the address serves, so it is not graded in its place. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.1.0.
1.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish AbaPay can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.