io.github.mrslbt/paypay-mcp
NPM · PAYPAY-MCP
PayPay QR payments for AI agents: QR codes, status, refunds, cancels. Bilingual JP/EN.
Available components
Last scanned (6 hours ago)
Scores higher than 64% of npm 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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 41 of 122 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 87 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1120 tokens (~160/item across 7 items; 4 tools + 3 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 0
- Stability: 0.97 → pass security
- 28 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 22 Oct 26 0
- Stability: 0.97 → pass security
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 7 Nov 2026 · Analysed npm/paypay-mcp@0.2.1
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 →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 122 packages
| Packages resolved | 122 |
|---|---|
| Stale | 41 |
| 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_qr_code Create PayPay QR Code ~356
Create a dynamic PayPay QR code that a customer can scan to pay. Returns the QR code both as a URL (deeplink + hosted image) and as an inline PNG image. Use `wait_for_payment` to poll until the customer completes the payment. 顧客がスキャンして支払うためのPayPay動的QRコードを作成します。 QRコードのURL(ディープリンクとホストされた画像)とインラインPNG画像の両方を返します。 顧客が支払いを完了するまで `wait_for_payment` でポーリングしてください。
| Name | Type | Req | Description |
|---|---|---|---|
| amount | integer | yes | Amount in JPY (integer, no decimals). 金額(円、整数)。 |
| code_type | string | – | QR code type. Currently only ORDER_QR is supported. |
| is_authorization | boolean | – | If true, this is a pre-auth (hold funds now, capture later). 事前承認(preauth)フラグ。 |
| merchant_payment_id | string | – | Unique ID for this payment. Auto-generated (UUID) if omitted. Reusing an ID for a different order will fail. 注文ごとの一意のID。省略時は自動生成。 |
| order_description | string | yes | What the customer is paying for. 注文内容。 |
| order_items | array | – | Optional line-item breakdown shown in the PayPay app. 商品明細(任意)。 |
| redirect_type | string | – | How the redirect should open: browser (WEB_LINK) or app (APP_DEEP_LINK). |
| redirect_url | string | – | Where to send the user after they complete payment in the PayPay app. |
No output schema declared.
No examples provided.
delete_qr_code Delete PayPay QR Code ~121
Invalidate a QR code before it is paid. Cannot be used after payment has completed. Use this when an order is canceled before checkout, or to clean up expired codes. 支払い前のQRコードを無効化します。決済完了後は使用できません。 注文がキャンセルされた場合や、期限切れのコードを整理する際に使用してください。
| Name | Type | Req | Description |
|---|---|---|---|
| code_id | string | yes | The codeId returned from create_qr_code (NOT the merchantPaymentId). create_qr_codeで返されたcodeId。 |
No output schema declared.
No examples provided.
get_payment_details Get PayPay Payment Details ~158
Fetch the current status and details of a payment by merchantPaymentId. Returns status: CREATED | AUTHORIZED | COMPLETED | REFUNDED | FAILED | CANCELED. Use this for one-off status checks. For active polling, prefer `wait_for_payment`. merchantPaymentIdで指定した取引の現在のステータスと詳細を取得します。 ステータス: CREATED / AUTHORIZED / COMPLETED / REFUNDED / FAILED / CANCELED。 単発の確認に使用してください。継続的な確認は `wait_for_payment` を推奨します。
| Name | Type | Req | Description |
|---|---|---|---|
| merchant_payment_id | string | yes | The merchantPaymentId used when creating the QR code. QR作成時のmerchantPaymentId。 |
No output schema declared.
No examples provided.
wait_for_payment Wait for PayPay Payment ~202
Poll PayPay until a payment reaches a terminal state (COMPLETED, AUTHORIZED, REFUNDED, FAILED, CANCELED) or the timeout elapses. Uses PayPay's recommended 2–3s polling interval by default. Returns the final status and full payment detail. 取引が終了状態(COMPLETED / AUTHORIZED / REFUNDED / FAILED / CANCELED)に達するかタイムアウトするまで、PayPayをポーリングします。 PayPay推奨の2〜3秒間隔をデフォルトで使用します。 最終ステータスと取引詳細を返します。
| Name | Type | Req | Description |
|---|---|---|---|
| merchant_payment_id | string | yes | The merchantPaymentId of the payment to wait on. |
| poll_interval_seconds | number | – | How often to poll (seconds). PayPay recommends 2–3s. |
| timeout_seconds | integer | – | Give up after this many seconds. Default: 120. |
No output schema declared.
No examples provided.
How do I install the io.github.mrslbt/paypay-mcp server?
io.github.mrslbt/paypay-mcp runs locally as an npm package, launched with npx -y paypay-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 · paypay-mcp
claude mcp add mrslbt-paypay-mcp -- npx -y paypay-mcp
What is the io.github.mrslbt/paypay-mcp server?
io.github.mrslbt/paypay-mcp is listed in the public MCP registry as io.github.mrslbt/paypay-mcp. PayPay QR payments for AI agents: QR codes, status, refunds, cancels. Bilingual JP/EN. This page covers its npm package (paypay-mcp).
Is the io.github.mrslbt/paypay-mcp server safe to use?
io.github.mrslbt/paypay-mcp scores 80 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 7 November 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 io.github.mrslbt/paypay-mcp server expose?
io.github.mrslbt/paypay-mcp exposes 4 tools: create_qr_code, get_payment_details, wait_for_payment, delete_qr_code. Their descriptions and schemas cost roughly 837 tokens of context every time the server is loaded.
Is the io.github.mrslbt/paypay-mcp server still maintained?
io.github.mrslbt/paypay-mcp is still listed as active in the MCP registry. We last reached this channel on 7 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 io.github.mrslbt/paypay-mcp server under?
io.github.mrslbt/paypay-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.
What did VerifyMCP test on the io.github.mrslbt/paypay-mcp server?
VerifyMCP ran 16 checks on io.github.mrslbt/paypay-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.