Remote MCP · Endpoint

Captcha Solver MCP server

No. Captcha Solver answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://api.mcp.ai/p_captcha

The last check completed an MCP handshake.

Registry name
io.github.mcp-dir/captcha-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
46 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Solve reCAPTCHA v2/v3, hCaptcha, Cloudflare Turnstile and image captchas. Platform-hosted, no creden
Listing
From the official MCP registry (active).
Recent checks of Captcha Solver
CheckedResultHandshake
1 day agoHandshake completed46 ms
3 days agoHandshake completed51 ms
5 days agoHandshake completed31 ms
7 days agoHandshake completed98 ms
8 days agoHandshake completed291 ms
9 days agoHandshake completed29 ms
12 days agoHandshake completed58 ms
13 days agoHandshake completed57 ms
15 days agoHandshake completed815 ms
16 days agoHandshake completed61 ms
18 days agoHandshake completed68 ms
19 days agoHandshake completed522 ms
20 days agoHandshake completed3.17 s
20 days agoHandshake completed70 ms
21 days agoHandshake completed59 ms
22 days agoHandshake completed279 ms

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

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