Remote MCP · Endpoint

Billify payments MCP server

No. Billify payments answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://billify.org/mcp/pay

The last check completed an MCP handshake.

Registry name
io.github.Ovindolo/billify-pay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
422 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Let agents verify the seller and pay Billify invoices with x402 (USDC on Base).
Listing
From the official MCP registry (active).
Recent checks of Billify payments
CheckedResultHandshake
18 minutes agoHandshake completed422 ms
10 days agoHandshake completed521 ms
10 days agoHandshake completed501 ms
11 days agoHandshake completed520 ms
13 days agoHandshake completed372 ms
14 days agoHandshake completed432 ms
14 days agoHandshake completed406 ms
15 days agoHandshake completed419 ms
17 days agoHandshake completed440 ms
19 days agoHandshake completed270 ms
21 days agoHandshake completed354 ms
24 days agoHandshake completed403 ms
26 days agoHandshake completed593 ms
28 days agoHandshake completed300 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Billify payments and makes no claim about it beyond what these checks measured.