# PayPing (pypi · payping-mcp)

PayPing merchant account for agents: balance, sales, invoices; create invoices and payment links.

- Trust score: 67/100 (medium)
- Change this week: −19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- pypi · `payping-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/sepehr071-payping-mcp/payping-mcp.md), [page](https://verifymcp.io/servers/sepehr071-payping-mcp/payping-mcp)

## Channel facts

- Registry: `pypi`
- Package: `payping-mcp`
- Version: `0.2.1`
- 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-10-22.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to sepehr071/payping-mcp).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 76/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1792 tokens (~85/item across 21 items; 21 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 10/100
  - Stability check failed: the tool surface changed between 0.1.0 and 0.2.1: 0 tool removals, 21 breaking changes, 0 additions.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 22 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 PayPing MCP server?

PayPing runs locally as a PyPI package, launched with uvx payping-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 sepehr071-payping-mcp -- uvx payping-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "sepehr071-payping-mcp": {
      "command": "uvx",
      "args": [
        "payping-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "sepehr071-payping-mcp": {
      "command": "uvx",
      "args": [
        "payping-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add sepehr071-payping-mcp -- uvx payping-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "sepehr071-payping-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "payping-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add sepehr071-payping-mcp --command uvx --arg payping-mcp
```

### Hermes

```yaml
mcp_servers:
  sepehr071-payping-mcp:
    command: "uvx"
    args: ["payping-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "sepehr071-payping-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "payping-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add sepehr071-payping-mcp -t stdio -c uvx -a payping-mcp
```

### Other

```json
{
  "mcpServers": {
    "sepehr071-payping-mcp": {
      "command": "uvx",
      "args": [
        "payping-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-10-22 (score 67, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-21 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-20 (score 81, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-18 (score 80, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-17 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-10-16 (score 80, −6)

- [security regression] Stability: 0.37 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Stability: 0.37 → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] Schema quality: excellent → good
- [functional] Package version: 0.1.2 → 0.2.0

### 2026-10-15 (score 86, +37)

- [security improvement] Injection markers: unverified → pass
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Stability: unverified → 0.37
- [functional improvement] MCP protocol: unverified → pass
- [functional] Package version: 0.1.0 → 0.1.2

### 2026-10-13 (score 49, 0)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.1.0 → 0.1.2

## MCP tools (21)

### `payping_get_profile` (~39 tokens)

PayPing: account profile

Show the PayPing account behind PAYPING_TOKEN: username, name, email, phone and verification flags.
Use first to confirm the token works.

### `payping_get_balance` (~26 tokens)

PayPing: wallet balance

Current PayPing wallet balance in Toman (money received and not yet withdrawn).

### `payping_get_sales_summary` (~69 tokens)

PayPing: sales summary

Sales totals for a period: total amount (Toman), transaction count and daily averages.
Defaults to the last 30 days.

Input parameters:

- `from_date`: First day to include (YYYY-MM-DD, UTC).
- `to_date`: Last day to include (YYYY-MM-DD, UTC).

### `payping_list_transactions` (~139 tokens)

PayPing: list transactions

List payments (newest first) with amount (Toman), payer, description, isPaid and payment code, plus the
total count for the same filter. Use payping_get_payment with a code for full detail.

Input parameters:

- `from_date`: First day to include (YYYY-MM-DD, UTC).
- `kind`: 'received' = payments to you, 'paid' = payments you made; omit for both.
- `limit` (integer): Items to return, 1-50.
- `offset` (integer): Skip this many items (paging).
- `to_date`: Last day to include (YYYY-MM-DD, UTC).

### `payping_get_payment` (~53 tokens)

PayPing: payment detail

One payment by payment code: amount, dates, payer, card, fees, refund state, paymentStatus plus
status_text. Use it to check whether a payment really succeeded.

Input parameters:

- `code` (string, required)

### `payping_list_withdrawals` (~71 tokens)

PayPing: list withdrawals

List settlements (withdrawals to your bank account): date, amount (Toman), code and whether it was paid
out, plus the total count.

Input parameters:

- `limit` (integer): Items to return, 1-50.
- `offset` (integer): Skip this many items (paging).

### `payping_get_withdrawal` (~43 tokens)

PayPing: withdrawal detail

Detail of one settlement by code: amount (Toman), request and payout dates, IBAN, bank tracking number.

Input parameters:

- `code` (string, required)

### `payping_list_customers` (~68 tokens)

PayPing: list customers

List saved customers (code, name, phone, email, business name) with the total count.

Input parameters:

- `limit` (integer): Items to return, 1-50.
- `offset` (integer): Skip this many items (paging).
- `search`: Text to search for.

### `payping_get_customer` (~34 tokens)

PayPing: customer detail

One customer by code: name, contact details, address, national id, memo.

Input parameters:

- `code` (string, required)

### `payping_list_products` (~86 tokens)

PayPing: list products

List products (PayPing "financial items"): code, title, price (Toman), stock, active, has a payment link.

Input parameters:

- `include_archived` (boolean): Include archived items.
- `limit` (integer): Items to return, 1-50.
- `offset` (integer): Skip this many items (paging).
- `search`: Text to search for.

### `payping_get_product` (~39 tokens)

PayPing: product detail

One product by code: title, description, price (Toman), stock, tax, image, category.

Input parameters:

- `code` (string, required)

### `payping_list_coupons` (~90 tokens)

PayPing: list coupons

List discount coupons: name, type (0 = percent, 1 = Toman), amount, code, active, products it applies to.

Input parameters:

- `include_archived` (boolean): Include archived items.
- `limit` (integer): Items to return, 1-50.
- `offset` (integer): Skip this many items (paging).
- `search`: Text to search for.

### `payping_get_coupon` (~37 tokens)

PayPing: coupon detail

One coupon by code: amount, expiry, max uses, number of buyers and their total spend.

Input parameters:

- `code` (string, required)

### `payping_list_invoices` (~102 tokens)

PayPing: list invoices

List invoices: code, number, title, status (0 draft, 1 awaiting payment, 2 paid, 3 overdue, 4 cancelled),
total (Toman), due and paid dates, customer.

Input parameters:

- `customer_code`
- `limit` (integer): Items to return, 1-50.
- `offset` (integer): Skip this many items (paging).
- `search`: Text to search for.
- `status`

### `payping_get_invoice` (~45 tokens)

PayPing: invoice detail

One invoice by code with its items, customer, status and payment code, plus `url`, the public page where
the customer pays.

Input parameters:

- `code` (string, required)

### `payping_create_customer` (~121 tokens)

PayPing: create customer

Save a new customer in the PayPing account and return it with its `code` (needed for invoices).
Creates real data: confirm the details with the user before calling.

Input parameters:

- `business_name`
- `email`
- `first_name` (string, required)
- `is_business` (boolean): True for a company (legal person).
- `last_name` (string, required)
- `memo`: Private note.
- `national_id`: National code or economic code.
- `phone`: Mobile number, e.g. 09121234567.

### `payping_create_product` (~120 tokens)

PayPing: create product

Create a product (financial item) and return its `code`. Then payping_create_payment_link makes a public
payment page for it. Creates real data: confirm title and price with the user before calling.

Input parameters:

- `amount_set_by_payer` (boolean): Payer types the amount (donations); no price.
- `amount_toman`: Price in Toman.
- `description`
- `has_tax` (boolean): Add VAT to the price.
- `quantity`: Stock; omit for unlimited.
- `title` (string, required)

### `payping_create_payment_link` (~82 tokens)

PayPing: create payment link

Make a permanent public payment page for a product; returns its `url` (https://ppng.ir/d/...).
Creates real data: confirm with the user before calling.

Input parameters:

- `ask_address` (boolean): Ask the payer for a postal address.
- `product_code` (string, required)
- `redirect_url`: https:// page to open after payment.

### `payping_create_coupon` (~124 tokens)

PayPing: create coupon

Create an active discount coupon and return its `code`. Creates real data: confirm with the user first.

Input parameters:

- `amount` (integer, required): Percent (1-100) or Toman, per `kind`.
- `coupon_code`: Code buyers type; omit to generate.
- `expires_on`: Last valid day (YYYY-MM-DD).
- `kind` (string, required): 'percent' off, or a fixed Toman amount off.
- `max_uses`
- `name` (string, required)
- `product_codes`: Limit to these products; omit for all.

### `payping_create_invoice` (~114 tokens)

PayPing: create invoice

Create an invoice for a saved customer; returns `code`, `payCode` and `url` (public pay page). Not sent:
call payping_send_invoice or share the url. Creates real data: confirm customer, items and prices with the
user before calling.

Input parameters:

- `customer_code` (string, required): From payping_create_customer.
- `due_date`: Pay by this day (YYYY-MM-DD).
- `items` (array, required)
- `notes`: Shown to the customer.
- `title`

### `payping_send_invoice` (~43 tokens)

PayPing: send invoice

Send an invoice to its customer by SMS/email from PayPing. Messages a real person: confirm with the user
before calling.

Input parameters:

- `code` (string, required)

## Diagnostics

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

## Score history

- 2026-10-22: 67
- 2026-10-21: 81
- 2026-10-20: 81
- 2026-10-19: 80
- 2026-10-18: 80
- 2026-10-17: 65
- 2026-10-16: 80
- 2026-10-15: 86
- 2026-10-14: 49
- 2026-10-13: 49
- 2026-10-12: 49
- 2026-10-04: 66

## Common questions

### What is the PayPing MCP server?

PayPing is an MCP server listed in the public MCP registry as io.github.sepehr071/payping-mcp. PayPing merchant account for agents: balance, sales, invoices; create invoices and payment links. This page covers its PyPI package (payping-mcp).

### Is the PayPing MCP server safe to use?

PayPing scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 2026. Its build provenance is signed and verified. 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 PayPing MCP server expose?

PayPing exposes 21 tools: payping_get_profile, payping_get_balance, payping_get_sales_summary, payping_list_transactions, payping_get_payment, and 16 more. Their descriptions and schemas cost roughly 1,545 tokens of context every time the server is loaded.

### Is the PayPing MCP server still maintained?

PayPing is still listed as active in the MCP registry. We last reached this channel on 22 October 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 PayPing MCP server under?

PayPing 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

- PyPI project: https://pypi.org/project/payping-mcp/
- Socket report: https://socket.dev/pypi/package/payping-mcp
- Repository: https://github.com/sepehr071/payping-mcp
- Changelog RSS feed: https://verifymcp.io/servers/sepehr071-payping-mcp/payping-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/sepehr071-payping-mcp/payping-mcp.json
- HTML version of this page: https://verifymcp.io/servers/sepehr071-payping-mcp/payping-mcp