Billify payments

io.github.OvindoloPublished by GitHub account Ovindolov0.2.0Updated Oct 26, 2026

Let agents verify the seller and pay Billify invoices with x402 (USDC on Base).

The publisher's own server: Payments Ai Mcp

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant look up Billify invoices, verify the seller against public registers, and pay invoices with x402 in USDC on Base.

What you can do
  • Look up a Billify invoice from its public link: seller, amount, status and x402 payability
  • Verify the seller against public registers (ANAF for Romanian CUIs, VIES for EU VAT numbers) and check the invoice IBAN
  • Pay an invoice with x402 v2: request the payment terms, sign the exact USDC amount on Base and resubmit with the payment metadata
When to use it
Use it when an assistant needs to check a Billify invoice before paying it, confirm that the seller is a registered and active company, or settle an invoice in USDC on Base through x402.
Requirements
A remote streamable HTTP endpoint at billify.org; no packages, environment variables or headers are declared. Paying requires an x402-capable wallet that can sign the USDC on Base payment, and the seller checks rely on public registers (ANAF, VIES) being reachable.
Before you install
pay_invoice moves real money: it settles USDC on Base and marks the invoice paid once the facilitator settles, so confirm the amount and seller first. The payment is signed by the client wallet, and invoice lookups use public links, so anyone with the link can read the invoice details. Seller verification is advisory and depends on third-party registers.

Installation

In SourceWeft

  1. Open Billify payments 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/io.github.Ovindolo%2Fbillify-pay/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": {
    "billify-payments": {
      "type": "http",
      "url": "https://billify.org/mcp/pay"
    }
  }
}

Tools

3

get_invoice

Get invoice

Look up a Billify invoice from its public link: seller, amount, status, and whether and how it can be paid with x402 (USDC on Base).

Parametersinvoicerequired

verify_seller

Verify seller

Before paying: check the seller of an invoice in the public registers (ANAF for Romanian CUIs, VIES for EU VAT numbers): registered name, whether it matches the invoice, VAT registration, whether the company is active and (ANAF) whether it is in the RO e-Factura register. Also checks the IBAN on the invoice page and shows the wallet an x402 payment goes to. Returns warnings to act on.

Parametersinvoicerequired

pay_invoice

Pay invoice (x402)

Pay a Billify invoice with x402 v2 over MCP. Call it once without payment to receive the PaymentRequired (exact USDC on Base); sign it and call again with _meta["x402/payment"]. The invoice is marked paid when the facilitator settles.

Parametersinvoicerequired

Version history

1
  1. v0.2.0LatestOct 18, 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 listedRequired15 pts
  • 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.

Other Payments integrations

Payments Ai Mcp

ai.payments.managedOfficial publisher

Remote MCP endpoint from Payments AI, a Merchant of Record, for launching products and branded checkouts for AI-built apps.

Streamable HTTPWeb executable
Business & CommerceNot indexed yetNov 8, 2026

Qut Pay (Kaspi QR payments)

kz.qutOfficial publisher

Qut Pay MCP server for Kaspi QR payments in Kazakhstan: create, check, cancel and refund invoices, and simulate sandbox payments.

Streamable HTTPWeb executableAuth
Finance9 toolsOct 26, 2026

walletcap for Coinbase payments MCP

Published by GitHub account coriolislabs

Spend-limit guard for Coinbase payments MCP wallets: a per-payment cap and a rolling 24-hour USDC budget shared across processes on one host.

STDIODesktop only
FinanceNot validated yetNov 7, 2026

FawryPay cash payments (unofficial)

Published by GitHub account mohamedaly-cloud

Unofficial local MCP server that lets an assistant work with FawryPay Pay-at-Fawry cash payments in Egypt, including optional refund and cancel tools.

STDIODesktop only
FinanceNot validated · the package did not installNov 1, 2026

Toss Payments

Published by GitHub account groove79

Local MCP server for Toss Payments that lets an assistant look up payments, list transactions and settlements, and cancel or refund with human approval.

STDIODesktop only
FinanceNot validated · the server did not startOct 24, 2026