Memory, reflection and safety for AI agents. Hosted or local, no vector database.
MCPpedia last refreshed this data
Cognicore Env is an MCP server that memory, reflection and safety for AI agents. Hosted or local, no vector database. Its tool list has not been published yet over stdio and sse, requires no API key, and scores 88/100 on MCPpedia's security, maintenance and efficiency rubric.
Config is the same across clients - only the file and path differ.
{
"mcpServers": {
"cognicore-env": {
"args": [
"cognicore-env"
],
"command": "uvx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Memory, reflection and safety for AI agents. Hosted or local, no vector database.
This server supports HTTP transport. Be the first to test it - help the community know if it works.
Five weighted categories - click any category to see the underlying evidence.
No known CVEs.
Checked cognicore-env against OSV.dev.
Click any tool to inspect its schema.
Be the first to review
Have you used this server?
Share your experience - it helps other developers decide.
Sign in to write a review.
Others in ai-ml
A cross-platform desktop application for managing AI Agents and MCP Servers. 一款用于管理AI智能体与MCP服务器的跨平台桌面应用程序。
Codebase knowledge graph for AI agents — 162 languages, sub-ms queries, 99% fewer tokens.
An open-source AI agent that brings the power of Gemini directly into your terminal.
🛡️ BLA (Blind LLM Agents) — Adversarial defense shield that protects binaries, Electron apps, JS bundles, Python, and WebAssembly against AI reverse-engineering agents like REA. Poison -> Exhaust -> Hallucinate.
MCP Security Weekly
Get CVE alerts and security updates for Cognicore Env and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Memory that moves between your coding agents. Work in Claude Code, then continue in Codex or claude.ai with the same ticket, the same decisions and the same open follow-up. There's nothing to re-explain.
If this saves you a session, a star helps other people find it.

pipx install "cognicore-env[mcp]" # or: uv tool install "cognicore-env[mcp]"
cognicore install # sets up Claude Code and Codex
Restart Claude Code. In Codex, run /hooks once and trust the three CogniCore hooks. To share memory with claude.ai, Claude Desktop and mobile, also run cognicore login.
Prefer to install from inside Claude Code? Run /plugin marketplace add cognicore-dev/cognicore-env, then /plugin install cognicore@cognicore-beta-marketplace.
Measured on real Claude Code and Codex sessions against claude-mem 15.7.0. In each task, session 1 does part of a job, its transcript is moved out of reach, and a fresh session 2 must finish a deferred follow-up and answer 8 questions. Both systems got every follow-up right.
| CogniCore | claude-mem | |
|---|---|---|
| Hands work from Claude Code to Codex | ✅ | ✅ |
| New tokens per 3-task benchmark (incl. background) | 53k–60k | 147k–216k |
| Memory ready after a session ends | ~1 second | 70–130 seconds |
| Brief injected at the next start | ~450 tokens | ~1,080 tokens |
| Model calls to save a session | 0 (optional AI compression) | one per tool use |
Method and full results: docs/transfer-audit.md. Rerun them yourself with scripts/bench_realworld.py.
cognicore_save_session and cognicore_resume_session.~/.cognicore/mcp (SQLite). CogniCore never reads tool output, file contents or the model's thinking, and it redacts secrets before saving.cognicore login once. Claude Code and Codex sessions then reach your hosted account, and sessions from the CogniCore connector come back. Only the redacted handoff is sent, never the transcript.python -m cognicore.memory.viewer opens a read-only page listing every saved session.Plugin details: plugins/cognicore/README.md · full-quality demo: MP4
Under the plugin is a Python library for persistent memory, reflection and safety in any agent. It needs no vector database, no embedding server and no external service; the only required dependencies are numpy, jsonschema and requests.
An agent debugs an issue, finds the fix, and the session ends. The next run star