Is the com.saastemly/lensaocr API still reachable?

Is the com.saastemly/lensaocr API still reachable?

No, not at the address its own documentation gives. The host declared as its server did not resolve in DNS on 2026-10-26, across 8 indexed operations. A document can look current and still name a host that no longer exists — nothing looks wrong until the call.

ERR-2026-7287, ERR-2026-7288, ERR-2026-7289, ERR-2026-7290, ERR-2026-7291, ERR-2026-7292, ERR-2026-7293, ERR-2026-7294

Every record behind those answers

8 open records, observed 2026-09-10. Every claim below carries the command that disproves it. If one is wrong, it should be withdrawn — 1089 have been across the whole registry.

the host no longer exists (8)

The host of the declared document or endpoint no longer resolves in DNS.

ERR-2026-7287https://crawl4agent.saastemly.com/mcpDNS failure for crawl4agent.saastemly.com: [Errno -2] Name ochecked 2026-10-26
ERR-2026-7288https://lensaocr.saastemly.com/mcpDNS failure for lensaocr.saastemly.com: [Errno -2] Name or schecked 2026-10-26
ERR-2026-7289https://mem0-cloud.saastemly.com/mcpDNS failure for mem0-cloud.saastemly.com: [Errno -2] Name orchecked 2026-10-26
ERR-2026-7290https://puptra-pdf-snapshot.saastemly.com/mcpDNS failure for puptra-pdf-snapshot.saastemly.com: [Errno -2checked 2026-10-26
ERR-2026-7291https://sandboxd-code-run.saastemly.com/mcpDNS failure for sandboxd-code-run.saastemly.com: [Errno -2] checked 2026-10-26
ERR-2026-7292https://supervision-draw.saastemly.com/mcpDNS failure for supervision-draw.saastemly.com: [Errno -2] Nchecked 2026-10-26
ERR-2026-7293https://uuid-forge.saastemly.com/mcpDNS failure for uuid-forge.saastemly.com: [Errno -2] Name orchecked 2026-10-26
ERR-2026-7294https://visionflow-match.saastemly.com/mcpDNS failure for visionflow-match.saastemly.com: [Errno -2] Nchecked 2026-10-26

Check it yourself:

curl -s -X POST https://crawl4agent.saastemly.com/mcp -H 'content-type: application/json' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"check","version":"1"}}}'

Also filed as: com.saastemly, com.saastemly/crawl4agent, com.saastemly/mem0-cloud, com.saastemly/puptra-pdf-snapshot, com.saastemly/sandboxd-code-run, com.saastemly/supervision-draw, com.saastemly/uuid-forge, com.saastemly/visionflow-match. One page, because two sweeps named the same subject differently and the record that mattered was on the page nobody would open.

If a record here is wrong

Run its check. If the answer differs from what is written, say so here and it will be withdrawn — 1089 already have been. A record nobody can contest is a record asking to be trusted, which is the opposite of the point.

Asking about something else

You arrived here about one subject. For any other — before you use it — one request, no account and no key:

GET https://apidefects.com/check?tool=<identity>

<identity> is whatever you already hold: an MCP registry entry (io.github.owner/repo), a deployment URL, an OpenAPI document URL, an npm or PyPI package name, or a host. The answer is one of three — defects_known, examined_nothing_open, or never_examined — and the third is not a clean bill of health. If you speak MCP, this registry is itself one server at https://apidefects.com/mcp, one tool, the same three answers.

What this page does not tell you

This is not a clean bill of health for anything not listed. The registry was built from a sample of two directories, and an operation absent from it was almost certainly never examined. Silence here means not looked at, not looked at and fine — which is the same mistake this registry exists to record in other people.

What this is

A record of defects in the public description of machine-callable operations: documents a directory claims are live and are not, hosts that no longer resolve, specifications that contradict the API they describe. It is not a ranking, not a review, and not a judgement about the service. No credential is ever sent to anything listed here.

The whole registry, machine-readable: errata.json. Index of subjects: index.html.

Built from registry errata-2026-09-10@5d7424202eae. If manifest.json shows a different one, this page is behind the records and should not be trusted over them.