Skip to content

Billify payments

by Ovindolo · remote · no sign-in to list tools · v0.2.0 · published by GitHub user Ovindolo

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

Final · 1Changes · 1
CompareRegistry entry

3 tools: 1 do something that can't be undone, 1 change things and 1 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

3 tools

Can't be undone 1Claude Code: ask
  • pay_invoicePay a Billify invoice with x402 v2 over MCP.No findings

    Why it is in this group

    • The name "pay_invoice" says "pay": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
Changes things 1Claude Code: ask
  • 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 regist…No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • openWorldHint: true
Only reads 1Claude Code: allow
  • 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).No findings

    Why it is in this group

    • The name "get_invoice" says "get": a word for reading.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • readOnlyHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.2.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__billify-pay__get_invoice"
    ],
    "ask": [
      "mcp__billify-pay__verify_seller",
      "mcp__billify-pay__pay_invoice"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as billify-pay. Review it before you use it.