MCP.so
Sign In
B

Brionic Payments MCP Server

@Brionic Payments

Basic information

Transport

streamable-http

Authentication

OAuth

Last updated

Author

Brionic Payments

About Brionic Payments MCP Server

Brionic Payments exposes merchant payment operations through MCP. The official server card describes charges, invoices and reusable payment links across supported cryptocurrency networks. Settlement goes to the merchant wallet under the provider model. Refund recording and payment administration should not be confused with unrestricted authority to withdraw funds.

Connection details

https://pay.brionicsecurity.com/mcp

Setup

claude mcp add brionic-payments --transport http https://pay.brionicsecurity.com/mcp

Brionic Payments MCP Server tools

Tool list not available yet

This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.

This server requires authentication. Tool discovery may require signing in or credentials from the provider.

Fetch the live tool list directly from this server's endpoint using the button above.

Overview

Overview

Brionic Payments exposes merchant payment operations through MCP. The official server card describes charges, invoices and reusable payment links across supported cryptocurrency networks.

Settlement goes to the merchant wallet under the provider model. Refund recording and payment administration should not be confused with unrestricted authority to withdraw funds.

Capabilities

  • Create charges and invoices
  • Manage payment links
  • Look up payment events

Connect

  1. Add the remote URL to an MCP-compatible client.
  2. Authenticate with the provider when prompted.
  3. Review the available tools and start with a read request where available.
{
  "mcpServers": {
    "brionic-payments": {
      "type": "http",
      "url": "https://pay.brionicsecurity.com/mcp"
    }
  }
}

Authentication and limits

A merchant account and OAuth grant or supported API credential are required. Test and live mode, permissions and costs must be reviewed before any payment action.

Sources

Official documentation. Verified 2026-11-18: initialize HTTP 401. No account authorization or business tool actions were performed.

Frequently asked questions

1

What is the Brionic Payments remote MCP server?

The Brionic Payments remote MCP server is a hosted Model Context Protocol endpoint at https://pay.brionicsecurity.com/mcp, so AI assistants can connect to it without installing or running anything locally.

2

How do I connect to the Brionic Payments MCP server?

Add the endpoint https://pay.brionicsecurity.com/mcp to any MCP-compatible client such as Claude Code, Cursor, or VS Code. The setup snippets on this page configure each client in one step.

3

Does the Brionic Payments MCP server require authentication?

Yes. Brionic Payments uses OAuth: the first time you connect, your MCP client opens a browser window to sign in and authorize access, then reuses the credentials for future sessions.

4

Which transport does the Brionic Payments MCP server use?

Brionic Payments exposes a streamable-http endpoint, the transport used by remote MCP servers and supported by all major MCP clients.

Comments