MCP.Market

Picpay MCP server

by codespar·io.github.codespar/mcp-picpay·v0.2.0-alpha.3·271 stars
No reviews yet

MCP server for PicPay Business — BR digital wallet (60M+ users): checkout, Pix QR, subscriptions

B82/100grade B
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
B82/100

full report

Adoption
Established

271 stars18 downloads/wk

Reviews

Write one

Nobody has reviewed Picpay yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Picpay tools (20, 12 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • cancel_paymentwrite action

    Cancel a PicPay order. If the order is unpaid, it is voided. If already paid, this triggers a refund (requires merchant account balance to cover).

  • cancel_subscriptionwrite action

    Cancel an active subscription. Future recurring charges are stopped; past charges are not refunded automatically.

  • create_b2p_transferwrite action

    Create a Business-to-Person (B2P) transfer: push funds from the merchant wallet to a PicPay user identified by CPF/CNPJ. Useful for payouts, cashbacks, rewards and marketplace splits. Amount in BRL decimal.

  • create_batch_paymentwrite action

    Submit a batch of B2P transfers in a single request. Each item is an independent transfer to a PicPay user; PicPay processes them asynchronously and notifies per-item via callback.

  • create_paymentwrite action

    Create a PicPay checkout payment. Returns paymentUrl (redirect the buyer to the PicPay app / web) and qrcode (content + base64 image). The buyer pays inside PicPay; your callbackUrl receives the status update. value is in BRL as a decimal number (e.g. 20.50).

  • create_payment_linkwrite action

    Create a shareable PicPay payment link. Returns a short URL the merchant can send via WhatsApp / email. The buyer opens the link and completes payment inside PicPay.

  • create_planwrite action

    Create a subscription plan (Recurrency API). Plans define the recurring amount, frequency, and trial.

  • create_subscriptionwrite action

    Enroll a buyer in a subscription plan. Returns the subscription record and the buyer-facing authorization URL.

  • delete_planwrite action

    Delete a subscription plan. Fails if the plan has active subscriptions.

  • generate_dynamic_qrcode

    Generate a dynamic PicPay Pay QR code with a fixed amount and optional expiration. Each QR is single-purpose. Returns qrcode content + base64 image and a paymentUrl.

  • generate_static_qrcode

    Generate a static PicPay Pay QR code for in-store / reusable use. The buyer opens PicPay, scans the QR and types in the amount. Returns the QR content and a base64 image.

  • get_b2p_transferwrite action

    Get the status of a B2P transfer by referenceId. Typical statuses: created, processing, completed, failed.

  • get_payment_status

    Get the status of a payment by referenceId. Typical statuses: created, expired, analysis, paid, completed, refunded, chargeback.

  • get_subscription

    Retrieve a subscription by id.

  • get_wallet_balance

    Retrieve the merchant's current PicPay wallet balance (available and blocked amounts in BRL). Useful before issuing refunds or B2P transfers.

  • list_plans

    List all subscription plans registered for this merchant.

  • list_transactions

    List merchant transactions (payments and transfers) within a date range. Supports pagination and optional status filter.

  • refund_paymentwrite action

    Refund a paid PicPay order, optionally partially. Unlike cancel_payment, this is the explicit refund endpoint and accepts a custom amount for partial refunds. The merchant wallet must have enough balance to cover the refund.

  • update_planwrite action

    Update an existing subscription plan.

  • validate_notification

    Verify that an incoming webhook callback came from PicPay by comparing the x-seller-token header against PICPAY_SELLER_TOKEN. Use this in your callback handler before trusting the payload, then call get_payment_status to fetch the authoritative status.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitystatic API keys via environment variables6/15
  • Maintenancelast push 29 days ago15/15
  • Maintainer identityregistry namespace matches repository owner7/10
Overall 82/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Picpay compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
82/100
higher than 63% of 48,255 servers
Tools
20
the typical server has 7
Tools that change things
60%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
271
more than 95% of 28,688 servers
Downloads a week
18
more than 5% of 12,191 servers with a package

What its tools let an agent do: 6 read · 8 create · 3 change · 3 delete

Install Picpay in Claude Code, Cursor or VS Code

Runs npx -y @codespar/mcp-picpay on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add mcp-picpay -- npx -y @codespar/mcp-picpay
Add to Cursor

What the publisher says

From the Picpay repository's README, as published. We do not edit it. Read it on GitHub

MCP Dev LATAM 🌎 Every commerce API your AI agent needs to run a business in Latin America. Brazil 🇧🇷 · Mexico 🇲🇽 · Argentina 🇦🇷 · Colombia 🇨🇴 · Chile 🇨🇱 · Peru 🇵🇪 · plus 4 agentic payment protocols. MCP servers for LATAM commerce · live in the official MCP Registry · MIT License Machine-readable catalog: codespar.dev/api/servers Catalog · Quick Start · Agentic Protocols · All Servers · Contribute

The Problem

AI agents can write code, analyze data, and chat. But they can't operate a business — collect payments, issue invoices, ship products, or notify customers. Especially not in Latin America, where every service has its own API, auth pattern, and quirks (mTLS for BACEN Pix v2, JWT-RSA for STP-SPEI, AFIP web services, contract-gated developer portals, and on).

Meanwhile, four agentic payment protocols are shipping in parallel — checkout protocols (Stripe ACP, Google UCP), authorization layers (AP2), and micropayment rails (x402) — and none of them compose cleanly with each other or with the regional rails businesses actually run on.

MCP Dev LATAM bridges both gaps. Traditional LATAM services + the new agentic payment protocols, all accessible through a single MCP interface.

The Solution

Each MCP server in this repo wraps a real provider — payments, fiscal, logistics, messaging, banking, ERP, identity, fraud, crypto, and the agentic protocols — so your agent can operate a complete business workflow.

🛒 Customer places order
  → 💳 Agent charges via Pix (Asaas / Mercado Pago / Zoop)
  → 📄 Agent issues NFe (Nuvem Fiscal / Focus NFe / NFe.io)
  → 📦 Agent generates shipping label (Melhor Envio / Skydropx)
  → 📱 Agent sends tracking via WhatsApp (Z-API / WhatsApp Cloud)
  → 📊 Agent records in ERP (Omie / Bling / Tiny)
  → 🏦 Agent reconciles balance (Stark Bank / Itaú / BTG)

Six systems. Zero human intervention. One agent.

Agentic Payment Protocols

Four servers for the emerging agentic payment stack:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Picpay: common questions

Is Picpay MCP server safe?
Mostly: it is graded B (82/100). Read the Picpay safety report
How do I install Picpay?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Picpay need an API key?
Yes. The registry entry asks for PICPAY_TOKEN, PICPAY_SELLER_TOKEN.
Is Picpay maintained?
The last commit was 67 days ago (2026-08-29). The latest release is v0.2.0-alpha.3.
How does Picpay compare with other MCP servers?
safety score 82/100 (higher than 63% of 48,255 servers); tools 20 (the typical server has 7); tools that change things 60% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

More from codespar →