io.github.under71/lupa-mcp
Lupa — local file search for your Mac
Is the Lupa MCP server down? Yes. It has given no valid answer since 2026-10-26: install failed.
Search your Mac's files by name and by text inside documents. Local index, Korean-aware.
install failed down since 2026-10-26 · probed 2026-11-14 · unchanged since 2026-11-02
npm error notsup Valid os: darwin npm error notsup Actual os: linux npm error A complete log of this run can be found in: /root/.npm/_logs/2026-11-09T08_53_09_
- Run it
- npx -y lupa-mcp@0.3.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/under71/lupa-mcp
- Website
- https://lupa.kr/agents.html
- Registry
- active, updated 2026-10-24 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- io.github.umbraco/Umbraco-CMS-MCP-Dev · needs env
- io.github.umitkavala/mindpm · alive
- Inferthat io.github.ummmno/inferthat · alive
- io.github.uncfreak1255-code/hostaway · alive
- unerr io.github.unerr-ai/unerr · crashed on start
- Vessel Browser io.github.unmodeled-tyler/vessel-browser · not probed
- thing io.github.unravel-team/thing · alive
- mail-index io.github.unsoldgroup/mail-index · crashed on start
Servers that mention lupa.
- LVL Up Auto — Dealership Vendor Catalog com.lvlupauto/vendor-catalog · needs auth
- io.github.janmalmstrom/lupaph-mcp · alive
- Lupamundo com.lupamundo/lupamundo · alive
- Lupa — local file search for your Mac io.github.paeyoungpark-web/lupa-mcp · install failed
- Lupa Shop br.net.lupashop/lupa-shop · alive
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- No valid answer since 2026-10-26, in every probe since then.
- npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.