PayPing
PYPI · PAYPING-MCP
PayPing merchant account for agents: balance, sales, invoices; create invoices and payment links.
Available components
Last scanned (10 hours ago)
Scores higher than 66% 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 31 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to sepehr071/payping-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1792 tokens (~85/item across 21 items; 21 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability check failed: the tool surface changed between 0.1.0 and 0.2.1: 0 tool removals, 21 breaking changes, 0 additions. See how to fix → Fail
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 67% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 22 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
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 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 21 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 20 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- 18 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 17 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 16 Oct 26 −6
- Stability: 0.37 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.37 → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: excellent → good functional
- Package version: 0.1.2 → 0.2.0 functional
- 15 Oct 26 +37
- Injection markers: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.37 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Package version: 0.1.0 → 0.1.2 functional
- 13 Oct 26 0
- Malware scan: pass → unverified ▼ security
- Package version: 0.1.0 → 0.1.2 functional
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 22 Oct 2026 · Analysed pypi/payping-mcp@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | sepehr071/payping-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/sepehr071/payping-mcp/.github/workflows/publish.yml@refs/tags/v0.2.1 |
| Rekor log index | 3390416963 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:87883c7726b6e7df65a95c752dad362198336c230c0baac8a732316b59804def |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 31 packages
| Packages resolved | 31 |
|---|---|
| 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 →
payping_create_coupon PayPing: create coupon ~124
Create an active discount coupon and return its `code`. Creates real data: confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | 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 | yes | 'percent' off, or a fixed Toman amount off. |
| max_uses | – | – | – |
| name | string | yes | – |
| product_codes | – | – | Limit to these products; omit for all. |
No output schema declared.
No examples provided.
payping_create_customer PayPing: create customer ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| business_name | – | – | – |
| – | – | – | |
| first_name | string | yes | – |
| is_business | boolean | – | True for a company (legal person). |
| last_name | string | yes | – |
| memo | – | – | Private note. |
| national_id | – | – | National code or economic code. |
| phone | – | – | Mobile number, e.g. 09121234567. |
No output schema declared.
No examples provided.
payping_create_invoice PayPing: create invoice ~114
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.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_code | string | yes | From payping_create_customer. |
| due_date | – | – | Pay by this day (YYYY-MM-DD). |
| items | array | yes | – |
| notes | – | – | Shown to the customer. |
| title | – | – | – |
No output schema declared.
No examples provided.
payping_create_payment_link PayPing: create payment link ~82
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ask_address | boolean | – | Ask the payer for a postal address. |
| product_code | string | yes | – |
| redirect_url | – | – | https:// page to open after payment. |
No output schema declared.
No examples provided.
payping_create_product PayPing: create product ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
No output schema declared.
No examples provided.
payping_get_balance PayPing: wallet balance ~26
Current PayPing wallet balance in Toman (money received and not yet withdrawn).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
payping_get_coupon PayPing: coupon detail ~37
One coupon by code: amount, expiry, max uses, number of buyers and their total spend.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
payping_get_customer PayPing: customer detail ~34
One customer by code: name, contact details, address, national id, memo.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
payping_get_invoice PayPing: invoice detail ~45
One invoice by code with its items, customer, status and payment code, plus `url`, the public page where the customer pays.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
payping_get_payment PayPing: payment detail ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
payping_get_product PayPing: product detail ~39
One product by code: title, description, price (Toman), stock, tax, image, category.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
payping_get_profile PayPing: account profile ~39
Show the PayPing account behind PAYPING_TOKEN: username, name, email, phone and verification flags. Use first to confirm the token works.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
payping_get_sales_summary PayPing: sales summary ~69
Sales totals for a period: total amount (Toman), transaction count and daily averages. Defaults to the last 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | – | – | First day to include (YYYY-MM-DD, UTC). |
| to_date | – | – | Last day to include (YYYY-MM-DD, UTC). |
No output schema declared.
No examples provided.
payping_get_withdrawal PayPing: withdrawal detail ~43
Detail of one settlement by code: amount (Toman), request and payout dates, IBAN, bank tracking number.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
payping_list_coupons PayPing: list coupons ~90
List discount coupons: name, type (0 = percent, 1 = Toman), amount, code, active, products it applies to.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
payping_list_customers PayPing: list customers ~68
List saved customers (code, name, phone, email, business name) with the total count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items to return, 1-50. |
| offset | integer | – | Skip this many items (paging). |
| search | – | – | Text to search for. |
No output schema declared.
No examples provided.
payping_list_invoices PayPing: list invoices ~102
List invoices: code, number, title, status (0 draft, 1 awaiting payment, 2 paid, 3 overdue, 4 cancelled), total (Toman), due and paid dates, customer.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_code | – | – | – |
| limit | integer | – | Items to return, 1-50. |
| offset | integer | – | Skip this many items (paging). |
| search | – | – | Text to search for. |
| status | – | – | – |
No output schema declared.
No examples provided.
payping_list_products PayPing: list products ~86
List products (PayPing "financial items"): code, title, price (Toman), stock, active, has a payment link.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
payping_list_transactions PayPing: list transactions ~139
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
payping_list_withdrawals PayPing: list withdrawals ~71
List settlements (withdrawals to your bank account): date, amount (Toman), code and whether it was paid out, plus the total count.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Items to return, 1-50. |
| offset | integer | – | Skip this many items (paging). |
No output schema declared.
No examples provided.
payping_send_invoice PayPing: send invoice ~43
Send an invoice to its customer by SMS/email from PayPing. Messages a real person: confirm with the user before calling.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
No output schema declared.
No examples provided.
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.
pypi · payping-mcp
claude mcp add sepehr071-payping-mcp -- uvx payping-mcp
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.