FawryPay cash payments (unofficial)
PYPI · MASR-PAY-MCP-UNOFFICIAL
Unofficial MCP server for FawryPay Pay-at-Fawry cash payments in Egypt. Not affiliated with Fawry.
Available components
Last scanned (17 hours ago)
Scores higher than 56% of PyPI servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 28 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 781 tokens (~390/item across 2 items; 2 tools + 0 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (14)
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Malware scan in Supply Chain SecurityMalware scan not yet available for this package.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 3 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 2 Nov 26 +6
- Source repository: fail → pass ▲ security
- 1 Nov 26 48
First indexed and scored.
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 5 Nov 2026 · Analysed pypi/masr-pay-mcp-unofficial@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | Known build tool | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 28 packages
| Packages resolved | 28 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
create_cash_payment Create a Pay-at-Fawry cash payment ~396
Create a Fawry reference number so a customer can pay an order in CASH at any Fawry outlet in Egypt. Use it when the user wants to charge someone who will pay cash (e.g. "charge Ahmed 350 EGP for order 42, he'll pay cash"). Returns a 9-digit reference number, the total the customer pays (order amount plus any Fawry fees, in EGP) and the deadline; pass these on to the customer. Nothing is charged until the customer pays at the outlet. Each order_id can be used for only one payment. Failures: a rejected merchant code or signature means the server's credentials are wrong (not the customer's fault); a duplicate order_id means that order already has a payment, so use get_payment_status instead. Amounts above the server's per-payment limit (default 50,000 EGP) are refused before anything is sent to Fawry.
| Name | Type | Req | Description |
|---|---|---|---|
| amount_egp | – | yes | Amount in Egyptian pounds (EGP), at most two decimals, e.g. 350 or 99.50. |
| customer_email | string | yes | Customer's email address. |
| customer_mobile | string | yes | Customer's Egyptian mobile, e.g. 01012345678 (+20 forms are accepted). |
| customer_name | – | – | Optional customer name. |
| description | string | yes | What the payment is for, e.g. 'Order 42'. |
| expiry_hours | number | – | Hours the customer has to pay (default 72, max 720). |
| language | string | – | Language for Fawry's customer-facing messages: 'en-gb' or 'ar-eg'. |
| order_id | string | yes | The merchant's own order number, e.g. '42' or 'ORD-2026-0042' (letters, digits, . _ - only). It identifies the payment in every later call. |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_egp | string | yes | – |
| customer_instructions | string | yes | A ready-to-send message for the customer. |
| environment | string | yes | 'mock', 'staging' or 'production'. Only production is real money. |
| expires_at_cairo | – | yes | – |
| expires_at_utc | – | yes | – |
| fawry_fees_egp | – | yes | – |
| order_id | string | yes | – |
| raw_status | string | yes | Status exactly as Fawry returned it. |
| reference_number | string | yes | The 9-digit number the customer pays with at Fawry. |
| status | – | yes | – |
| total_to_pay_egp | string | yes | What the customer pays at the outlet (amount + fees). |
No examples provided.
get_payment_status Check a Pay-at-Fawry payment ~160
Check whether the customer has paid an order (e.g. "did Ahmed pay for order 42?"). Look up by the same order_id used in create_cash_payment. Returns a normalized status (awaiting_payment, paid, expired, canceled, refunded, failed or unknown), the raw Fawry status, when it was paid, and amounts in EGP. Safe to call as often as needed; it changes nothing. "Order not found" means no payment was ever created for that order_id.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | The merchant's own order number, e.g. '42' or 'ORD-2026-0042' (letters, digits, . _ - only). It identifies the payment in every later call. |
| Name | Type | Req | Description |
|---|---|---|---|
| amount_egp | string | yes | – |
| environment | string | yes | – |
| fawry_fees_egp | – | yes | – |
| is_paid | boolean | yes | – |
| order_id | string | yes | – |
| paid_at_cairo | – | yes | – |
| paid_at_utc | – | yes | – |
| raw_status | string | yes | Status exactly as Fawry returned it. |
| reference_number | – | yes | – |
| refunded_amount_egp | – | yes | – |
| status | – | yes | awaiting_payment | paid | expired | canceled | refunded | failed | unknown |
| summary | string | yes | One-sentence plain-English answer. |
| total_to_pay_egp | string | yes | – |
No examples provided.
How do I install the FawryPay cash payments (unofficial) MCP server?
FawryPay cash payments (unofficial) runs locally as a PyPI package, launched with uvx masr-pay-mcp-unofficial. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · masr-pay-mcp-unofficial
claude mcp add mohamedaly-cloud-masr-pay-mcp-unofficial -- uvx masr-pay-mcp-unofficial
What is the FawryPay cash payments (unofficial) MCP server?
FawryPay cash payments (unofficial) is an MCP server listed in the public MCP registry as io.github.mohamedaly-cloud/masr-pay-mcp-unofficial. Unofficial MCP server for FawryPay Pay-at-Fawry cash payments in Egypt. Not affiliated with Fawry. This page covers its PyPI package (masr-pay-mcp-unofficial).
Is the FawryPay cash payments (unofficial) MCP server safe to use?
FawryPay cash payments (unofficial) scores 54 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. 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 FawryPay cash payments (unofficial) MCP server expose?
FawryPay cash payments (unofficial) exposes 2 tools: create_cash_payment, get_payment_status. Their descriptions and schemas cost roughly 556 tokens of context every time the server is loaded.
Is the FawryPay cash payments (unofficial) MCP server still maintained?
FawryPay cash payments (unofficial) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the FawryPay cash payments (unofficial) MCP server under?
FawryPay cash payments (unofficial) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the FawryPay cash payments (unofficial) MCP server?
VerifyMCP ran 14 checks on FawryPay cash payments (unofficial), covering Known CVEs, Install scripts, Dependency health, Source repository and 10 more. 2 items could not be completed, a gap on our side rather than a finding about FawryPay cash payments (unofficial): Malware scan and Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a PyPI package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.