io.github.OmerTurkenits/flownav
io.github.OmerTurkenits/flownav
Is the io.github.OmerTurkenits/flownav MCP server down? It gave no valid answer in the probe of 2026-11-10: crashed on start. One failed probe is not an outage.
Read-only graph of n8n workflows for AI agents: explain, affected, check, scoped code reads.
crashed on start no valid answer since 2026-11-10 · probed 2026-11-14 · unchanged since 2026-11-10
MCP error -32000: Connection closed diff <old> <new> install [options] <target> Install the agent skill (target: claude) serve
- Run it
- npx -y flownav@0.2.2 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/OmerTurkenits/flownav
- Registry
- active, updated 2026-11-09 · 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.OilpriceAPI/mcp-server · needs env
- Obsidian Vault MCP Server io.github.OleksandrKucherenko/mcp-obsidian-via-rest · crashed on start
- io.github.OliverGrabner/composer · timeout
- io.github.OlivierLAVAUD/mcp-immo · alive
- OmniPost io.github.OmniGoAI/omnipost · not found
- io.github.OmniSocKit/omnisockit-mcp · alive
- io.github.Omodaka9375/netexpert-mcp · alive
- io.github.Omodaka9375/ugnas-mcp · needs env
Servers that mention workflows or affected.
- ac.tandem/docs-mcp · alive
- China Marketing AI Intelligence MCP ai.chinamarketing/intelligence · needs auth
- Dreamlit ai.dreamlit/mcp · alive
- Gemus ai.gemus/gemus · needs auth
- Hexa ai.hexahq/hexa · needs auth
- ai.orgsdk/mcp · no DNS
- Orisu ai.orisu/orisu · needs auth
- Roster ai.rosterresolve/roster · needs your URL
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
- The package did not start as an MCP server at its probe on 2026-11-10. One failed probe is not an outage: the board calls a package down when it fails again at its next probe, a week later.
- The process exited on start before it answered initialize. The error output is above.