AICortex runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 5 Nov 2026.
Self-hosted brain for any LLM: memory, skills, encrypted vault, devices and scheduled jobs.
What the code does
We read the source, 1 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return yaml.load(value, Loader=_NoAliasLoader), ""
done = subprocess.run(shlex.split(cmd), capture_output=True, text=True, timeout=5)
env = server_env(Path.cwd() / ".glama-data", port, dict(os.environ))
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to AICortex
same job, measured the same wayShared memory and teamwork for AI agents: knowledge base, memories, tasks, encrypted vault.
GitLab CI/CD MCP — pipelines, jobs, schedules, MRs, files. Any GitLab (SaaS or self-hosted).
Shared MCP memory for AI agents: knowledge base, skills, todos and agent-to-agent handoffs.
Self-hosted memory for LLMs in TriliumNext, structured by the server and editable by you.
Encrypted mail, shared memory, and persistent context for AI agents.
Local-first shared memory for AI tools. Your files, encrypted at rest by default; budgeted reads.
Your Obsidian vault as private, searchable memory for Claude, Cursor, Hermes and any MCP client
Persistent, encrypted, deterministic memory for AI agents. Local-first, 173 canonical tools.
AICortex — questions
Answers built from our own checks of this server.