br.com.pushinpay/mcp — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Track identity, package activity, privileges, documentation and data handling

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

PushinPay PIX charges and balance lookup

What we know

Official PushinPay MCP exposing balance, transactions and creation of PIX payment requests. MCP oficial da PushinPay: cobranças PIX, consulta de transações e saldo via IA.

Maintenance / activity evidence

171 downloads from 2026-09-09 through 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: medium_identity_and_metrics; published-function claims not execution verified.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1. Reported action classes: Generate PIX payment QR codes. Complete write authority is not verified.
See package authentication documentation; not independently tested.
Sensitive access: Account or infrastructure data accessible with supplied credentials

Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1.
Public listing does not imply a safe runtime or security audit.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 171 package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package @pushinpaybr/mcp-server; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T17:26:34Z.

All limitations / Review context

Have @pushinpaybr/mcp-server permissions, hosted data retention, publication identity or supported MCP operations changed?

Bounded public tracking review; known consequences disclosed: Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1.

Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1.
Public listing does not imply a safe runtime or security audit.
See package authentication documentation; not independently tested.
Reviewed write actions: Generate PIX payment QR codes
Sensitive access: Account or infrastructure data accessible with supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Operator must review permissions and remote data processing before installation.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Original activity observations

171 downloads from 2026-09-09 through 2026-10-08

Technical identity

npm/@pushinpaybr/mcp-server

Exact implementation source: https://www.npmjs.com/package/@pushinpaybr/mcp-server ↗
Reviewed resource type: MCP Server
Package identity: npm:@pushinpaybr/mcp-server

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@pushinpaybr/mcp-server
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
PUSHINPAY_TOKEN required; PUSHINPAY_ENV=sandbox preferred before production payments.
publisher install or stdio launch · Publisher instructions
npx -y @pushinpaybr/mcp-server
Configure / authenticate
MCP100 setup guide
Set PUSHINPAY_TOKEN and optional PUSHINPAY_ENV=sandbox|production in MCP client env. Keep default sandbox for non-production verification.
Previously reviewed client configuration / prerequisites: Switch to production only intentionally, after provider permissions and test-mode separation are understood.
claude desktop or cursor mcpServers json · MCP100 composed guide
{ "mcpServers": { "pushinpay": { "args": [ "-y", "@pushinpaybr/mcp-server" ], "command": "npx", "env": { "PUSHINPAY_ENV": "sandbox", "PUSHINPAY_TOKEN": "REPLACE" } } } }
Check connection
Suggested check
With PUSHINPAY_TOKEN and PUSHINPAY_ENV=sandbox, call consultar_saldo only (read-only). Do NOT use criar_cobranca_pix for testing.
Remove / uninstall / revoke
MCP100 setup guide
If you added this integration to Claude Code under the registration name `pushinpay`, run `claude mcp remove pushinpay` to unregister that client entry. In Claude Desktop, Cursor, VS Code or another host, delete/disable the corresponding named MCP registration in that host's settings and restart/reconnect. If you installed an npm package globally or operate a separate HTTP server, uninstall/stop it with its original deployment method. This does not delete user data or revoke service credentials.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: PushinPay panel issues PUSHINPAY_TOKEN (may be IP-bound); sandbox or production selected by PUSHINPAY_ENV. Official package README does not document exact key deletion/revocation UI. Do not create PIX charges to verify connection.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove pushinpay

Official Documentation & Sources

What it does

Official PushinPay MCP exposing balance, transactions and creation of PIX payment requests. MCP oficial da PushinPay: cobranças PIX, consulta de transações e saldo via IA.

Capability: Finance & Payments
Resource type: MCP Server
Industry: Financial Services & Investing
Best fit: PushinPay PIX charges and balance lookup

Representative uses

Check PIX transactions
Generate PIX payment QR codes

Limitations

Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1.
Exact install command and full env contract unverified except where explicitly documented; check official package before running.
Exact npm download observation only; no independent installation test.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: See package authentication documentation; not independently tested.
Permissions: Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1.
Data handling: Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1.
Cost: Not verified; check vendor terms
Risk and cautions: Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1.

Access scope and cautions

Write actions: Not verified Generate PIX payment QR codes
Sensitive access: Account or infrastructure data accessible with supplied credentials
Risk level: high
Security notes: Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1. Public listing does not imply a safe runtime or security audit.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T17:26:34Z. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Check PIX transactions; Generate PIX payment QR codes.

What setup and authentication are documented?

A complete connection procedure is not verified. Recorded transport: stdio. Client notes: Never infer missing startup flags or credentials. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: API credential or authenticated app account required; exact setup should be checked in upstream package

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Generate PIX payment QR codes. Recorded permission context: Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1.

What data-handling boundary should I consider?

Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1. Recorded sensitive-access context: Account or infrastructure data accessible with supplied credentials.

What limitations and risks should I check before use?

Production token grants access to payments data and can create collection requests; withdrawals and refunds not exposed in documented v1. Exact install command and full env contract unverified except where explicitly documented; check official package before running. Exact npm download observation only; no independent installation test. Public listing does not imply a safe runtime or security audit. Operator must review permissions and remote data processing before installation.