Remote MCP · Endpoint

SpendPreflight MCP server

No. SpendPreflight answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.spendpreflight.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.spendpreflight/spendpreflight
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
284 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Preflight x402 payments. Base ERC-8004 agent #1151628; wallet binding verified Nov 3, 2026.
Listing
From the official MCP registry (active).
Recent checks of SpendPreflight
CheckedResultHandshake
1 hour agoHandshake completed284 ms
4 days agoHandshake completed714 ms
14 days agoHandshake completed262 ms
15 days agoHandshake completed411 ms
15 days agoHandshake completed312 ms
17 days agoHandshake completed418 ms
18 days agoHandshake completed388 ms
19 days agoHandshake completed232 ms
20 days agoHandshake completed248 ms
21 days agoHandshake completed352 ms
23 days agoHandshake completed283 ms
25 days agoHandshake completed231 ms
28 days agoHandshake completed230 ms

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

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