Billify payments MCP server
io.github.Ovindolo/billify-payOvindolostreamable-httpv0.2.0Scanned
Let agents verify the seller and pay Billify invoices with x402 (USDC on Base).
4 tools: 1 do something that can't be undone, 2 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 1
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Billify payments MCP server can do
The Billify payments MCP server is published by the GitHub account Ovindolo. It has 4 tools. It can do things that cannot be undone, such as sending, paying or publishing (pay_invoice) and create or change data (2 tools: verify_seller and confirm_delivery), but cannot delete data. 1 tool only reads.
1 tool brings in text other people can write (verify_seller).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.
Last scanned Nov 16, 2026, version 0.2.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 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 2Claude Code: ask
confirm_deliveryAfter paying: record whether the work was delivered, as accepted or disputed (a dispute needs a note).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.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: true
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…Reads text others writeNo 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
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 1Show 1 read-only tool
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write1
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:59 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://billify.org/.well-known/oauth-protected-resource
- Authorization servers
- https://brrstlblwhnfyirwcgoh.supabase.co/auth/v1
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://billify.org/mcp/pay: tools/list returned 4 tools to an anonymous client, including pay_invoice (irreversible), verify_seller (write), confirm_delivery (write)
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 2 to 3
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 2 -> 3.View diff
- Tools that change things, listed without credentials: 2 to 3
Tools1 added.+1 addedView diff
- Added:confirm_deliveryChanges things
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/payclaude mcp add --transport http billify-pay https://billify.org/mcp/payRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__billify-pay__get_invoice"
],
"ask": [
"mcp__billify-pay__verify_seller",
"mcp__billify-pay__pay_invoice",
"mcp__billify-pay__confirm_delivery"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as billify-pay. Review it before you use it.
Capability tags behind 1 rule
- mcp__billify-pay__verify_seller untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.Ovindolo/billify-pay/verify?hash=5388648cb28a3d3ae5af2970fe591b39170471e113fd91b48a917740640b8fde" | jq -e '.changed == false'Pinned hash 5388648cb28a, from Nov 16, 2026, 20:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.Ovindolo/billify-pay/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.Ovindolo/billify-pay)Source: MCP Registry. Synced Oct 21, 2026, 18:18 UTC.
Billify payments MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Billify payments MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Billify payments MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Billify payments MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: pay_invoice.
What tools does the Billify payments MCP server have?
- 4 tools: 1 irreversible, 2 write, 1 read. pay_invoice, verify_seller, confirm_delivery and get_invoice.
Does the Billify payments MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Billify payments MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Billify payments MCP server changed its tools?
- Yes, once since Anlyon Radar started tracking it, most recently on Nov 3, 2026. Every change is on this page and in its Atom feed.