Remote MCP · Endpoint

LensaOCR MCP server

Yes, as of 2 days ago: the hostname does not resolve.

DownLast checked 2 days ago

Server URL

https://lensaocr.saastemly.com/mcp

The last check failed: the hostname does not resolve.

Registry name
com.saastemly/lensaocr
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
1 tool
Uptime, last 30 days
76.9% from 13 checks
Described by its publisher as
Tesseract-compatible OCR over HTTP: send an image, get its text and word boxes in Tesseract's...
Listing
From the official MCP registry (active).
Recent checks of LensaOCR
CheckedResultHandshake
2 days agoFailed - the hostname does not resolve—
5 days agoFailed - the hostname does not resolve—
7 days agoFailed - the hostname does not resolve—
9 days agoHandshake completed498 ms
11 days agoHandshake completed93 ms
13 days agoHandshake completed65 ms
15 days agoHandshake completed77 ms
17 days agoHandshake completed69 ms
19 days agoHandshake completed47 ms
20 days agoHandshake completed83 ms
21 days agoHandshake completed76 ms
22 days agoHandshake completed76 ms
25 days agoHandshake completed55 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 10 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 LensaOCR and makes no claim about it beyond what these checks measured.