com.papayapay.consumer-production.mcp-agent/bill-payment · v1.0.1 · finance-and-payments
Papaya Pay Any Bill (US) is healthy: it completed an MCP handshake in 805 ms and exposes 6 tools.
Pay any US bill in a snap, right from your chat — utilities, medical, rent, parking tickets & more.
Endpoint: https://mcp-agent.consumer-production.papayapay.com/payagent/mcp (streamable-http)
No repository listed · Website · JSON · Add to my inventory
| Users (last 30 days) | 0 |
| Handshake | Healthy |
| Auth needed | None |
| Tool count | 6 |
| Latency | 805 ms |
| Last checked (UTC) | 2026-10-17T06:00:37.935Z |
| Checked (UTC) | Status | Latency | Error |
|---|---|---|---|
| 2026-10-17T06:00:37.935Z | Healthy | 805 | |
| 2026-10-17T06:00:37.881Z | Healthy | 731 | |
| 2026-10-15T23:05:13.854Z | Healthy | 1069 | |
| 2026-10-14T21:05:37.366Z | Needs auth | 1904 | initialize: HTTP 403 |
analyze_bill | Read a bill from the user's description and create it for payment. This is the first step. Capture every address and identifier on the bill (remit-to address, account/invoice number, any code or pin) - missing details can delay or fail the payment. The remit-to address (where payment is |
check_payment_method | Optional: check whether the user has finished the secure form and a card is on the bill yet. Returns the card's last 4 digits and name when one is set, or a PENDING status when the form has not been completed. Use only if you need to confirm the card landed (e.g. the user asks) - it is n |
confirm_payment_intent | Final step: submit the bill for payment, after a card has been set. You must have confirmed the amount with the user first (amount_to_pay may be partial) and quote their confirmation in user_amount_statement - do not call this until you have asked. If analyze_bill reported a need for ext |
get_new_auth_token | Get a fresh auth token when another tool fails with an authorization error. Pass the user's current refresh_token; returns a new auth_token/refresh_token pair to use on the retried call and on later calls. Call this only in response to an auth failure, not preemptively. Args: |
fetch_bill_status | Check the payment status of a submitted bill. Read `value` for the current status. statusEvaluatedDescription is only present when the payment was declined or failed, and then explains why - relay that reason to the user. It is omitted for every other status, so treat its presence as a d |
request_bill_cancellation | Cancel a submitted bill so it will not be paid. Use when the user wants to stop a bill they submitted; cancellation may be rejected if the payment has already progressed too far - relay any error to the user. Not for correcting bill details: re-run analyze_bill for that. Args: |