# MyFatoorah MCP (npm · myfatoorah-mcp)

Safely connect AI agents to MyFatoorah payments, invoices, payment methods, and refunds.

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-23

## Components

- npm · `myfatoorah-mcp`: 83/100 (this document), [markdown](https://verifymcp.io/servers/kuwaitdevs-myfatoorah-mcp/myfatoorah-mcp.md), [page](https://verifymcp.io/servers/kuwaitdevs-myfatoorah-mcp/myfatoorah-mcp)

## Channel facts

- Registry: `npm`
- Package: `myfatoorah-mcp`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-23.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 0 of 3 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 26 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 745 tokens (~93/item across 8 items; 7 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 90/100
  - Stability observed for 27 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 88/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add kuwaitdevs-myfatoorah-mcp -- npx -y myfatoorah-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "kuwaitdevs-myfatoorah-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "myfatoorah-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "kuwaitdevs-myfatoorah-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "myfatoorah-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add kuwaitdevs-myfatoorah-mcp -- npx -y myfatoorah-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "kuwaitdevs-myfatoorah-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "myfatoorah-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add kuwaitdevs-myfatoorah-mcp --command npx --arg -y --arg myfatoorah-mcp
```

### Hermes

```yaml
mcp_servers:
  kuwaitdevs-myfatoorah-mcp:
    command: "npx"
    args: ["-y", "myfatoorah-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "kuwaitdevs-myfatoorah-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "myfatoorah-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add kuwaitdevs-myfatoorah-mcp -t stdio -c npx -a -y myfatoorah-mcp
```

### Other

```json
{
  "mcpServers": {
    "kuwaitdevs-myfatoorah-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "myfatoorah-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-22 (score 83, +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.

### 2026-09-20 (score 82, +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.

### 2026-09-18 (score 81, +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.

### 2026-09-16 (score 80, +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.

### 2026-09-13 (score 79, +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.

### 2026-09-11 (score 78, +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.

### 2026-09-09 (score 77, +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.

### 2026-09-07 (score 76, +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.

## MCP tools (7)

### `myfatoorah_get_payment_methods` (~39 tokens)

Get MyFatoorah payment methods

List payment methods enabled for this account. Read ApiName from the result and pass it as paymentMethod when creating a hosted payment.

Output parameters:

- `response` (object)

### `myfatoorah_create_payment` (~243 tokens)

Create MyFatoorah payment or invoice link

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.

Input parameters:

- `advanced` (object): Additional documented v3 request fields. Explicit fields above take precedence.
- `amount` (number, required): 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.

Output parameters:

- `response` (object)

### `myfatoorah_get_payment` (~63 tokens)

Get MyFatoorah payment details

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.

Input parameters:

- `paymentId` (string, required): PaymentId from a callback or payment response.

Output parameters:

- `response` (object)

### `myfatoorah_get_invoice` (~76 tokens)

Get MyFatoorah invoice

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}.

Input parameters:

- `lookupBy` (string, required)
- `value` (string, required): Invoice ID or merchant-provided external identifier.

Output parameters:

- `response` (object)

### `myfatoorah_create_refund` (~128 tokens)

Create a MyFatoorah refund

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.

Input parameters:

- `amount` (number, required)
- `comment` (string)
- `confirm` (boolean, required): Must be true after explicit user approval.
- `externalIdentifier` (string)
- `idempotencyKey` (string)
- `paymentId` (string, required)
- `serviceChargeOnCustomer` (boolean)
- `supplierRefundedAmount` (array)

Output parameters:

- `response` (object)

### `myfatoorah_get_refund` (~50 tokens)

Get MyFatoorah refund details

Gets a refund by RefundId using GET /v3/refunds/{refundId}. Refund statuses include Refunded, Canceled, and Pending.

Input parameters:

- `refundId` (string, required)

Output parameters:

- `response` (object)

### `myfatoorah_api_request` (~127 tokens)

Advanced MyFatoorah API request

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.

Input parameters:

- `body`
- `confirm` (boolean): Must be true for POST or PUT.
- `idempotencyKey` (string)
- `method` (string)
- `path` (string, required): Relative path beginning with /v2/ or /v3/.

Output parameters:

- `response` (object)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/kuwaitdevs-myfatoorah-mcp/myfatoorah-mcp#diagnostics

## Score history

- 2026-09-23: 83
- 2026-09-22: 83
- 2026-09-21: 82
- 2026-09-20: 82
- 2026-09-19: 81
- 2026-09-18: 81
- 2026-09-17: 80
- 2026-09-16: 80
- 2026-09-15: 79
- 2026-09-14: 79
- 2026-09-13: 79
- 2026-09-12: 78
- 2026-09-11: 78
- 2026-09-10: 77
- 2026-09-09: 77
- 2026-09-08: 76
- 2026-09-07: 76
- 2026-09-06: 75
- 2026-09-05: 75
- 2026-09-04: 74
- 2026-09-03: 74
- 2026-09-02: 71
- 2026-09-01: 71
- 2026-08-31: 71
- 2026-08-30: 71
- 2026-08-29: 71
- 2026-08-28: 71
- 2026-08-27: 56

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/myfatoorah-mcp
- Socket report: https://socket.dev/npm/package/myfatoorah-mcp
- Repository: https://github.com/kuwaitdevs/myfatoorah-mcp
- Changelog RSS feed: https://verifymcp.io/servers/kuwaitdevs-myfatoorah-mcp/myfatoorah-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/kuwaitdevs-myfatoorah-mcp/myfatoorah-mcp.json
- HTML version of this page: https://verifymcp.io/servers/kuwaitdevs-myfatoorah-mcp/myfatoorah-mcp