Remote MCP · Endpoint

Invoice Preflight x402 MCP MCP server

No. Invoice Preflight x402 MCP answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.dropenginehq.com/api/paid-mcp

The last check completed an MCP handshake.

Registry name
io.github.Ahmet11159/invoice-preflight
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
147 ms
Tools exposed
24 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Invoice checks for AI agents: UBL/PDF/image, line items, evidence, free tier quote, x402 USDC.
Listing
From the official MCP registry (active).
Recent checks of Invoice Preflight x402 MCP
CheckedResultHandshake
1 hour agoHandshake completed147 ms
8 days agoHandshake completed123 ms
9 days agoHandshake completed163 ms
11 days agoHandshake completed141 ms
12 days agoHandshake completed123 ms
12 days agoHandshake completed150 ms
14 days agoHandshake completed124 ms
14 days agoHandshake completed130 ms
16 days agoHandshake completed160 ms
19 days agoHandshake completed118 ms
21 days agoHandshake completed145 ms
24 days agoHandshake completed121 ms
26 days agoHandshake completed125 ms
28 days agoHandshake completed109 ms

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

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 Invoice Preflight x402 MCP and makes no claim about it beyond what these checks measured.