Payments

click.myinfrastructurePublished by myinfrastructure.clickOfficial publisherv1.0.3Updated Nov 4, 2026

Planos, assinaturas, links de pagamento e métricas

The publisher's own server: Auth

VerifiedStreamable HTTPWeb executableBusiness & Commerce

Server details

Identifier: click.myinfrastructure/payments
Transport: Streamable HTTP
Runtime: Web executable
Trust: Verified
Published: Oct 21, 2026

Security note

MCP servers receive tool arguments from a conversation and may perform external actions. Review what a server can do before you enable it, and give it only the access it needs.

The registry verified that this server's namespace belongs to myinfrastructure.click, which also runs its endpoint. That identifies the publisher; it does not make the server's tools safe.

SourceWeft's checks cover whether the listing is complete and the endpoint answered; they do not review the server's code or what its tools do.

Add a badge to your README

Show readers this MCP server is listed on SourceWeft. The badge links to this page.

[![Listed on SourceWeft](https://sourceweft.com/badge/mcp/click.myinfrastructure%2Fpayments.svg)](https://sourceweft.com/mcp/click.myinfrastructure%2Fpayments?utm_source=readme&utm_medium=badge)

Overview

AI-generated overview

Remote MCP server for payments: plans, subscriptions, payment links and metrics, reachable over streamable HTTP with OAuth sign-in.

What you can do: Manage plans and subscriptions
Create and share payment links
Review payment metrics
No individual tools are documented, so the exact operations are not described in the supplied material.
When to use it: When an assistant should work with payment plans, subscriptions, payment links or payment metrics for a business, and you are comfortable connecting it to a hosted payments service over OAuth.
Requirements: A remote endpoint at payments.worker.myinfrastructure.click over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.

Before you install

It handles payment and subscription data behind an OAuth account, so the assistant may be able to create payment links or change plans and subscriptions. Grant only the scopes you need and review what the OAuth consent requests before connecting.

Installation

In SourceWeft

Open Payments in the dashboard and add it to a workspace.
Connect the required credentials. They are stored privately and never shown on public pages.
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/click.myinfrastructure%2Fpayments/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": {
    "payments": {
      "type": "http",
      "url": "https://payments.worker.myinfrastructure.click/mcp"
    }
  }
}

Tools

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

v1.0.3LatestNov 4, 2026
v1.0.1Oct 21, 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.