Remote MCP · Endpoint

Solvecha MCP server

No. Solvecha answered an MCP handshake 59 minutes ago.

UpLast checked 59 minutes ago

Server URL

https://api.solvecha.com/mcp

The last check completed an MCP handshake.

Registry name
com.solvecha/solvecha
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
435 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Solve reCAPTCHA image grids, text captchas, GeeTest and FunCAPTCHA for AI agents. Free tier.
Listing
From the official MCP registry (active).
Recent checks of Solvecha
CheckedResultHandshake
59 minutes agoHandshake completed435 ms
9 days agoHandshake completed402 ms
10 days agoHandshake completed368 ms
11 days agoHandshake completed490 ms
12 days agoHandshake completed513 ms
14 days agoHandshake completed388 ms
14 days agoHandshake completed388 ms
15 days agoHandshake completed376 ms
17 days agoHandshake completed653 ms
19 days agoHandshake completed380 ms
21 days agoHandshake completed368 ms
24 days agoHandshake completed389 ms
26 days agoHandshake completed390 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 Solvecha and makes no claim about it beyond what these checks measured.