MCP.Market

Memex MCP server

by STiFLeR7·io.github.STiFLeR7/memex·v1.0.3·12 stars
No reviews yet

Temporal engineering context for agents via MCP.

C65/100grade C
Write a reviewInstall
What users say
No reviews yet
Be the first
Safety scan
C65/100

full report

Adoption
Growing

12 stars489 downloads/wk

Reviews

Write one

Nobody has reviewed Memex yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Memex tools (15, 3 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • explain_change

    Cross-references a git commit's diff with linked Decision/Problem nodes and returns a grounded Markdown explanation synthesised by Gemini Pro.

  • get_engineering_context

    Returns a bounded, provenance-aware engineering ContextPacket projection using the shared memex selector.

  • get_open_problems

    Returns currently open technical problems and TODOs sorted by severity as a Markdown string.

  • get_project_context

    Returns a compressed briefing of the project as a Markdown string: active modules, recent decisions, and open problems.

  • get_recent_decisions

    Returns architectural and technical decisions from the past N days as a Markdown string.

  • get_stale_context

    Returns relationships that have decayed in confidence and may be outdated as a Markdown string.

  • get_symbol_context

    Returns detailed information about a specific function or class as a Markdown string including callers/callees.

  • guard_read

    Read a worktree file and the sha256 a guarded write must expect.

  • guard_writewrite action

    Apply file changes as one fenced commit, or refuse and change nothing.

  • invalidate_edge

    Explicitly invalidates a graph edge when it is discovered to be stale or incorrect. Returns a status string.

  • predict_impact

    Returns a ranked Markdown list of modules likely affected by changes to a file, based on graph coupling (calls + imports + decision links). No LLM call.

  • record_decisionwrite action

    Creates a Decision node in the graph. Call this when making or discovering architectural choices. Returns a status string. Phase 9: pass corroborates=<id> to reinforce, supersedes=<id> to replace, or force=true to bypass duplicate detection.

  • record_problemwrite action

    Creates a Problem node in the graph. Call this when discovering bugs or technical debt. Returns a status string.

  • resolve_problem

    Marks a Problem as closed and records the resolution. Returns a status string.

  • search_context

    Semantic + keyword + graph traversal search across all node types. Use for broad discovery. Returns a Markdown string.

Public scan report

scanner v0.1.10 · 2026-10-31 · same rubric, same numbers if you re-run it

1 high
  • Code scan2 source files scanned; 117 source files scanned13/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 qualitystatic API keys via environment variables6/15
  • Maintenancelast push 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highShell command built from a string (injection risk)exec.shell-concat
    bin/memex-mcp.js: … function isCommand(cmd) { try { execSync(`${cmd} --version`, { stdio: 'ignore' }); …
Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Memex compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
65/100
higher than 20% of 48,255 servers
Tools
15
the typical server has 7
Tools that change things
20%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
12
more than 89% of 28,688 servers
Downloads a week
489
more than 88% of 12,191 servers with a package

What its tools let an agent do: 12 read · 3 change

Release history: 3 versions in the registry since 2026-08-26, latest 2026-10-26, typically one every 43 days.

Install Memex in Claude Code, Cursor or VS Code

Runs npx -y stifler-memex-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add memex -- npx -y stifler-memex-mcp
Add to Cursor

What the publisher says

From the Memex repository's README, as published. We do not edit it. Read it on GitHub

memex — trusted engineering context for agentic software engineering

<!-- mcp-name: io.github.STiFLeR7/memex -->

A protocol-neutral engineering-context layer for AI coding agents. memex

builds a bitemporal knowledge graph of your repository — modules, symbols,

decisions, problems, evidence, and code evolution — and exposes bounded,

provenance-aware context through Hermes MemoryProvider or MCP.

A daemon and MCP server that turns commits and file changes into structured engineering knowledge. Agents can receive relevant repository context before a task, with freshness and provenance preserved, without making memex a source of personal memory or raw session state.

flowchart LR
    A[Your repository<br/>files + git] --> B[memex watcher<br/>tree-sitter + Gemini]
    B --> C[Neo4j graph<br/>bitemporal facts]
    C --> D[memex core<br/>ContextPacket selection]
    D --> E[Hermes MemoryProvider<br/>automatic read-only prefetch]
    D --> F[MCP fallback<br/>explicit lookup]
    E --> G[AI coding agent]
    F --> G

    style B fill:#cfe8ff,stroke:#0066cc,color:#000
    style C fill:#fff4cf,stroke:#cc9900,color:#000
    style E fill:#d4f5d4,stroke:#2d8f2d,color:#000

Install

Via Claude Code marketplace

/plugin marketplace add STiFLeR7/claude-plugins
/plugin install memex-mcp@stifler-marketplace

Restart your Claude Code session.

Manual

docker compose -f docker/docker-compose.yml up -d
cat > .env <<EOF
NEO4J_URI=bolt://localhost:7687
NEO4J_USER=neo4j
NEO4J_PASSWORD=memex-local
GEMINI_API_KEY=your-key-here
EOF
npx stifler-memex-mcp init --repo .
npx stifler-memex-mcp watch --repo .
npx stifler-memex-mcp serve --repo .

Hermes integration

The v0.9 Hermes integration is read-only. Hermes retains personal memory, raw session state, and execution state. memex supplies repository engineering context through a bounded ContextPacket; it does not ingest Hermes state.db, transcripts, prompts, or tool results.

Add the memex provider to Hermes' profile configuration:

memory:
  provider: memex
plugins:
  memex:
    repo_path: /absolute/path/to/repository
    prefetch_timeout_seconds: 7
    max_items: 8
    max_chars: 12000

If Hermes is not installed, use the same context selector through the MCP getengineeringcontext tool. Both paths share the protocol-neutral memex core and fail open when retrieval is unavailable.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Memex: common questions

Is Memex MCP server safe?
With care: it is graded C, so read the findings first (65/100). Read the Memex safety report
How do I install Memex?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Memex need an API key?
Yes. The registry entry asks for NEO4J_PASSWORD, GEMINI_API_KEY.
Is Memex maintained?
The last commit was 7 days ago (2026-10-28). The latest release is v1.0.3.
How does Memex compare with other MCP servers?
safety score 65/100 (higher than 20% of 48,255 servers); tools 15 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.