PicPay
by PicPay
Check your PicPay balance, cofrinhos, credit-card invoice, boletos, Pix limits and statement from your AI assistant. 13 tools, all reads, OAuth sign-in with facial biometrics.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Connect PicPay via MCP
https://mcp.svc.picpay.com/v2/mcpWorks in any MCP-compatible client. In Agentman Studio it is one click — no config file to edit.
Use in Agentman
Connect PicPay once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.
Open in Agentman StudioPicPay Tools & Capabilities (13)
Tool names from Anthropic's directory listing. This server requires sign-in, so we could not read tool descriptions or parameter schemas.
Limits
- Two advertised OAuth scopes exceed the published tool surface.
piggy_bank.writeandpix.writeappear in the server's own descriptor while nothing in the 13 tools writes. PicPay publishes no explanation. Read the consent screen. - The vendor's material is Portuguese only. The tool reference, the connector page and the launch release are all Brazilian Portuguese. Every quotation on this page is our translation. For a non-Portuguese-reading team this is a real evaluation constraint.
- Statement history is capped at 90 days, defaulting to 7 days and 15 records. Anything older is not reachable through this connector.
- We could not read live tool schemas. The endpoint rejected an anonymous handshake and a syntactically valid junk bearer with different error bodies, so authentication is genuinely enforced. Parameter types and return fields on this page are PicPay's documentation, not observed responses, and documentation can drift from a running server.
- No rate limits are published. PicPay's reference documents no request ceiling, quota or throttling behaviour for the connector. We do not know whether one exists.
- No troubleshooting guidance is published. PicPay's documentation has no error-handling, failure-mode or reconnection section, so there is nothing to cite about what a failed call means.
- Cofrinhos are capped at 10.
piggy_listreturns a flag for whether the 10-cofrinho limit has been reached, which is the connector telling you about a product limit rather than its own. - Availability was staged, not open. PicPay described a gradual rollout via an early-access list. Whether general availability has since been reached is not published.
- Permission inheritance is undocumented. PicPay publishes no statement about whether the connector is bounded by the signed-in user's own permissions. Its absence is not evidence either way.
- The connector supports one account. Nothing in the tool list accepts an account or profile selector, so it appears to address the single account you sign in as. PicPay does not state this.
Frequently asked questions
No tool in the published inventory moves money. All 13 tool names end in get or list, and PicPay's per-tool reference documents only query parameters and return fields, with no amount or destination input anywhere. PicPay's own launch release states the integration is dedicated to queries and financial tracking, without transactions through the platform.
PicPay's OAuth descriptor lists seven scopes including two write scopes, which we read directly from the server on 2026-09-09. No published tool exercises them. PicPay has not explained the gap, so treat the scopes as capability the authorization layer is built for rather than behaviour the current connector performs, and re-read the consent screen before approving.
No. PicPay states the connection sends you to internet banking login and that having the app installed is not required. The connector uses the same security layers as the PicPay app, including facial biometric authentication. Access rolled out gradually through an early-access list at no cost, on both Android and iOS.
PicPay is a Brazilian bank and the connector reaches a Brazilian account, so you need a PicPay account to use it. Every value it returns is in Brazilian reais and the features it exposes are Brazilian instruments: Pix, boletos, cofrinhos. PicPay does not publish any non-Brazilian availability for this connector.
Ninety days is the documented maximum. PicPay's reference for statements_list gives a default window of the last seven days, a ceiling of 90 days, and a default of 15 records per response. It also accepts a type filter that switches between recent entries and scheduled future ones.
Portuguese only. PicPay's tool reference, its connector landing page and its launch release are all in Brazilian Portuguese, and we found no English version of any of them. Field names in the returned data are mixed, with some in English and some in Portuguese such as saldo_total and total_investido, which matters when you write prompts against them.
There is no evidence it does, and the documented surface is narrower than the app. The 13 tools cover balance, cofrinhos, cards, invoices, investments, boletos, Pix keys, contacts and limits, and nothing else. PicPay has not published a written statement about permission inheritance, so we cannot confirm the boundary beyond what the tool list shows.
Anthropic lists PicPay as working with Claude, the Claude API, Claude Code and Claude Desktop. PicPay separately shipped a ChatGPT plugin roughly two weeks before the Claude connector and says existing plugin users were enabled for Claude. The endpoint speaks standard streamable HTTP MCP, so other compliant clients should connect.
Sources
- PicPay MCP tool reference (per-tool parameters and return fields, all 13 tools) (retrieved 2026-09-09, HTTP 200) · retrieved 2026-09-09
- PicPay MCP connector landing page — the
documentationURL in Anthropic's directory, which links to the reference above (retrieved 2026-09-09, HTTP 200) · retrieved 2026-09-09 - PicPay press release, *"PicPay lança integração inédita com o Claude e avança em sua estratégia de IA"*, dated 2026-09-03 — capability list, example questions, security and rollout detail, and the CEO quotation (retrieved 2026-09-09) · retrieved 2026-09-03
- Live OAuth posture check against
https://mcp.svc.picpay.com/v2/mcp— anonymousinitializereturned HTTP 401 with an RFC 9728WWW-Authenticatechallenge naming its resource metadata document (2026-09-09) · retrieved 2026-09-09 - PicPay protected-resource metadata (RFC 9728), source of the seven advertised scopes —
https://mcp.svc.picpay.com/.well-known/oauth-protected-resource/v2/mcp(HTTP 200, 2026-09-09) · retrieved 2026-09-09 - PicPay authorization-server metadata (RFC 8414) — authorization, token and dynamic client registration endpoints,
coderesponse type and S256 PKCE —https://mcp.svc.picpay.com/.well-known/oauth-authorization-server/v2/mcp(HTTP 200, 2026-09-09) · retrieved 2026-09-09 - PicPay press release on cofrinhos, source of the 102% of CDI figure and the daily-liquidity CDB (retrieved 2026-09-09) · retrieved 2026-09-09
- PicPay regulatory disclosures index (retrieved 2026-09-09) · retrieved 2026-09-09
- Anthropic Connectors Directory entry, source of the 13 tool names, categories, endpoint and partner tier (snapshot 2026-09-08, re-checked 2026-09-09) · retrieved 2026-09-08
- PicPay privacy notice (last updated August 2026, retrieved 2026-09-09) · retrieved 2026-09-09
Server Info
- Category
- Finance
- Developer
- PicPay
- Tools
- 13
- Domain
- mcp.svc.picpay.com
Using Claude Desktop or another MCP client? Setup docs — the connection URL above works anywhere.
Similar MCP Servers for Finance
Related Resources
Ready to connect PicPay?
Connect PicPay once and your agents call these tools on their own — on a schedule, in a workflow, with nobody at the keyboard.