MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Payments & trading

Billify payments

By Ovindolo

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

WebsiteSource codeFinance & paymentsAI models & agents
Connect to Billify payments
Checks passed
11 / 22

3 failed · 8 not measured

Median response
697 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
4

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
004
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
310
Publisher identityCan the publisher be traced to its source?
222

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 697 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-06-18, serverInfo.name billify-pay.

  • Pass
    Lists tools

    tools/list returned 4 tools.

  • Pass
    Current protocol

    Negotiated 2025-06-18. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 697 ms over 1 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 697 ms over 1 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    1 of 1 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Not measured
    Stable tool list

    Fewer than two successful probes in 30 days, so tool-list stability is not measured.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Fail
    Parameters documented

    6 of 9 parameters have a description (67%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Not measured
    Website matches publisher

    This namespace is not a reverse domain, so the website comparison does not apply.

  • Fail
    Source repo linked

    No repository URL is on file.

  • Fail
    Repo owner matches

    The GitHub repository owner does not match the namespace login.

  • Pass
    Recently updated

    Updated 2026-10-18T14:52:18.578387Z, within 180 days.

  • Not measured
    Open-source licence

    No GitHub repository to ask about a licence.

Start using Billify payments

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

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

Capabilities

Tools 4

confirm_delivery

After 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 content hash). With signature, an EIP-191 signature by the wallet that paid over the text this tool returns as sign_message when called without decision, the decision is recorded as proven by the payer; without it, only as made by someone holding the invoice link. An acceptance is final. It appears in the signed Invoice Passport history.

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

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

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

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected697 ms4

Related servers

All alternatives

Same function and industry, ranked by checks passed then median latency.

Explore alternatives to Billify payments