MyFatoorah MCP
NPM · MYFATOORAH-MCP · SCANNED SEP 23
Safely connect AI agents to MyFatoorah payments, invoices, payment methods, and refunds.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency48
- 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 26 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 745 tokens (~93/item across 8 items; 7 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management90
- Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 38% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety88
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "myfatoorah_get_refund" implies "refund" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 8 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
How do I install the MyFatoorah MCP server?
MyFatoorah MCP runs locally as an npm package, launched with npx -y myfatoorah-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · myfatoorah-mcp
claude mcp add kuwaitdevs-myfatoorah-mcp -- npx -y myfatoorah-mcp
{
"mcpServers": {
"kuwaitdevs-myfatoorah-mcp": {
"command": "npx",
"args": [
"-y",
"myfatoorah-mcp"
]
}
}
} {
"servers": {
"kuwaitdevs-myfatoorah-mcp": {
"command": "npx",
"args": [
"-y",
"myfatoorah-mcp"
]
}
}
} codex mcp add kuwaitdevs-myfatoorah-mcp -- npx -y myfatoorah-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"kuwaitdevs-myfatoorah-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"myfatoorah-mcp"
],
"enabled": true
}
}
} openclaw mcp add kuwaitdevs-myfatoorah-mcp --command npx --arg -y --arg myfatoorah-mcp
mcp_servers:
kuwaitdevs-myfatoorah-mcp:
command: "npx"
args: ["-y", "myfatoorah-mcp"] {
"McpServers": {
"kuwaitdevs-myfatoorah-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"myfatoorah-mcp"
]
}
}
} assistant mcp add kuwaitdevs-myfatoorah-mcp -t stdio -c npx -a -y myfatoorah-mcp
{
"mcpServers": {
"kuwaitdevs-myfatoorah-mcp": {
"command": "npx",
"args": [
"-y",
"myfatoorah-mcp"
]
}
}
} 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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
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 23 Sept 2026 · Analysed npm/myfatoorah-mcp@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 | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| 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 →
myfatoorah_api_request Advanced MyFatoorah API request ~127
Escape hatch for documented MyFatoorah v2/v3 endpoints not covered by another tool. Accepts only safe relative /v2/ or /v3/ paths and GET, POST, or PUT. Absolute URLs are blocked so credentials cannot be sent elsewhere. POST/PUT require confirm=true.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| confirm | boolean | – | Must be true for POST or PUT. |
| idempotencyKey | string | – | – |
| method | string | – | – |
| path | string | yes | Relative path beginning with /v2/ or /v3/. |
| Name | Type | Req | Description |
|---|---|---|---|
| response | object | yes | – |
No examples provided.
myfatoorah_create_payment Create MyFatoorah payment or invoice link ~243
Creates a payment/invoice using POST /v3/payments. In a live environment this creates a real payable invoice. Omit paymentMethod to show all enabled methods; use notificationOption for invoicing. The returned PaymentURL is where the customer pays.
| Name | Type | Req | Description |
|---|---|---|---|
| advanced | object | – | Additional documented v3 request fields. Explicit fields above take precedence. |
| amount | number | yes | Payment amount; must be greater than zero. |
| currency | string | – | Display currency. Defaults to the account base currency. |
| customer | object | – | – |
| displayPaymentMethods | array | – | – |
| externalIdentifier | string | – | – |
| idempotencyKey | string | – | – |
| language | string | – | – |
| notificationOption | string | – | – |
| paymentExpiry | string | – | UTC ISO-8601 expiration time. |
| paymentMethod | string | – | ApiName from myfatoorah_get_payment_methods; omit to show enabled methods. |
| redirectionUrl | string | – | Customer return URL after payment. |
| suppliers | array | – | – |
| userDefinedFields | object | – | – |
| webhookUrl | string | – | Per-payment webhook URL. |
| Name | Type | Req | Description |
|---|---|---|---|
| response | object | yes | – |
No examples provided.
myfatoorah_create_refund Create a MyFatoorah refund ~128
Creates a real full or partial refund using POST /v3/refunds. This moves money in live environments. Call only after the user explicitly approves the exact PaymentId and amount; confirm must be true.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | number | yes | – |
| comment | string | – | – |
| confirm | boolean | yes | Must be true after explicit user approval. |
| externalIdentifier | string | – | – |
| idempotencyKey | string | – | – |
| paymentId | string | yes | – |
| serviceChargeOnCustomer | boolean | – | – |
| supplierRefundedAmount | array | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| response | object | yes | – |
No examples provided.
myfatoorah_get_invoice Get MyFatoorah invoice ~76
Gets an invoice by exactly one lookup type. Invoice ID uses /v3/invoices/{value}; external identifier returns the most recent matching invoice and uses /v3/invoices/externalIdentifier/{value}.
| Name | Type | Req | Description |
|---|---|---|---|
| lookupBy | string | yes | – |
| value | string | yes | Invoice ID or merchant-provided external identifier. |
| Name | Type | Req | Description |
|---|---|---|---|
| response | object | yes | – |
No examples provided.
myfatoorah_get_payment Get MyFatoorah payment details ~63
Gets authoritative payment details by PaymentId using GET /v3/payments/{paymentId}. Treat payment as successful only when Invoice.Status is PAID and Transaction.Status is SUCCESS.
| Name | Type | Req | Description |
|---|---|---|---|
| paymentId | string | yes | PaymentId from a callback or payment response. |
| Name | Type | Req | Description |
|---|---|---|---|
| response | object | yes | – |
No examples provided.
myfatoorah_get_payment_methods Get MyFatoorah payment methods ~39
List payment methods enabled for this account. Read ApiName from the result and pass it as paymentMethod when creating a hosted payment.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| response | object | yes | – |
No examples provided.
myfatoorah_get_refund Get MyFatoorah refund details ~50
Gets a refund by RefundId using GET /v3/refunds/{refundId}. Refund statuses include Refunded, Canceled, and Pending.
| Name | Type | Req | Description |
|---|---|---|---|
| refundId | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| response | object | yes | – |
No examples provided.
What is the MyFatoorah MCP server?
MyFatoorah MCP is listed in the public MCP registry as io.github.kuwaitdevs/myfatoorah-mcp. Safely connect AI agents to MyFatoorah payments, invoices, payment methods, and refunds. This page covers its npm package (myfatoorah-mcp).
Is the MyFatoorah MCP server safe to use?
MyFatoorah MCP scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 23 September 2026. It declares no install or post-install scripts. 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 MyFatoorah MCP server expose?
MyFatoorah MCP exposes 7 tools: myfatoorah_get_payment_methods, myfatoorah_create_payment, myfatoorah_get_payment, myfatoorah_get_invoice, myfatoorah_create_refund, and 2 more. Their descriptions and schemas cost roughly 726 tokens of context every time the server is loaded.
Is the MyFatoorah MCP server still maintained?
MyFatoorah MCP is still listed as active in the MCP registry. We last reached this channel on 23 September 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 MyFatoorah MCP server under?
MyFatoorah MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.