Zambia Payments (Flutterwave — mobile money)

app.wishpoolPublished by wishpool.appOfficial publisherv0.1.0Updated Oct 24, 2026

Zambia payments for AI agents — mobile money via Flutterwave. Never holds funds.

The publisher's own server: Algeria Payments (Chargily Pay — EDAHABIA / CIB)

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant handle Zambia mobile money payments through Flutterwave, without the server holding funds.

What you can do
A remote MCP endpoint for Zambia payments built on Flutterwave mobile money. The registry description says it provides Zambia payments for AI agents via mobile money and that it never holds funds. No tool list is published, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to work with Zambian mobile money payments through Flutterwave, for example collecting or initiating payments in that market. Because no tool list is published, confirm the available operations before relying on it.
Requirements
Remote streamable HTTP endpoint at No packages, environment variables, headers, or authentication are declared in the manifest, but a payment service of this kind would normally need Flutterwave credentials; verify what it actually requires.
Before you install
It is a payments service, so operations may move real money and any credentials or API keys involved are sensitive. The manifest declares no authentication, which is unusual for payments and worth checking before use. No tool list is published, so review what each tool does before letting an assistant call it.

Installation

In SourceWeft

  1. Open Zambia Payments (Flutterwave — mobile money) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/app.wishpool%2Fzambia-payments-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "zambia-payments-flutterwave-mobile-money": {
      "type": "http",
      "url": "https://mcp-zm.wishpool.app/mcp"
    }
  }
}

README

This repository has no README.

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v0.1.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declaredRequired10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.

Other Wishpool integrations