Remote MCP · Endpoint

Voidpay (hosted) MCP server

No. Voidpay (hosted) answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.voidly.ai/mcp/voidpay

The last check completed an MCP handshake.

Registry name
io.github.voidly-ai/voidpay
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
654 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Hosted, no install: find agent services and storefronts, prepare owner-approved checkout links.
Listing
From the official MCP registry (active).
Recent checks of Voidpay (hosted)
CheckedResultHandshake
1 hour agoHandshake completed654 ms
2 days agoHandshake completed1.62 s
5 days agoHandshake completed427 ms
7 days agoHandshake completed545 ms
9 days agoHandshake completed843 ms
11 days agoHandshake completed645 ms
13 days agoHandshake completed610 ms
15 days agoHandshake completed669 ms
17 days agoHandshake completed1.12 s
19 days agoHandshake completed455 ms
20 days agoHandshake completed997 ms
21 days agoHandshake completed1.09 s
23 days agoHandshake completed737 ms

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

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