payping-mcp@0.3.0
VERIFIED· not startedPublisher claims: "Local MCP server for PayPing (payping.ir) merchants: let AI agents read balance, sales, transactions, withdrawals, customers, products, coupons and invoices, and create customers, products, payment links, coupons and invoices." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
PAYPING_TOKENConfiguration, not credentials: PAYPING_MCP_PROXY- Where it talks to
- payping.ir (its own)Also ppng.ir — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names ppng.ir as well as its own vendor. The guard injects PAYPING_TOKEN only into requests to payping.ir (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-14 and scored it 87/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
<summary><b>Claude Code</b></summary> ```bash claude mcp add payping -e PAYPING_TOKEN=your-token -- uvx payping-mcp ``` This saves the server, with the token, iFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Cursor</b></summary> Click **Install in Cursor** at the top and fill in the token, or add the Claude Desktop block to `~/.cursor/mcp.json` (or `.curFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Claude Desktop</b></summary> Settings → Developer → Edit Config, then add: ```json { "mcpServers": { "payping": { "command": "uvx", "args": ["paypinFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Gemini CLI</b></summary> Add to `~/.gemini/settings.json`: ```json { "mcpServers": { "payping": { "command": "uvx", "args": ["payping-mcp"], "env": Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Codex CLI</b></summary> ```bash codex mcp add payping --env PAYPING_TOKEN=your-token -- uvx payping-mcp ``` Or in `~/.codex/config.toml`: ```toml [mFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>VS Code (Copilot agent mode)</b></summary> Click **Install in VS Code** at the top, or add to `.vscode/mcp.json`. VS Code asks for the token once anFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>From GitHub instead of PyPI</b></summary> Replace `uvx payping-mcp` with: ```bash uvx --from git+https://github.com/sepehr071/payping-mcp payping-mcFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for payping-mcp@0.3.0 as of 34 min ago. This is the package itself, not its dependencies.