robo-cortex MCP server
io.github.robotel-limited/robo-cortex·v0.4.1·1 starsGit-aware memory store for AI coding agents; memories are anchored to git blob hashes.
1 stars18 downloads/wk
Reviews
Write oneNobody has reviewed robo-cortex yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
robo-cortex tools (8, 1 write)
write = sends, deletes, buys or postsRead from the package source without running it. The installed server may list more.
attach_evidencechange_statusMove a memory to a deliberate, final state (superseded, invalidated, abandoned, archived) or manually back to active. new_status='active' re-verifies: every linked path's blob hash is recaptured against current HEAD and last_verified_at is set to now, so the next retrieve_context/search_memory call doesn't immediately re-flag needs_review. `scope` disambiguates a memory_id that collides between th
get_memorylist_affectedWhat does a diff put at risk -- the proactive half of invalidation. Default (all omitted): working tree + staged combined. Runs the staleness refresh first, so anything already committed since the last check is flagged/healed for real before the diff-scoped report is computed.
record_memorywrite actionCreate a memory -- the only way new memories enter the store (explicit authorship). Linked paths are validated to exist at HEAD before anything is written; a dead link is refused loudly. scope='global' memories are written to the reusable cross-project store, require non-empty assumptions, and cannot have linked paths. No inline evidence field -- call attach_evidence afterward.
retrieve_contextsearch_memoryverify_evidence
Public scan report
scanner v0.1.9 · 2026-09-25 · same rubric, same numbers if you re-run it
- Code scan41 source files scanned25/25
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 26 days ago15/15
- Maintainer identityregistry namespace matches repository owner6/10
How robo-cortex compares
Against every graded E-commerce MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 89/100
- higher than 87% of 2,174 E-commerce servers
- Tools
- 8
- the typical E-commerce server has 6
- Tools that change things
- 13%
- typical: 0%. Fewer write tools means less an agent can break
- GitHub stars
- 1
- more than 65% of 1,047 E-commerce servers
- Downloads a week
- 18
- more than 5% of 411 E-commerce servers with a package
What its tools let an agent do: 7 read · 1 change
Install robo-cortex in Claude Code, Cursor or VS Code
claude mcp add robo-cortex -- uvx robo-cortex
What the publisher says
From the robo-cortex repository's README, as published. We do not edit it. Read it on GitHub
robo-cortex
<!-- mcp-name: io.github.robotel-limited/robo-cortex -->
Git-aware knowledge integrity for AI coding agents.
Your AI agent debugs a bug, learns the lesson, and forgets it by next week — or worse, keeps citing a "lesson" that the code has since made false. robo-cortex is a local knowledge base built for that specific failure mode: memories are anchored to git blob hashes, so when the code they're about changes, the memory is automatically flagged for review instead of being silently trusted or silently lost. In other words: drift detection and stale-memory detection for AI agent memory, done deterministically from git history — not an LLM guess, not an embedding-similarity heuristic.
Why robo-cortex, not another memory tool
Most agent-memory tools are embeddings + a vector database + a cloud dependency. robo-cortex is deliberately none of that. Four things it does that a generic key-value memory store doesn't:
- Git-aware staleness (drift) detection. Every memory can link to specific file paths, captured by git blob hash at record time. When the linked code changes, the memory is automatically flagged needsreview on the next retrieve/search/affected call — and a committed revert automatically heals it back. The healing requires three conditions: (a) the revert must be committed (git blob hash must match HEAD again), (b) the memory must have been flagged by the system (not manually via changestatus), and (c) you must run a lazy trigger (retrieve/search/affected) after the revert to scan for changes. Few memory tools tie themselves to your actual code's history this deterministically — no embedding similarity, no LLM judgment call, just a git blob hash matching or not.
- Evidence, not vibes. Memories can carry attached evidence (test output, a commit, a re-runnable command) with a mechanically computed strength — not a judgment call. A provisional memory only becomes active once real evidence backs it, or a human explicitly promotes it.
- Zero dependencies, fully local. Pure stdlib + SQLite (FTS5 for search). No embeddings, no API keys, no network calls unless you explicitly configure Gitea evidence verification. .cortex/memory.db is just a file — inspect it with sqlite3 any time.
- A real lifecycle with an audit trail. Every status change (active → superseded → archived, etc.) requires a --reason, permanently recorded. Nothing disappears silently; wrong lessons are marked invalidated, not deleted.
Measured impact (benchmark, honestly stated)
Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
robo-cortex: common questions
- Is robo-cortex MCP server safe?
- Yes, by our scan: it is graded A (89/100). Read the robo-cortex safety report
- How do I install robo-cortex?
- It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
- Does robo-cortex need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is robo-cortex maintained?
- The last commit was 65 days ago (2026-08-31). The latest release is v0.4.1.
- What can I use instead of robo-cortex?
- Servers from other publishers that do the same job: Mneme Memory MCP server, Delx Memory MCP server and Kagura Memory Cloud MCP server.
- How does robo-cortex compare with other E-commerce MCP servers?
- safety score 89/100 (higher than 87% of 2,174 E-commerce servers); tools 8 (the typical E-commerce server has 6); tools that change things 13% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.
Alternatives to robo-cortex
Same job from other publishers: the closest match first, then the best rated.
- Mneme MemoryCross-session memory for AI coding agents via six tools; local-first SQLite store.not reviewedEstablishedA
- Delx MemoryLocal-first persistent memory MCP: shared SQLite key/value store, searchable, TTL-aware, secret-safenot reviewedGrowingA
- Kagura Memory CloudPersistent memory for AI assistants: store, search, and connect knowledge across conversations.not reviewedGrowingA
- Vectros AITyped record store + hybrid search over MCP: deterministic lookups + semantic memory, per-customer.not reviewedGrowingB
- Loki ModeAutonomous spec-to-product coding-agent CLI with an MCP server exposing 39 tools over stdio.not reviewedEstablishedB