Let agents verify the seller and pay Billify invoices with x402 (USDC on Base).
Connect Remote server
claude mcp add --transport http billify-pay https://billify.org/mcp/pay
{
"mcpServers": {
"billify-pay": {
"url": "https://billify.org/mcp/pay"
}
}
}
{
"servers": {
"billify-pay": {
"type": "http",
"url": "https://billify.org/mcp/pay"
}
}
}
Settings > Connectors > Add custom connector
URL: https://billify.org/mcp/pay
Tools 4 found in our last check
get_invoiceLook up a Billify invoice from its public link: seller, amount, status, and whether and how it can be paid with x402 (USDC on Base).
verify_sellerBefore 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 c…
pay_invoicePay 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.
confirm_deliveryAfter paying: record whether the work was delivered, as accepted or disputed (a dispute needs a note). The decision is tied to the seller's latest delivery record (see delivered in get_invoice), by its record_hash. Add reference for your own note of what you received (a URL or a…
Details
| Endpoint | https://billify.org/mcp/pay (Streamable HTTP) |
| First published | 18 Oct 2026 |
| Last updated | 18 Oct 2026 |
| Registry name | io.github.Ovindolo/billify-pay |
More finance and crypto servers See all
Listing data from the official MCP registry. Status and tools from NestDaddy's daily check. Browse all MCP servers.
