RRepoGEO

REPOGEO REPORT · LITE

mex-memory/mex

Default branch main · commit c341ee73 · scanned 6/22/2026, 9:41:23 PM

GitHub: 1,007 stars · 60 forks

AI VISIBILITY SCORE
40 /100
Critical
Category recall
0 / 2
Not recommended in any query
Rule findings
2 pass · 0 warn · 0 fail
Objective metadata checks
AI knows your name
3 / 3
Direct prompts that named your repo
HOW TO READ THIS REPORT

Action plan is what to do next — copy-pasteable changes prioritized by impact. Category visibility is the real GEO test: when a user asks an AI a brand-free question that should surface mex-memory/mex, does the AI actually recommend you — or your competitors? Objective checks verify the metadata signals AI engines weight first. Self-mention check detects whether AI even knows you exist by name.

Action plan — copy-paste fixes

3 prioritized changes generated by gemini-2.5-flash. Mark items done after you ship the fix.

OVERALL DIRECTION
  • highabout#1
    Update repository description to explicitly differentiate from MATLAB

    Why:

    CURRENT
    Persistent project memory for AI coding agents. Structured scaffold + drift detection CLI.
    COPY-PASTE FIX
    Persistent project memory for AI coding agents (not MATLAB MEX). Structured scaffold + drift detection CLI for LLM context.
  • highreadme#2
    Add a prominent disclaimer about MATLAB MEX functions in README

    Why:

    COPY-PASTE FIX
    Note: This `mex` is for AI coding agents and is not related to MATLAB MEX functions.
  • mediumtopics#3
    Expand topics to include specific LLM agent terms and competitor alternatives

    Why:

    CURRENT
    claude-code, claude-code-skills, cli-tool, codex, context-management, cursor, developer-tools, documentation, llm, memory-management, typescript
    COPY-PASTE FIX
    claude-code, claude-code-skills, cli-tool, codex, context-management, cursor, developer-tools, documentation, llm, memory-management, typescript, llm-agents, agent-memory, ai-agent-context, langchain-alternative, llamaindex-alternative, generative-ai-tools

Category GEO backends resolved for this scan: google/gemini-2.5-flash, deepseek/deepseek-v4-flash

Category visibility — the real GEO test

Brand-free queries asked to google/gemini-2.5-flash. Did AI recommend you, or someone else?

Same questions for every model — switch tabs to compare answers and rankings.

Recall
0 / 2
0% of queries surface mex-memory/mex
Avg rank
—
Lower is better. #1 = top recommendation.
Share of voice
0%
Of all named tools, what % are you?
Top rival
LangChain
Recommended in 2 of 2 queries
COMPETITOR LEADERBOARD
  1. LangChain · recommended 2×
  2. LlamaIndex · recommended 2×
  3. Pinecone · recommended 1×
  4. Weaviate · recommended 1×
  5. ChromaDB · recommended 1×
  • CATEGORY QUERY
    How can I give my AI coding agent persistent memory and project context between sessions?
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. Pinecone
    3. Weaviate
    4. ChromaDB
    5. LlamaIndex
    6. SQLite
    7. PostgreSQL
    8. MySQL
    9. Watchdog
    10. GitPython

    AI recommended 10 alternatives but never named mex-memory/mex. This is the gap to close.

    Show full AI answer
  • CATEGORY QUERY
    Seeking a tool to manage LLM agent context, avoiding large, drifting instruction files.
    you: not recommended
    AI recommended (in order):
    1. LangChain
    2. LlamaIndex
    3. Haystack
    4. Semantic Kernel
    5. DSPy
    6. PromptSource
    7. Pydantic

    AI recommended 7 alternatives but never named mex-memory/mex. This is the gap to close.

    Show full AI answer

Objective checks

Rule-based audits of metadata signals AI engines weight most.

  • Metadata completeness
    pass

  • README presence
    pass

Self-mention check

Does AI even know your repo exists when asked about it directly?

  • Compared to common alternatives in this category, what is the core differentiator of mex-memory/mex?
    pass
    AI named mex-memory/mex explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • If a team adopts mex-memory/mex in production, what risks or prerequisites should they evaluate first?
    pass
    AI named mex-memory/mex explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

  • In one sentence, what problem does the repo mex-memory/mex solve, and who is the primary audience?
    pass
    AI named mex-memory/mex explicitly

    AI answers can be confidently wrong. Read for accuracy: does it match your actual tech stack, audience, and differentiator?

Embed your GEO score

Drop this badge into the README of mex-memory/mex. It auto-updates whenever the report is rescanned and links back to the latest report — easy public proof that you care about AI discoverability.

RepoGEO badge previewLive preview
MARKDOWN (README)
[![RepoGEO](https://repogeo.com/badge/mex-memory/mex.svg)](https://repogeo.com/en/r/mex-memory/mex)
HTML
<a href="https://repogeo.com/en/r/mex-memory/mex"><img src="https://repogeo.com/badge/mex-memory/mex.svg" alt="RepoGEO" /></a>
Pro

Subscribe to Pro for deep diagnoses

mex-memory/mex — Lite scans stay free; this card itemizes Pro deep limits vs Lite.

  • Deep reports10 / month
  • Brand-free category queries5 vs 2 in Lite
  • Prioritized action items8 vs 3 in Lite
mex-memory/mex — RepoGEO report