Remote MCP · Endpoint

SparkPay MCP server

No. SparkPay answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://sparkpay.dev/api/mcp/mcp

The last check completed an MCP handshake.

Registry name
dev.sparkpay/sparkpay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
159 ms
Tools exposed
25 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Stripe billing for indie apps: plans, coupons, subscriptions, customers and revenue reporting.
Listing
From the official MCP registry (active).
Recent checks of SparkPay
CheckedResultHandshake
1 hour agoHandshake completed159 ms
2 days agoHandshake completed235 ms
4 days agoHandshake completed203 ms
5 days agoHandshake completed165 ms
7 days agoHandshake completed223 ms
8 days agoHandshake completed205 ms
9 days agoHandshake completed156 ms
12 days agoHandshake completed184 ms
13 days agoHandshake completed156 ms
15 days agoHandshake completed139 ms
16 days agoHandshake completed173 ms
18 days agoHandshake completed170 ms
19 days agoCredentials required—
20 days agoCredentials required—
20 days agoCredentials required—
21 days agoCredentials required—
22 days agoCredentials required—

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

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