io.github.chaoscypherinc/chaoscypher

Chaos Cypher

Is the Chaos Cypher MCP server down? Yes. It has given no valid answer since 2026-10-18: install failed.

Local-first knowledge graphs from your documents: build, search (GraphRAG) and edit on your machine.

install failed down since 2026-10-18 · probed 2026-11-14 · unchanged since 2026-11-07

error: No solution found when resolving dependencies   cause: Because the current Python version (3.13.18) does not satisfy Python>=3.14 and chaoscypher-cli==0.

Run it: uvx chaoscypher-cli@0.7.2 (stdio, probed in a container with the network off)
Host: pypi.org
Repository: https://github.com/chaoscypherinc/chaoscypher
Website: https://chaoscypher.com
Registry: active, updated 2026-11-06 · registry entry

Compare this server with others.

More servers

Other registry entries on pypi.org, the ones next to this name; all of them.

io.github.certindex/certindex-mcp · needs mcp<2
ReasonGate io.github.cgrtml/reasongate · needs args
nable io.github.chaandannn/finops-mcp · needs mcp<2
io.github.chanyou0311/aiseg2-mcp · alive
io.github.chaoz23/charactercheck · crashed on start
io.github.chaoz23/dmcheck · crashed on start
loudcheck io.github.chaoz23/loudcheck · needs args
io.github.chaoz23/srdcheck · crashed on start

Servers that mention cypher or chaos.

io.github.lonniev/cypher-mcp · needs auth
Chaos Index io.github.pipeworx-io/chaos-index · error
net.composedchaos/speed-to-lead · needs auth
Chaos — OKX Perpetual Signals tw.okx/chaos · alive
io.github.cuonztech/agent-harness · alive
io.github.mrfentmen/blockcypher-mcp · alive
io.github.neo4j-contrib/mcp-neo4j-cypher · crashed on start
Deep Agentic Core MCP io.github.DeepAgentLabs/deep-agentic-core-mcp · 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.

Atom feed

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.
npx or uvx could not install the package. The package name in the registry entry is wrong, the package is not published, or the install needs a build step.