Billify payments MCP Server

by ovindolo Your server? Claim it

not responding

Billify payments is listed as active in the registry but did not answer our last check. It exposes 3 tools.

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

Uptime history 7 days of history · worst day 0%

7 days agonow

1.1%

Uptime 24h

1 of 91 checks

Tools

read from the server

324 ms

Response time

average over 24h

open, no key

Access

streamable-http

What changed 1

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 19 October 2026. No other catalogue keeps this.

19 Oct a tool description was rewritten verify_seller

Billify payments does not always answer

Over the last week it answered 5.6% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 9 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add billify-pay --transport http https://billify.org/mcp/pay

Settings → Connectors → Add custom connector, then paste this address

https://billify.org/mcp/pay

~/.codex/config.toml

[mcp_servers.billify-pay]
url = "https://billify.org/mcp/pay"

.cursor/mcp.json

{
  "mcpServers": {
    "billify-pay": {
      "url": "https://billify.org/mcp/pay"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "billify-pay": {
      "type": "http",
      "url": "https://billify.org/mcp/pay"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

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).

pay

pay_invoice

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.

verify

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.

Endpoints

URL	Transport	State	Latency	Checked
https://billify.org/mcp/pay	streamable-http	answering	346 ms	9 min ago

Alternatives to Billify payments

same job, measured the same way

M2mcent

by evozim

x402 payment wrapper for AI Agents and MCP Servers. USDC settlements on Base L2.

11 installs/wk local only

AgnicPay

by agnicpay-prog

X402 payment MCP for AI agents. Auto-pay 300+ APIs with USDC on Base and Solana.

answering

XDC AI

by 0xbeny

Wallet and payments for AI agents: auto-pay x402 APIs in USDC on XDC, within on-chain limits.

answering

Voidly Agent Wallet

by voidly-ai

Local Base USDC wallet for agents with capped x402 payments and Marketplace recovery.

70 installs/wk local only

Cleared

by clearedpay

USDC invoicing on Base: send invoices, share pay links, track payments and customers.

answering

Amanchain MCP

by gitajhd

59 pay-per-call AI services as MCP tools with automatic x402 USDC-on-Base payment.

39 installs/wk local only

x402 Atlas

by ausrine-labs

The x402 agent market on Base: sellers, prices, on-chain payments, operators, buyers. Dated.

local only

Phantom MCP Server

by arbromagency-sato

PHANTOM ID MCP payment server: agent-to-agent USDC payments on Base.

99 installs/wk local only

Billify payments — questions

Answers built from our own checks of this server.

What can Billify payments do?

It exposes 3 tools, read directly from the server on our last check. Among them: get_invoice, pay_invoice, verify_seller. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Billify payments working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 1 of 91 checks got a reply (1.1%), average response time 324 ms. The bar chart above shows every period we have measured.

The registry lists Billify payments as active — why does it not respond?

The official MCP registry stores what the author submitted; it does not verify that the server still runs. We check the endpoint ourselves, and this one does not answer. Catalogues that copy the registry without checking will show it as working.

How do I connect Billify payments?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Billify payments need an API key?

No. Billify payments completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Billify payments?

It answers our handshake in 324 ms on average, which is faster than 50% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.