MCP server connector for Cash App payments using Playwright browser automation
This server has critical definition gaps across all 13 tools. While tool names follow verb_noun convention (cashapp_get_balance, cashapp_send_money), descriptions are present but lack LLM-optimization guidance. Most critically: (1) Input schemas are visible and properly typed, but parameter descriptions are minimal (1-2 sentences, often under 50 chars). (2) No output schemas are documented, LLMs cannot infer what fields to expect from responses. (3) No error handling guidance, tools return JSON but lack recovery instructions. (4) Security-critical: cashapp_login exposes credentials as parameters (email_or_phone, password) rather than using server-side injection. (5) cashapp_send_money and cashapp_accept_request are IRREVERSIBLE but lack confirmation/dry-run patterns. (6) No pagination support on list tools (cashapp_get_transactions, cashapp_get_pending_requests). (7) Parameter 'note' is marked required in cashapp_send_money and cashapp_request_money but described as 'optional', contradiction. Baseline: A+ tools average 194 chars description + 72 chars per param; this server averages ~80 chars description + 40 chars per param.
Accept a pending payment request. This will send the requested amount to the requester.
Decline a pending payment request.
Get the current Cash App balance for the logged-in account. Returns the balance amount in USD.
Get the current Bitcoin (BTC) balance and its USD value for the logged-in Cash App account.
Get the available Cash Card Boosts (discounts and offers) for the logged-in account.
Get information about the linked Cash Card including last four digits, status, and type.
Credentials exposed as tool parameters. cashapp_login requires email_or_phone and password as input parameters. These will be logged in agent traces and prompt history. Must use server-side secret injection via environment variables or secure vault.
No output schemas documented. LLMs cannot infer response structure (field names, types, nesting). All 13 tools return JSON but lack formal schema declarations. Agents cannot plan downstream tool calls or extract required fields reliably.
| Scored | Grade | Overall | Spec posture | Rubric |
|---|---|---|---|---|
| 2026-09-23 | D | 52 | 2026-07-28+ | v2 |
Get the list of contacts/friends associated with the logged-in Cash App account.
Get a list of all pending payment requests for the logged-in account. Returns incoming requests that haven't been accepted or declined.
Get detailed information about a specific transaction by its ID.
Get the transaction history for the logged-in Cash App account. Returns a list of recent transactions.
Log in to Cash App using email/phone and password. Must be called before any other Cash App operations. Returns success/failure and a message.
Request money from another Cash App user. Sends a payment request to the specified recipient.
Send money to another Cash App user. Requires the recipient's $Cashtag, amount in USD, and an optional note.
Irreversible operations lack confirmation/dry-run pattern. cashapp_send_money (IRREVERSIBLE) and cashapp_accept_request (IRREVERSIBLE) can transfer funds but have no confirmation step. Agents make mistakes, these tools need a dry-run or explicit confirmation gate.
Parameter schema contradictions. cashapp_send_money and cashapp_request_money mark 'note' as required (in required array) but describe it as 'Optional note/memo'. LLMs will treat it as mandatory, causing failures when agents omit it.
No pagination or result limits on list tools. cashapp_get_transactions and cashapp_get_pending_requests accept a limit parameter but lack offset/cursor and total_count in responses. Large result sets will blow context windows. No guidance on max results.