io.github.ataberk-xyz/gossipcat
io.github.ataberk-xyz/gossipcat
Is the io.github.ataberk-xyz/gossipcat MCP server down? Yes. It has given no valid answer since 2026-10-18: crashed on start.
Multi-agent orchestration for Claude Code — consensus review, adaptive dispatch, skill learning
crashed on start down since 2026-10-18 · probed 2026-11-15 · unchanged since 2026-11-01
MCP error -32000: Connection closed Error: ENOENT: no such file or directory, open '/work/.gossip/mcp.log' syscall: 'open', path: '/work/.gossip/mcp.log' }
- Run it
- npx -y gossipcat@0.2.1 (stdio, probed in a container with the network off)
- Host
- npmjs.com
- Repository
- https://github.com/gossipcat-ai/gossipcat-ai
- Registry
- active, updated 2026-04-10 · registry entry
Compare this server with others.
More servers
Other registry entries on npmjs.com, the ones next to this name; all of them.
- Local YDB MCP io.github.astandrik/local-ydb-mcp · alive
- io.github.asume21/music-theory-mcp · alive
- io.github.asume21/webear · alive
- Papyrio PDF Tools io.github.atabekdemurtaza/papyrio-mcp · alive
- Sheets MCP io.github.atc07/sheets-mcp · alive
- io.github.atef-ataya/depwire · alive
- io.github.atheris-ee/atheris-mcp · alive
- io.github.athlan20/slg-mcp · alive
Servers that mention orchestration or consensus.
- ai.getvda/llm-observability-orchestration · newer protocol
- ai.getvda/llm-observability-orchestration-agent-langchain · newer protocol
- ai.getvda/llm-observability-orchestration-agent-langchain-community · newer protocol
- ai.getvda/llm-orchestration-agent-2 · newer protocol
- ai.getvda/llm-orchestration-agent-2-df5979 · newer protocol
- ai.getvda/llm-orchestration-agent-cryptography · newer protocol
- ai.getvda/llm-orchestration-agent-d0a1a1 · newer protocol
- ai.getvda/llm-orchestration-agent-d2feb0 · newer protocol
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-18, in every probe since then.
- The process exited on start before it answered initialize. The error output is above.