QuickPay

com.pagaconquickpayPublished by pagaconquickpay.comOfficial publisherv1.2.0Updated Oct 27, 2026

Payment links, stats, subscriptions, receivables and kitchen orders in Venezuela. Never moves money.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote QuickPay MCP server for Venezuela-focused payments: payment links, stats, subscriptions, receivables and kitchen orders, without moving money.

What you can do
  • Create and manage payment links.
  • Review payment statistics and receivables.
  • Handle subscriptions.
  • Track kitchen orders.
  • The server is described as never moving money, so it appears limited to viewing and organizing payment-related records rather than transferring funds.
When to use it
Useful when an assistant should help a Venezuela-based business work with QuickPay payment links, subscription records, receivables or kitchen orders, and summarize payment statistics. It is not intended for executing payments or transfers.
Requirements
A remote streamable HTTP endpoint at mcp.pagaconquickpay.com; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Access is granted through OAuth to a payment provider account, so the assistant can see financial and order data. The description states it never moves money, but confirm in the provider's documentation what each tool can change before relying on that.

Installation

In SourceWeft

  1. Open QuickPay in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. 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.pagaconquickpay%2Fquickpay/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. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "quickpay": {
      "type": "http",
      "url": "https://mcp.pagaconquickpay.com/mcp"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

3
  1. v1.2.0LatestOct 17, 2026
  2. v1.1.0Oct 17, 2026
  3. v1.0.0Oct 17, 2026

Score

67% 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 listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts
  • 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.