Index / payments

io.github.mrslbt/paypay-mcp

io-github-mrslbt-paypay-mcp declares 4 capabilities across 4 tools, with 3 critical issues. One of them, no-revocation, is recorded for every server in the index because MCP has no field in which to declare a way to switch a tool off; a missing declaration is not evidence that the control is missing.

40/100 exposureElevated

Manifest recorded 2026-10-30 from tools/list answered by the npm package paypay-mcp@0.2.1 (published to npm as paypay-mcp, listed in the official MCP registry as io.github.mrslbt/paypay-mcp 0.2.1), run in an isolated container with no network access and no credentials. The date changes only when the manifest does. Not verified by a maintainer.

Issues

These describe what this server's manifest declares. A product can provide controls that MCP has no way to express — token revocation, an admin console, audit logs — and this page cannot see them. The absence of a declaration is not evidence that a control is absent.

critical · no-revocation · All 4 tools

4 of 4 tools declare no way for the customer to switch them off once granted. This applies to every tool because MCP has no field in which to declare a revocation mechanism; the product may provide one outside MCP that a manifest cannot show.

critical · irreversible-uncapped · 2 of 4 tools

2 tools are classified as irreversible or destructive and declare no limit. 1 of them is counted only because the server annotated it destructiveHint. In MCP that annotation marks a tool that may make destructive changes rather than only additive ones; it does not say the change cannot be undone.

critical · uncapped-spend · 1 of 4 tools

1 tool is classified as moving money and declares no dollar limit. A cap on the number of payments does not bound their amount.

high · no-expiry · All 4 tools

4 of 4 tools declare no expiry. This applies to every tool because MCP has no field in which to declare an expiry; the product may provide one outside MCP that a manifest cannot show.

high · no-audit-trail · All 4 tools

4 of 4 tools declare no record of their actions that the customer can read. This applies to every tool because MCP has no field in which to declare an audit requirement; the product may provide one outside MCP that a manifest cannot show.

high · uncapped-write · 1 of 4 tools

1 tool can modify data and declares no limit.

low · uncapped-read · 1 of 4 tools

1 tool can read data and declares no limit.

Declared capabilities

How each tool was read. declared means the server's own annotation said so — self-reported and unverified. inferred is from the tool's name. assumed means nothing indicated either way.

Tool	Read as	Basis
`create_qr_code`	`write`	inferred
`get_payment_details`	`read`	declared
`wait_for_payment`	`pay`	inferred
`delete_qr_code`	`destructive`	declared

Answering this question about your own agent? The self-serve stack report applies the same reading to your own stack or server and gives you a dated document you can hand to a customer's security review. It is generated in your browser, with nobody to wait for. Buying one does not change this page, its score or its place in the index — see Independence.

Maintain this server? If this page misreads your manifest, or your server has changed, submit its current tools/list response and it will be re-scored and dated. Corrections are published alongside the original, not in place of it.