Browse / MCP servers
lucasmartins-ai/lookacrawler
Free, open-source, token-efficient local alternative to Firecrawl with native MCP Server for LLMs (>73% token reduction).
- MCP
Works.Tested on 2026-10-27. From the README alone, on Linux with Haiku and Linux with Luna.
What we checked
Does it run from the README?Yes. Running in 1:37 on a clean Linux box.The run
Tested Oct 27, 2026, rev bc5ce11.
Does it do what the README says?1 of 1 claims held up.Evidence
“The antislop command flags cliché or exaggerated copy and reports violations.”
Expected JSON reports isSlop true and two violations. Got "isSlop": true.
Which setups did we try?Works with Haiku, Luna.Setups
Linux / Haiku: works, Oct 27, rev bc5ce11. Linux / Luna: works, Oct 27, rev bc5ce11.
Needs keys, a login or a browser?No.Details
None seen
Is it safe to run?Made outbound HTTPS connections: yes (hosts not recorded) by <guest-path>, <guest-path>What we saw
Review signals across current setups: connection review, sensitive read. 186 listed items (named-host connections, static matches, dependency advisories) are below and do not change this verdict.
Repository processes attempted these non-loopback connections; proxies can hide the final hostname. 25 distinct locations. 2 findings. 9 attributed processes.
OSV reports a known vulnerability in this dependency version. 15 distinct locations. 93 findings.
A repository process attempted to read this sensitive path. Kind of file: package registry login. 2 findings. 2 attributed processes.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written; read only test files inside the test workspace or its temporary folders.
Reviewed as expected for a test run: attempted writes that failed, so nothing was written; read only test files inside the test workspace or its temporary folders; resolver address lookups that send no data.
Full event, path and process lists for each observed setup:
A quiet run is not a safety guarantee.
Is it maintained?Maintained · 47 commits in 90 days · 19 merged PRs in 90 days · 1 open issues · 2 open PRsActivity
actively maintained: last commit 7 days ago; 47 commits and 19 merged PRs in 90 days; 1 open issues, 2 open PRs; 1 of 10 recent threads got a maintainer reply, median first reply 161.8h; latest release 2026-10-11
Can I show this on my README?Copy the badge.Badge
The run
Oct 27 · rev bc5ce11Independent test, not endorsed by the project.