Skip to content
External endpointresponds

Papaya Pay Any Bill

Pay any bill in a snap, right from your chat. Utilities, medical, rent, parking tickets and more.

Endpoint URL
https://mcp-agent.consumer-production.papayapay.com/payagent/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
311 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.papayapay.consumer-production.mcp-agent/bill-payment

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
Papaya Pay Any Bill
Version
1.29.0
Capability keys
experimental, prompts, resources, tools
Tool names
analyze_bill, check_payment_method, confirm_payment_intent, get_new_auth_token, fetch_bill_status, request_bill_cancellation
Instructions excerpt

This connector lets the user pay a bill via Papaya. Flow: analyze_bill (read the bill and create it - its result includes a payment_link) -> the user opens that link and enters their card on a secure form (this only SETS the payment method, it does not pay) -> confirm_payment_intent (collect the email for status updates plus any extra info the bill needs, then submit the payment). Hand the payment_link to the user as-is the moment you get it; the secure form is the only way to provide a card. After they tell you they have finished the form, call confirm_payment_intent. If the user is returning, reuse their user_id and auth_token from earlier in the conversation rather than creating a new user. Before submitting, ask the user for the email where payment updates should go - never make one up; a wrong email means they get no updates. Style: keep replies to one or two short sentences. Do not recap the bill or restate what you just did unless asked. Ask for one missing item at a time, nev

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 255ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 581ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 371ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 311ms