Remote MCP · Endpoint

io.github.DataLeadsPRO/captchaflow MCP server

No. io.github.DataLeadsPRO/captchaflow answered an MCP handshake 11 hours ago.

UpLast checked 11 hours 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
289 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 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
11 hours agoHandshake completed289 ms
2 days agoHandshake completed400 ms
4 days agoHandshake completed289 ms
6 days agoHandshake completed305 ms
7 days agoHandshake completed297 ms
8 days agoHandshake completed284 ms
9 days agoHandshake completed435 ms
12 days agoHandshake completed319 ms
14 days agoHandshake completed311 ms
15 days agoHandshake completed358 ms
16 days agoHandshake completed348 ms
17 days agoHandshake completed358 ms
19 days agoHandshake completed305 ms
19 days agoHandshake completed350 ms
20 days agoHandshake completed285 ms
21 days agoHandshake completed293 ms
23 days agoHandshake completed1.10 s

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