FawryPay cash payments (unofficial)

io.github.mohamedaly-cloudPublished by GitHub account mohamedaly-cloudv0.1.0Updated Nov 1, 2026

Unofficial MCP server for FawryPay Pay-at-Fawry cash payments in Egypt. Not affiliated with Fawry.

The publisher's own server: Payments Ai Mcp

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Unofficial local MCP server that lets an assistant work with FawryPay Pay-at-Fawry cash payments in Egypt, including optional refund and cancel tools.

What you can do
  • Connect an assistant to FawryPay Pay-at-Fawry cash payment operations in Egypt.
  • Run against a mock, staging or production FawryPay environment selected by configuration.
  • Optionally expose refund and cancel tools when destructive tools are explicitly enabled.
  • No tool list is published, so the exact operations available are not documented here.
When to use it
Worth adding when you want an assistant to help with FawryPay cash payment flows in Egypt, for example testing against a mock or staging environment before touching production. It is unofficial and not affiliated with Fawry, so it suits experimentation and merchant-side tooling rather than official support.
Requirements
Runs as a local process over stdio, installed from the PyPI package, so a Python environment is needed. Requires a FawryPay merchant code in FAWRY_MERCHANT_CODE and a secure key in FAWRY_SECURE_KEY. FAWRY_ENV selects mock (default), staging or production. Desktop only.
Before you install
The secure key in FAWRY_SECURE_KEY is a payment credential; keep it out of logs and shared configs. Setting FAWRY_ENV to production points the assistant at live payment data, so start with mock or staging. Enabling MASR_PAY_ENABLE_DESTRUCTIVE_TOOLS adds refund and cancel tools that change payment state and should be limited to merchant staff. The server is unofficial and not affiliated with Fawry.

Installation

In SourceWeft

  1. Open FawryPay cash payments (unofficial) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package did not install.

Version history

1
  1. v0.1.0LatestNov 1, 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 days25 pts

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

  • Auth declared10 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 Payments integrations