Papaya Pay Any Bill (US)

com.papayapay.consumer-production.mcp-agentPublished by mcp-agent.consumer-production.papayapay.comOfficial publisherv1.0.1Updated Oct 24, 2026

Pay any US bill in a snap, right from your chat — utilities, medical, rent, parking tickets & more.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

A remote Papaya Pay server that lets an assistant help pay US bills, such as utilities, medical, rent and parking tickets, from chat.

What you can do
Pay US bills from chat, covering utilities, medical, rent, parking tickets and more, according to the provider's description. No tool list is published, so the exact actions available are not documented here. It runs as a hosted remote endpoint rather than a local package.
When to use it
Consider it when you want to settle a US bill through a chat assistant instead of a separate payment site, for example utilities, rent, medical charges or parking tickets.
Requirements
A remote MCP client that supports streamable HTTP, connected to the provider's hosted endpoint. The manifest declares no authentication, environment variables or headers, so any account or payment setup needed is not documented.
Before you install
This is a payment service: using it can move real money, so confirm amounts and recipients before approving anything. The manifest declares no authentication, which is unusual for a payment tool and worth verifying with the provider. No tool list is published, so what data is sent to Papaya Pay and what actions are performed cannot be confirmed from this listing.

Installation

In SourceWeft

  1. Open Papaya Pay Any Bill (US) in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.papayapay.consumer-production.mcp-agent%2Fbill-payment/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "papaya-pay-any-bill-us": {
      "type": "http",
      "url": "https://mcp-agent.consumer-production.papayapay.com/payagent/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.1LatestSep 16, 2026

Score

56% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.