Payzu Mcp Pix MCP Server

payzu-mcp-pix npm v0.7.0 Source verified

Published by payzuai — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server for PayZu Pix Processamento API. 29 tools: Pix charges, withdrawals, transfers, callbacks, MED infractions. Works with Antigravity, Claude Code, Claude Desktop, Cursor, Windsurf.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 3

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([reports_download]) co-exist with external-action tools ([callbacks_resend_webhook, webhooks_create, webhooks_get, webhooks_update, webhooks_delete, webhooks_rotate_secret]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [reports_download] → sinks [callbacks_resend_webhook, webhooks_create, webhooks_get, webhooks_update, webhooks_delete, webhooks_rotate_secret]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow reports_download → callbacks_resend_webhook

medium Unconstrained URL/host parameter "url" on "webhooks_create"MTC-CAP-007

Tool "webhooks_create" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool webhooks_create · inputSchema.properties.url

medium Unconstrained URL/host parameter "url" on "webhooks_update"MTC-CAP-007

Tool "webhooks_update" takes a URL/host parameter "url" with no allowlist/pattern. An outbound-request tool with an unbounded destination enables SSRF and cloud-metadata access (e.g. 169.254.169.254).

Fix: Allowlist destinations or constrain the parameter; block private/link-local addresses server-side.

Location: tool webhooks_update · inputSchema.properties.url

Tools 45

Each tool and what it can reach — statically extracted from the published source.

  • callbacks_resend_webhooknetwork egress
  • reports_downloadingests untrusted input
  • webhooks_createnetwork egress
  • webhooks_deletenetwork egress
  • webhooks_getnetwork egress
  • webhooks_rotate_secretnetwork egress
  • webhooks_updatenetwork egress
  • account_balanceno sensitive capability
  • account_pix_keysno sensitive capability
  • account_profileno sensitive capability
Show 35 more tools ↓
  • callbacks_getno sensitive capability
  • callbacks_listno sensitive capability
  • callbacks_resendno sensitive capability
  • callbacks_resend_bulkno sensitive capability
  • infractions_create_defenseno sensitive capability
  • infractions_getno sensitive capability
  • infractions_get_defenseno sensitive capability
  • infractions_listno sensitive capability
  • infractions_list_defensesno sensitive capability
  • internal_transfer_createno sensitive capability
  • internal_transfer_getno sensitive capability
  • pix_createno sensitive capability
  • pix_getno sensitive capability
  • pix_proofno sensitive capability
  • pix_qr_codeno sensitive capability
  • refund_createno sensitive capability
  • reports_bank_statementno sensitive capability
  • reports_bank_statementsno sensitive capability
  • reports_create_csvno sensitive capability
  • reports_deposit_pendingno sensitive capability
  • reports_deposit_pending_getno sensitive capability
  • reports_get_jobno sensitive capability
  • reports_get_transactionno sensitive capability
  • reports_list_jobsno sensitive capability
  • reports_list_transactionsno sensitive capability
  • reports_summaryno sensitive capability
  • webhooks_listno sensitive capability
  • webhooks_sent_detailno sensitive capability
  • webhooks_sent_quantityno sensitive capability
  • withdraw_by_qrno sensitive capability
  • withdraw_createno sensitive capability
  • withdraw_dictno sensitive capability
  • withdraw_getno sensitive capability
  • withdraw_proofno sensitive capability
  • withdraw_read_qrno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

What this scan could not see

Versions 3

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.7.0 latest A 97/100 3 1.13.0 2026-09-07
v0.6.1 A 97/100 0 1.13.0 2026-09-01
v0.3.0 A 97/100 0 1.12.1 2026-08-19

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/payzu-mcp-pix/badge.svg)](https://mcptrustchecker.com/registry/payzu-mcp-pix)
HTML
<a href="https://mcptrustchecker.com/registry/payzu-mcp-pix"><img src="https://mcptrustchecker.com/registry/payzu-mcp-pix/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/payzu-mcp-pix/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan payzu-mcp-pix --online

Use the free API → How scoring works

More in Business & CRM