Skip to main content
Glama
io.github.zerotaldev/ozow

io.github.zerotaldev/ozow

by zerotaldev

ozow-mcp

test

An MCP server for Ozow, the South African instant EFT ("pay by bank") gateway. It lets an AI assistant create and track Ozow payment requests.

It is locked to Ozow's staging environment unless production is explicitly unlocked twice over. That is the main design decision; the rest of this file explains it.

Node 20+. One runtime dependency (the MCP SDK) plus zod.

The safety model

An MCP server that wraps a payments API gives a language model the ability to move money. That deserves more care than a typical API wrapper, so:

1. Staging by default. Ozow selects environment by base URL, not a request flag, so a staging-configured server has no route to production. This is structural, not a check that can be forgotten.

2. Production needs two independent keys turned. OZOW_ENV=production and OZOW_ALLOW_PRODUCTION=i-understand-this-moves-real-money. Setting only the first makes the server refuse to start. It never silently downgrades to staging - an operator who believes they are live but is not ends up in a worse position than one who cannot start at all.

3. Per-call confirmation, but only where it means something. In production, ozow_create_payment requires confirm="CONFIRM LIVE PAYMENT" exactly. In staging it does not: confirmation friction on imaginary money teaches people to click through, which is worse than no friction at all. The tool description tells the model, in as many words, not to supply that phrase on its own initiative.

4. An amount ceiling. OZOW_MAX_AMOUNT (default R1000) caps any single request, so a miscounted zero hits a wall instead of a bank account.

5. Honest tool annotations. Read-only tools declare readOnlyHint; payment and cancel tools declare destructiveHint. Clients that surface these can ask the user before the call rather than after.

6. Secrets stay out of output. The environment tool masks the client ID and never returns the secret. There is a test that fails if either leaks.

Related MCP server: Centrapay MCP Server

Setup

npm install
cp .env.example .env     # fill in from the Ozow Portal
npm run check            # validates config and credentials, moves no money

You need an Ozow merchant account first, then ask Ozow support or your account manager to enable One API clients in the portal, where the client ID and secret are created.

Tools

Tool

Reads/writes

Notes

ozow_environment

read

Which environment, limits, whether money is real. No network call.

ozow_verify_credentials

read

Confirms the client ID and secret get a token.

ozow_create_payment

write

Returns a redirectUrl for the payer. Confirmation required in production.

ozow_get_transactions

read

Whether a payment request was paid.

ozow_cancel_payment

write

Irreversible.

Connecting a client

{
  "mcpServers": {
    "ozow": {
      "command": "node",
      "args": ["/absolute/path/to/ozow-mcp/src/index.mjs"],
      "env": {
        "OZOW_CLIENT_ID": "...",
        "OZOW_CLIENT_SECRET": "...",
        "OZOW_SITE_CODE": "XXX-XXX-XXX",
        "OZOW_ENV": "staging"
      }
    }
  }
}

Tests

npm test

20 tests. The guard tests are pure and need no credentials; the server tests spawn the real binary and speak MCP to it over stdio, checking that the staging default holds, that production refuses to start unacknowledged, that over-ceiling and non-https requests are rejected before any network call, and that secrets never reach the output.

Status and caveats

Early. Written against Ozow's One API (one.ozow.com/v1), not the legacy i-Pay Payment API - confirm with Ozow which applies to your account, as the published docs cover both and disagree.

One correction to Ozow's own docs: their quick-start gives the token endpoint as <api host>/v1/token. That path returns 404 on both hosts. Tokens are actually issued by a separate auth host - auth.ozow.com/token and stagingauth.ozow.com/token - which answer client_credentials with standard OAuth2 errors. This server uses those. The /v1/payments paths in the docs are correct (they return 401, not 404, without a valid token).

Not yet covered: payouts (money out), which Ozow gates behind separate approval and staging tests; refunds, which their docs describe as a dashboard action rather than an API call; and webhook verification for transaction.complete.

Endpoint paths were probed directly and behave as expected for unauthenticated requests. The server has not yet been run against a live Ozow staging account with real credentials, so request and response bodies are built from the documentation rather than from observed traffic. Expect to adjust field names on first contact.

Licence

MIT

Publishing

The order matters: the official MCP Registry is upstream of the directories, so publishing there is what makes the rest happen.

1. GitHub and npm

gh repo create zerotaldev/ozow-mcp --public --source=. --push
npm publish

package.json carries "mcpName": "io.github.zerotaldev/ozow". The registry checks that marker matches the name in server.json; if they drift, the publish is rejected as an ownership failure.

2. The official MCP Registry

mcp-publisher login github      # device-code OAuth, grants io.github.zerotaldev/*
mcp-publisher publish --dry-run # validates without publishing
mcp-publisher publish

The GitHub login is what entitles the io.github.zerotaldev/* namespace. If you would rather publish under your own domain as com.ciyane/ozow, use mcp-publisher login dns --domain ciyane.com instead and change name in server.json to match — the namespace must agree with the login method or the publish is refused.

server.json validates against the 2025-12-11 schema. Note the registry caps description at 100 characters.

3. Glama

glama.json in the repo root claims the listing for the zerotaldev maintainer. Glama also discovers servers from GitHub, and you can add one manually with Add MCP Server on their servers page using the repository URL. Their FAQ says most submissions pass automatically within minutes.

4. PulseMCP

Nothing to submit. PulseMCP paused direct submissions while they rework ingestion, and they build listings by scraping the official registry and GitHub. Publishing in step 2 is what gets you there.

Available Tools

5 tools
ozow_cancel_paymentCancel an Ozow payment requestA
DestructiveIdempotent

Cancel a payment request that has not been completed. Irreversible: the payer can no longer use that link.

Inputs: paymentId (required).

ozow_create_paymentCreate an Ozow payment requestA
Destructive

Create a payment request and return a redirectUrl for the payer to complete in their bank. In production this collects REAL money and requires explicit confirmation from the human you are working for - never supply the confirmation phrase on your own initiative. Amounts are in rands.

Inputs: amount (required), returnUrl (required), merchantReference (required), confirm, +3 more.

ozow_environmentShow Ozow environmentA
Read-only

Report which Ozow environment this server is connected to, whether it can move real money, and the configured limits. Call this first - and always before any payment - so you know whether you are in staging or production.

Inputs: no named parameters.

ozow_get_transactionsList transactions for a paymentB
Read-only

List the transactions recorded against a payment request, to check whether it was paid. Read-only.

Inputs: paymentId (required), toDate, fromDate.

ozow_verify_credentialsVerify Ozow credentialsA
Read-only

Check that the configured client ID and secret can obtain an access token. Makes no changes and moves no money.

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A3.9/5.0

    Scored across 5 tools

    Disambiguation4/5

    Each tool has a clearly distinct role: credential check, environment report, payment creation, transaction lookup, and cancellation. There is slight conceptual overlap between ozow_verify_credentials and ozow_environment (both configuration preflight checks), but the descriptions make the boundary clear.

    Naming Consistency4/5

    All tools use a consistent ozow_ prefix and snake_case with verb_noun phrasing (verify_credentials, create_payment, get_transactions, cancel_payment). ozow_environment is a noun-only outlier, but overall the pattern is predictable.

    Tool Count5/5

    Five tools is a tight, well-scoped surface for a payment integration. Every tool earns its place covering a distinct step in the payment flow.

    Completeness3/5

    The core flow (create, check status, cancel) is covered, but there are notable gaps: no refund, no settlement/payout inspection, no webhook or notification handling, and transaction listing is only scoped per payment request rather than a general ledger. Agents handling post-payment reconciliation would hit dead ends.

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to interact with the PayFast payment gateway to manage transactions, subscriptions, and refunds. It provides a suite of 13 tools with built-in human-in-the-loop safety confirmations for high-risk financial operations.
      14
      52 npm
      2
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables interaction with the Centrapay payments API for testing NZ payment flows, including creating, managing, and settling payment requests through natural language.
      9
      7 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely create payment references and requests for Multibanco, MB WAY, Payshop, Credit Card, PinPay, Cofidis Pay, PIX, and retrieve payment reports.
      -