Remote MCP · Endpoint
captcha.cc Human Verification MCP server
No. captcha.cc Human Verification answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://captcha.cc/mcp
The last check completed an MCP handshake.
- Registry name
- cc.captcha/captchacc
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 158 ms
- Tools exposed
- 3 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Human verification CAPTCHA with visual and selective-listening audio challenges.
- Website
- https://captcha.cc/docs/mcp
- Repository
- https://github.com/earonesty/captcha
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 158 ms |
| 13 hours ago | Handshake completed | 378 ms |
| 1 day ago | Handshake completed | 199 ms |
| 3 days ago | Handshake completed | 291 ms |
| 4 days ago | Handshake completed | 154 ms |
| 4 days ago | Handshake completed | 183 ms |
| 5 days ago | Handshake completed | 56 ms |
| 6 days ago | Handshake completed | 249 ms |
| 8 days ago | Handshake completed | 401 ms |
| 11 days ago | Handshake completed | 268 ms |
| 13 days ago | Handshake completed | 305 ms |
| 16 days ago | Handshake completed | 160 ms |
| 18 days ago | Handshake completed | 176 ms |
| 20 days ago | Handshake completed | 196 ms |
| 22 days ago | Handshake completed | 217 ms |
| 24 days ago | Handshake completed | 288 ms |
| 26 days ago | Handshake completed | 281 ms |
| 27 days ago | Handshake completed | 174 ms |
| 29 days ago | Handshake completed | 226 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 31 responding of 31.
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.cc Human Verification and makes no claim about it beyond what these checks measured.