Pay 2 Cash MCP server

• Addresshttps://mcp.pay2.cash/mcpnot in the official registry: answered when asked

No entry in the official MCP registry names this server. It answered on pay2.cash when the Atlas asked at the address servers are usually mounted on, so it is the vendor's own. Clients and catalogues that list servers from the registry do not show it.

• Stateanswerschecked 2026-10-28
• Tools11
• Server calls itselfpay2-cash
• Server version0.2.0
• Protocol version2025-06-18

On 2026-10-28 the server answered initialize and tools/list without a sign-in. First answer in 66 ms.

• Whether its tools do the product's job has not been judged yet.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score72 of 100answers 100 · definitions 67 · context 100 · connects 100 · lowered by the warning signs below
• Answered100% of days8 of 8 daily checks
• Median first answer204 ms
• Space in an agent's context≈ 1,367 tokensthe definitions of all its tools (11), which an agent carries on every turn
• Tool definitionsC · 67 of 100
• Typed results0 of 11 toolsdeclared outputSchema: results come typed, read once

• Parameters without a description: in 11 of 11
• Not saying whether it only reads or can destroy: 11 of 11

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• onboard_user

  Register a user by their UPI VPA. Returns the pay2-cash user id.

• create_mandate

  Credential A — create a UPI Reserve Pay mandate. User authorises ONCE; returns 'pending' until approved.

• issue_card

  Credential B — issue a scoped virtual card token (agentcard.sh/Stripe) the agent presents at card checkouts.

• agent_pay

  Spend against an ACTIVE mandate within the remaining limit. If merchantId is given, the payment is split (operator share + platform fee).

• mandate_status

  Get a mandate's status and remaining spendable amount.

• create_payment_intent

  Propose a specific purchase (amount + merchant + description). method: 'upi_mandate' | 'upi_intent' | 'card'. Returns an intent requiring confirmation (+ approvalUrl for UPI, or a single-use card for 'card').

• confirm_payment_intent

  Confirm and capture a payment intent. Splits to the merchant; for a 'card' intent the single-use card is DELETED after capture.

• onboard_merchant

  Onboard an operator as a PayU child merchant for Split Settlement (PayU handles KYC/nodal/settlement).

• merchant_status

  Get an onboarded merchant's status and platform fee.

• search_flights

  Search flights (Duffel). Returns priced offers (offerId, amount in minor units, currency, airline, segments). Show these to the user; book the chosen offerId with book_flight. Amounts are in the fare currency's minor units (e.g. EUR cents).

• book_flight

  Book a chosen flight offer. Issues a single-use virtual card scoped to the fare, places the Duffel order, then cancels the card. Re-prices the offer and refuses to book above maxPriceMinor. Returns the airline PNR (bookingReference).