io.github.vncsleal/openplan
io.github.vncsleal/openplan
Is the io.github.vncsleal/openplan MCP server down? Yes. It has given no valid answer since 2026-10-17: not found.
Plan, track, and learn from software projects — three MCP tools for the AI agent lifecycle.
not found down since 2026-10-17 · probed 2026-11-14 · unchanged since 2026-10-31
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 @openplan/mcp@0.1.22 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/vncsleal/openplan
- Registry
- active, updated 2026-06-22 · 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.vmoranv/jshookmcp · alive
- ViBo Memory io.github.vnbochkarev-netizen/vibo-mcp · alive
- io.github.vnbochkarev-netizen/vibo-memory · alive
- io.github.vnbochkarev-netizen/vibocode-mcp · needs network
- io.github.voidfeedai-ops/voidfeed-mcp · alive
- Voidly Agent Wallet io.github.voidly-ai/agent-wallet-kit · crashed on start
- Voidmail Agent Email io.github.voidly-ai/mcp-email · alive
- Voidly io.github.voidly-ai/mcp-server · alive
Servers that mention openplan or lifecycle or projects.
- OpenPlanr Docs dev.openplanr/docs · alive
- Dubai Data — Dubai real estate statistics ae.datadubai/dubai-real-estate · alive
- Alpic ai.alpic.mcp/alpic-mcp · needs auth
- Atako ai.atako/mcp · needs auth
- Project Desk ai.atlier/project-desk · needs auth
- AutoRFP.ai ai.autorfp/mcp · needs auth
- BeatBandit MCP ai.beatbandit/beatbandit · needs auth
- ai.bridgeapp/bridgeapp · needs auth
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-17, 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.