dev.weavetab/mcp
Weavetab
Is the Weavetab MCP server down? Yes. It has given no valid answer since 2026-10-24: crashed on start.
Open automation engine for AI agents. Control live browsers and desktop apps locally.
crashed on start down since 2026-10-24 · probed 2026-11-14 · unchanged since 2026-10-31
MCP error -32000: Connection closed [Weavetab] Fatal: [!] Weave failed: Running as root is not allowed. Start Weavetab as a normal user.
- Run it
- npx -y @weavetab/mcp@2.5.0 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/Weavetab/mcp
- Registry
- active, updated 2026-10-17 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- vetkit dev.vetkit/mcp · needs env
- vid2llm dev.vid2llm/mcp · alive
- dev.waxberry/live-translate-mcp · crashed on start
- dev.weakspot/weakspot · alive
- WireCat pbx dev.wirecat/asterisk-cli · crashed on start
- WireCat b24 dev.wirecat/bitrix24-cli · crashed on start
- WireCat Memo dev.wirecat/cli-memo · alive
- WireCat Google Drive dev.wirecat/drive-cli · crashed on start
Servers that mention automation or browsers.
- Bowmark web data: LinkedIn, Amazon, YouTube, Reddit, Airbnb, Instagram ai.bowmark/bowmark · alive
- D50 AI — Sales, Marketing & Hiring Automation ai.d50/d50-platform · needs auth
- Hyreflow ai.hyreflow/hyreflow · needs auth
- JustAutomate website ai.justautomate/website · alive
- TinyFish AI Web Agent ai.mino/web-agent · needs auth
- Mozark MCP Server ai.mozark/mcp · not found
- NativePort ai.nativeport/mcp · needs auth
- TEK BOSS Small Business AI Strategy Assessment ai.tekboss/assessment · 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-24, in every probe since then.
- The process exited on start before it answered initialize. The error output is above.