Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AbaPay

REMOTE · AGENTS.ABAPAYS.COM

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

0 this week 81 Trust /100

Last scanned (22 hours ago)

Scores higher than 79% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Recent critical change

Authorization (19 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4338 tokens (~309/item across 14 items; 13 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
What we tested

Checks we ran (14)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol
  • Capabilities

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 0
    • New tool “pay_bank_transfer”, which the server declares destructive security
    • Schema quality: 3917 → 4338 ▼ functional
    • New tool “list_banks” functional
  • 19 Nov 26 +56
    • Authorization: unverified → fail ▼ critical
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
    • Schema quality: unverified → 100 ▲ functional
  • 18 Nov 26 −56
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Authorization: fail → unverified ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Schema quality: 100 → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
  • 11 Nov 26 +1
    • Stability: 0.97 → pass security
  • 10 Nov 26 −1
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 30 Sept 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “cancel_schedule” rewrote its description, which is the text the model reads security
    • Schema quality: 3394 → 3917 ▼ functional
    • Server version: 1.0.0 → 1.1.0 functional
    • New tool “get_payment_status” functional
    • “cancel_schedule” added an optional parameter “all” cosmetic
    • “cancel_schedule” added an optional parameter “pin” cosmetic
    • “pay_bill” added an optional parameter “idempotency_key” cosmetic
    • “pay_bill_batch” added an optional parameter “idempotency_key” cosmetic
    • “schedule_bill” added an optional parameter “idempotency_key” cosmetic
    • “cancel_schedule” reworded the description of “id” cosmetic
    • “cancel_schedule” reworded the description of “provider” cosmetic
    • “pay_bill” reworded the description of “pin” cosmetic
    • “pay_bill_batch” reworded the description of “pin” cosmetic
    • “schedule_bill” reworded the description of “pin” cosmetic
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://agents.abapays.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=agents.abapays.com CN=YR2,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 RSA 2048 SHA256-RSA 64f0db5d6d96a7d8deb325df5421308d2fd
SANs: agents.abapays.com
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of agents.abapays.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
abapays.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://agents.abapays.com/api/mcp Verified 200
http (plaintext) http://agents.abapays.com/api/mcp HTTPS enforced 308 https://agents.abapays.com/api/mcp
MCP tools · 13 exposed · ~3,728 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cancel_schedule ~233

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.

NameTypeReqDescription
allboolean–Set true to cancel EVERY active schedule on this wallet. Requires pin. Never inferred — must be passed explicitly.
api_keystring–AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
idstring–The exact schedule id from list_schedules. Cancels only that one schedule. No PIN needed.
pinstring–The PIN set when the API key was created. Required with provider or all; not needed for a single id.
providerstring–Cancel every active schedule for this provider, e.g. "mtn". Requires pin. Ignored if id is also given.

No output schema declared.

No examples provided.

check_balance ~103

Check a linked wallet's stablecoin balances and remaining agent spending allowance. Works with no arguments once this connector is authorized via OAuth.

NameTypeReqDescription
api_keystring–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…
chainstring–Defaults to the chain approved when the key was created.

No output schema declared.

No examples provided.

describe_capabilities ~45

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_payment_status ~138

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.

NameTypeReqDescription
api_keystring–AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
referencestringyesThe transaction hash (0x…) or request id of the payment.

No output schema declared.

No examples provided.

list_banks ~63

List the Nigerian banks a bank transfer can be sent to, with the bank_code pay_bank_transfer needs. Read-only, no authentication.

NameTypeReqDescription
searchstring–Optional: filter by part of the bank name, e.g. "access" or "opay".

No output schema declared.

No examples provided.

list_international_options ~249

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.

NameTypeReqDescription
countrystring–Country name or ISO code, e.g. "Ghana" or "GH". Omit to list all supported countries.
operator_idstring–An operator_id returned for this country + product_type_id — the network to top up. Omit to list operators.
product_type_idstring–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.

No output schema declared.

No examples provided.

list_plans ~174

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.

NameTypeReqDescription
providerstringyese.g. mtn, airtel, glo, 9mobile (data); dstv, gotv, startimes (cable); waec, waec-registration, jamb (education)
servicestringyesWhich service to list plans for. Electricity and airtime are free-amount and have no plan list.

No output schema declared.

No examples provided.

list_schedules ~91

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.

NameTypeReqDescription
api_keystring–AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.

No output schema declared.

No examples provided.

pay_bank_transfer ~358

Send naira to a Nigerian bank account, paid from the linked wallet. ONLY for agents with a verified Self Agent ID: the request must be signed with the Self agent key (x-self-agent-* headers; see docs.abapays.com → Self Agent ID), otherwise it is refused before anything is charged. Call list_banks for the bank_code. The account name is checked before any money moves and returned in the result: confirm it with the human. ALWAYS requires the PIN — ask the human for it every time. Money moves for real. The result gives a reference: call get_payment_status with it to read the transfer reference and receipt once the transfer is sent.

NameTypeReqDescription
account_numberstringyesThe 10-digit account number (NUBAN).
amount_ngnnumberyesAmount in naira to send (whole naira, at least 100).
api_keystring–AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
bank_codestringyesThe bank code from list_banks.
chainstring–Optional. Defaults to the chain approved when the key was created.
idempotency_keystring–Optional, strongly recommended: a unique id for THIS transfer (8-128 chars). Retrying with the same key returns the first result instead of paying again.
pinstringyesThe PIN set when the API key was created. Required on EVERY payment — ask the human for it each time.
tokenstring–Optional stablecoin to pay with on that chain (e.g. "USDC", "USDT"). Defaults to the one approved when the key was created.

No output schema declared.

No examples provided.

pay_bill ~883

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.

NameTypeReqDescription
account_numberstringyesPhone 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 a…
amount_ngnnumber–Amount in Naira. Not needed for service: INTERNATIONAL — the NGN-equivalent is derived from the live plan you picked via list_international_options.
api_keystring–AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
chainstring–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.
countrystring–Required for service: INTERNATIONAL — country name or ISO code, from list_international_options.
customer_emailstring–Required for service: INTERNATIONAL (the receipt goes here). Optional otherwise.
customer_namestring–Optional — used for the receipt if known
idempotency_keystring–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 differ…
meter_typestring–Required for ELECTRICITY
operator_idstring–Required for service: INTERNATIONAL — from list_international_options.
pinstringyesThe 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.
product_type_idstring–Required for service: INTERNATIONAL — from list_international_options.
providerstring–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.
servicestringyesWhich kind of bill
tokenstring–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 availabl…
variation_codestring–Plan/bundle/product code — required for DATA, EDUCATION, and INTERNATIONAL, and for CABLE when changing package (not needed to renew the current one)

No output schema declared.

No examples provided.

pay_bill_batch ~502

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.

NameTypeReqDescription
api_keystring–AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
chainstring–Default chain for recipients that don't set their own. Falls back to the chain approved when the API key was created.
customer_emailstring–Optional — used for receipts if known, applies to the whole batch.
idempotency_keystring–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 differ…
pinstringyesThe PIN set when the API key was created (6 digits for new keys). Required once for the whole batch.
recipientsarrayyesAt least 2 recipients (a single recipient should just use pay_bill), at most 20 per call — split a larger batch across several calls.
tokenstring–Default token for recipients that don't set their own. Falls back to the token approved when the API key was created.

No output schema declared.

No examples provided.

schedule_bill ~695

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.

NameTypeReqDescription
account_numberstringyesPhone number (airtime/data), meter number (electricity), or smartcard/IUC number (cable)
amount_ngnnumberyesAmount in Naira to charge each time the schedule runs.
api_keystring–AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
chainstring–Defaults to the chain approved when the API key was created.
customer_emailstring–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 se…
day_of_monthnumber–Required when frequency is "monthly" — 1 through 28.
day_of_weeknumber–Required when frequency is "weekly" — 0 (Sunday) through 6 (Saturday).
frequencystringyesHow often this runs. "once" fires exactly one time, schedule_in_minutes from now.
idempotency_keystring–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 differ…
meter_typestring–Required for ELECTRICITY
pinstringyesThe PIN set when the API key was created (6 digits for new keys). Required to create a schedule, same as pay_bill.
providerstring–e.g. mtn, airtel, glo, 9mobile, ikeja-electric, dstv, gotv, startimes
schedule_in_minutesnumber–Required when frequency is "once" — minutes from now to run it a single time.
servicestringyesWhich kind of bill to schedule. EDUCATION and INTERNATIONAL are not schedulable — use pay_bill directly for those.
tokenstring–Defaults to the token approved when the API key was created.
variation_codestring–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.

No output schema declared.

No examples provided.

transaction_history ~194

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.

NameTypeReqDescription
api_keystring–AbaPay MCP API key. NOT needed when the connector is authorized via OAuth — omit it entirely in that case.
limitnumber–How many recent transactions to return. Defaults to 10, max 25.
offsetnumber–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.

No output schema declared.

No examples provided.

Install

How do I install the AbaPay MCP server?

AbaPay is a hosted endpoint at https://agents.abapays.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · agents.abapays.com

# add to Claude Code
claude mcp add --transport http investorphem-abapay 'https://agents.abapays.com/api/mcp'
Common questions

What is the AbaPay MCP server?

AbaPay is an MCP server listed in the public MCP registry as io.github.investorphem/abapay. Non-custodial stablecoin bill-pay rails on Celo & Base for AI agents, settled on-chain via MCP. This page covers its hosted endpoint (https://agents.abapays.com/api/mcp).

Is the AbaPay MCP server safe to use?

AbaPay scores 81 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AbaPay MCP server expose?

AbaPay exposes 13 tools: describe_capabilities, check_balance, list_plans, list_international_options, transaction_history, and 8 more. Their descriptions and schemas cost roughly 3,728 tokens of context every time the server is loaded.

Does the AbaPay MCP server require authentication?

No. We connected to AbaPay without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AbaPay MCP server still maintained?

AbaPay is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the AbaPay MCP server?

VerifyMCP ran 14 checks on AbaPay, covering TLS certificate, Authorization, HTTPS, HSTS header and 10 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.