Remote MCP · Endpoint

WebLens MCP server

No. WebLens answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.weblens.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.weblens/weblens
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
305 ms
Tools exposed
27 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Scrape, crawl, map and extract the web. Pay per call in USDC, no account or API key.
Listing
From the official MCP registry (active).
Recent checks of WebLens
CheckedResultHandshake
1 hour agoHandshake completed305 ms
2 days agoHandshake completed230 ms
4 days agoHandshake completed281 ms
5 days agoHandshake completed208 ms
7 days agoHandshake completed182 ms
8 days agoHandshake completed474 ms
9 days agoHandshake completed222 ms
12 days agoHandshake completed38 ms
13 days agoHandshake completed267 ms
15 days agoHandshake completed194 ms
16 days agoHandshake completed474 ms
18 days agoHandshake completed210 ms
19 days agoHandshake completed333 ms
20 days agoHandshake completed190 ms
20 days agoHandshake completed238 ms
21 days agoHandshake completed215 ms
22 days agoHandshake completed293 ms

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