API Tools

billify.org

Looks up, verifies, and pays Billify invoices via x402, including seller identity and VAT/company checks.

2 endpoints3 known toolsFirst detected October 19, 2026Last detected October 19, 2026

ENDPOINT 1

https://billify.org/mcp

Auth required

Known tools 0

No tool metadata was available in the registry cache.

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.billify-org]
url = "https://billify.org/mcp"
enabled = true
bearer_token_env_var = "MCP_BEARER_TOKEN"

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Code

.mcp.json

{
  "mcpServers": {
    "billify-org": {
      "type": "http",
      "url": "https://billify.org/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Claude Desktop

Settings → Connectors → Add custom connector

Name: billify-org
Remote MCP URL: https://billify.org/mcp

Add the URL as a custom connector, then complete its supported authorization flow. Claude Desktop remote connectors are configured in the UI.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "billify-org": {
      "url": "https://billify.org/mcp",
      "headers": {
        "Authorization": "Bearer YOUR_BEARER_TOKEN"
      }
    }
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Visual Studio Code

.vscode/mcp.json

{
  "servers": {
    "billify-org": {
      "type": "http",
      "url": "https://billify.org/mcp",
      "headers": {
        "Authorization": "Bearer ${input:mcp-token}"
      }
    }
  },
  "inputs": [
    {
      "type": "promptString",
      "id": "mcp-token",
      "description": "billify-org bearer token",
      "password": true
    }
  ]
}

Authentication is required. Replace the placeholder locally and never commit a secret.

Generic MCP

Client-specific MCP configuration

{
  "name": "billify-org",
  "transport": "streamable-http",
  "url": "https://billify.org/mcp",
  "headers": {
    "Authorization": "Bearer YOUR_BEARER_TOKEN"
  }
}

Authentication is required. Replace the placeholder locally and never commit a secret.

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://billify.org/mcp/pay

No auth detected

MCP server metadata

Name: billify-pay
Version: 0.1.0

Capabilities

tools

Server instructions

Pay Billify invoices. get_invoice shows what an invoice link is for; verify_seller checks the seller in public registers before you pay; pay_invoice uses x402 v2 (exact USDC on Base, eip155:8453): call without payment, sign the requirement, call again with _meta["x402/payment"]. Amounts include a few millionths that identify the invoice; pay exactly what is asked.

Known tools 3

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

Potential side effects

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.

Potential side effects

pay_invoice

Pay a Billify invoice with x402 v2 over MCP.

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

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

Claude Code

.mcp.json

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

Claude Desktop

Settings → Connectors → Add custom connector

Name: billify-pay
Remote MCP URL: https://billify.org/mcp/pay

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

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

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "billify-pay",
  "transport": "streamable-http",
  "url": "https://billify.org/mcp/pay"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.