Remote MCP · Endpoint

io.github.DataLeadsPRO/captchaflow MCP server

No. io.github.DataLeadsPRO/captchaflow answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://captcha.dataleads.pro/mcp/captchaflow

The last check completed an MCP handshake.

Registry name
io.github.DataLeadsPRO/captchaflow
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
275 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Universal captcha solving with the industry-standard createTask / getTaskResult protocol, 19 task
Listing
From the official MCP registry (active).
Recent checks of io.github.DataLeadsPRO/captchaflow
CheckedResultHandshake
1 hour agoHandshake completed275 ms
1 day agoHandshake completed296 ms
3 days agoHandshake completed290 ms
3 days agoHandshake completed311 ms
4 days agoHandshake completed584 ms
5 days agoHandshake completed292 ms
7 days agoHandshake completed304 ms
10 days agoHandshake completed283 ms
12 days agoHandshake completed281 ms
15 days agoHandshake completed291 ms
17 days agoHandshake completed290 ms
19 days agoHandshake completed287 ms
21 days agoHandshake completed289 ms
23 days agoHandshake completed400 ms
25 days agoHandshake completed289 ms
26 days agoHandshake completed305 ms
28 days agoHandshake completed297 ms
29 days agoHandshake completed284 ms

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

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 io.github.DataLeadsPRO/captchaflow and makes no claim about it beyond what these checks measured.