Brionic Payments

com.brionicsecurity.payPublished by pay.brionicsecurity.comOfficial publisherv2.1.0Updated Nov 1, 2026

Non-custodial crypto payments: charges, invoices and refunds in BTC, XRP, USDC and more.

VerifiedStreamable HTTPWeb executableFinance

Overview

AI-generated overview

Remote MCP endpoint for Brionic's non-custodial crypto payments, letting an assistant create charges, invoices and refunds in BTC, XRP, USDC and other coins.

What you can do
  • Create and manage crypto payment charges
  • Issue invoices and track their status
  • Process refunds on crypto payments
  • Work across multiple coins including BTC, XRP and USDC
  • Authenticate either with a Brionic API key or through OAuth merchant approval
When to use it
Useful when a merchant wants an assistant to handle crypto payment operations — creating charges or invoices, checking payment state, or issuing refunds — without leaving the chat, and prefers a hosted endpoint over a local install.
Requirements
A remote streamable HTTP endpoint at pay.brionicsecurity.com; no local package. Authentication is required: either an Authorization header with a Bearer Brionic API key (test or live) or OAuth sign-in approved by the merchant. A Brionic merchant account is implied.
Before you install
This server moves real money: charges, invoices and refunds are financial actions, and a live API key can create real transactions. Keep the API key secret and prefer the test key while evaluating. Refunds and charges change merchant and customer balances, so review actions before approving them. The manifest lists no tools, so the exact operations and their safeguards are not documented here.

Installation

In SourceWeft

  1. Open Brionic Payments 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.brionicsecurity.pay%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": {
    "brionic-payments": {
      "type": "http",
      "url": "https://pay.brionicsecurity.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

1
  1. v2.1.0LatestNov 1, 2026

Score

83% 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
  • 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.