cc.qataroasis/cortex
cc.qataroasis/cortex
Is the cc.qataroasis/cortex MCP server down? No. It is up and needs network, probed 2026-11-20.
Local-first memory for Claude Code and Cursor: 33 MB Go binary, ~50 ms hybrid search, no cloud.
needs network probed 2026-11-20
MCP error -32000: Connection closed [cortex-mcp-local] first run: downloading cortex-linux-amd64.tar.gz (v4.0.1) for linux [cortex-mcp-local] getaddrinfo EAI_AG
- Bundle
- https://github.com/lh123aa/cortex/releases/download/v4.0.1/cortex-local-memory-4.0.1.mcpb (MCPB, for a client that installs bundles; probed in a container with the network off)
- Host
- github.com
- Repository
- https://github.com/lh123aa/cortex
- Website
- https://cortex.qataroasis.cc
- Registry
- active, updated 2026-11-19 · registry entry
Compare this server with others.
More servers
Other registry entries on github.com, the ones next to this name; all of them.
- PostSail app.postsail/postsail · alive
- ScreenPost app.screenpost/screenpost · alive
- ShowTake app.showtake/showtake · crashed on start
- Filmlog cc.filmlog/filmlog · crashed on start
- Yap cc.yapapp/yap · alive
- LocalCloud MCP cloud.local/localcloud · alive
- AhaSignals Evidence com.ahasignals/evidence · alive
- Autodesk Fusion com.autodesk.aps.api/fusion-local-mcp · crashed on start
Servers that mention cortex.
- com.cortexpad/cortexpad · needs auth
- AI Cortex Storage dev.aic0rt3x.memory/mcp · timeout
- CortexPlus io.cortexplus/cortexplus · alive
- Cortex io.github.100monkeys-ai/cortex · needs your URL
- Cortex io.github.FilippoPilo/cortex · alive
- AnswerPool (formerly CortexAssay) io.github.blakeyounger/cortexassay · not found
- io.github.jonahthan433/cortexcloud · alive
- io.github.meltingpixelsai/zero-core-intel · not found
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 server tries to reach the network on start. The probe runs in a container with the network off, so a server that connects lazily, on the first tool call, is measured.