io.github.zguiyang/pi-worker-mcp
Pi Worker MCP
Is the Pi Worker MCP server down? Yes. It has given no valid answer since 2026-10-19: not found.
A host-agnostic MCP worker runtime for supervising local Pi coding-agent processes.
not found down since 2026-10-19 · probed 2026-11-15 · unchanged since 2026-10-26
npm error 404 Note that you can also install from a npm error 404 tarball, folder, http url, or git url. npm error A complete log of this run can be found in: /
- Run it
- npx -y @zguiyang/pi-worker-mcp@0.1.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/zguiyang/pi-worker-mcp
- Website
- https://github.com/zguiyang/pi-worker-mcp
- Registry
- active, updated 2026-10-08 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Zerostel io.github.zerostel/zerostel · alive
- io.github.zeroth-settlement/agdel-mcp · needs env
- io.github.zeynepaslierhan/promptlike-mcp · alive
- Pi TaskExec io.github.zguiyang/pi-task-exec · alive
- io.github.zh-xx/antu · crashed on start
- BrowserDo io.github.zhaijunlong/browserdo · install failed
- Notemend io.github.zharkodv-cmd/notemend · alive
- iFlow Search io.github.zhengyanglsun/iflow-search · alive
Servers that mention worker.
- Business Contact Finder agency.ottobot/business-contact-finder · alive
- Contractor Licence Changes agency.ottobot/contractor-license-changes · alive
- Auxen ai.auxen/auxen · needs auth
- ai.gigaverse/gigaverse · alive
- SOAR Record Gateway ai.lateos/soar-record-gateway · needs auth
- Rams ai.rams/rams · alive
- Tanjiren MCP Server app.tanjiren/tanjiren-mcp · no DNS
- app.tinkrr/intelligence · not found
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-19, in every probe since then.
- The endpoint answers HTTP 404. The registry entry points to a URL that is not an MCP endpoint any more. Publish a new version of the registry entry with the current URL.