How does memex handle temporal aspects of code changes?

Every edge in the knowledge graph has creation and optional expiration timestamps, enabling bitemporal queries and confidence decay over time.

Which AI agents are compatible with memex?

Memex supports Claude Code, Cursor, Codex, Gemini CLI, and any other MCP-compatible AI coding agents.

How do I install and run memex?

You can install via npx, pip, or Docker; then initialize, watch your repo, and serve the MCP server using provided CLI commands.

Does memex support multi-user or team deployments?

Yes, it supports shared team setups with a single Neo4j instance and memex server, with authentication enabled by default.

Memex

Q: What data does memex extract from my repository?

It extracts modules, symbols, architectural decisions, open problems, and lockfile facts from every commit and file change.

Provides a bitemporal knowledge graph of git repo modules, symbols, decisions, and problems for AI coding agents via MCP.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "stifler7-memex": {
      "command": "npx",
      "args": [
        "-y",
        "stifler-memex-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

This server continuously monitors git repositories to build a temporal knowledge graph capturing modules, symbols, architectural decisions, and open problems. It stores this structured data in Neo4j with bitemporal validity windows and confidence scores that decay over time. The server exposes 14 MCP tools for AI coding agents to read and write knowledge, enabling persistent context across sessions and preventing redundant rediscovery of codebase facts. It supports integrations with agents like Claude Code, Cursor, Codex, and Gemini CLI.

Use cases

Maintain persistent codebase context for AI coding agents across sessions

Query recent architectural decisions and open problems in a repository

Retrieve symbol-level call graphs and linked decisions before editing

Record new decisions or problems discovered during AI-assisted coding

Analyze repository structure and confidence decay of knowledge over time

Key features

Bitemporal knowledge graph with created_at and expired_at timestamps

Confidence scores on edges that decay with a two-regime half-life

14 MCP tools including read, write, and analytic operations

Integration with multiple AI coding agents via MCP over stdio or HTTP

Automated extraction from git commits using tree-sitter and Gemini Flash

Support for team deployments with authentication and access control

Capabilities & Tool Schemas (12)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Memex.

get_project_context

Session start. Returns a cluster-level briefing under 1500 tokens regardless of repo size

get_symbol_context

Before editing a function or class. Returns callers, callees, linked decisions

get_recent_decisions

Last N days of architectural decisions, optionally module-scoped

get_open_problems

Active bugs and tech debt, sorted by severity

search_context

Hybrid search: semantic × keyword × graph traversal × RRF merge

get_stale_context

Edges whose composite confidence dropped below threshold

Documentation Overview

memex — trusted engineering context for agentic software engineering

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.

memex — temporal knowledge graph MCP server for AI coding agents, built on Graphiti and Neo4j

mermaid

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

Code

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

Restart your Claude Code session.

Manual

Terminal

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:

yaml

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 get_engineering_context tool. Both paths share the protocol-neutral memex core and fail open when retrieval is unavailable.

Channel	Command
Claude Code marketplace	`/plugin install memex-mcp@stifler-marketplace`
npx (no install)	`npx stifler-memex-mcp <cmd>`
uv	`uv add memex-mcp`
pip	`pip install memex-mcp`
source	`git clone github.com/STiFLeR7/memex && uv sync`

Self-hosted team deployment

For a shared team setup (one Neo4j + one memex-server, auth on by default, Neo4j's ports never exposed to the host):

bash

bash docker/bootstrap-team-env.sh
docker compose -f docker/docker-compose.team.yml up -d

See docker/TEAM-DEPLOY.md for the full flow, capturing the initial admin key, and the down -v footgun to avoid.

At a glance

Property	Value
Output	A Neo4j graph populated continuously from your repo
Storage	Neo4j via Graphiti. Bitemporal — every edge has `created_at` and optional `expired_at`
Context	Bounded, ranked, provenance-aware `ContextPacket`
Integrations	Hermes MemoryProvider, MCP resources/tools, Claude Code, Cursor, Codex, Gemini CLI
Failure mode	Fail-open; agent execution continues without memex
Granularity	Scales from 50 to 5000+ modules via hierarchical Leiden clusters
Synthesis	Gemini Flash distills commits into `Decision` nodes; Pro for grounded synthesis
Confidence	Computed at query time. Two-regime decay (validated half-life ~139d, unvalidated stale at 30d)
Write governance	Per-node-type ACL, intent-confirmation on agent writes, explicit `corroborates` / `supersedes` semantics
Goal 10 evidence	8/8 valid paired runs, 0 treatment failures, 0 treatment regressions

The lifecycle

mermaid

flowchart TD
    Init[memex init<br/>extract baseline] --> Watch[memex watch<br/>daemon + git hooks]
    Watch -->|commit| Extract[tree-sitter extract<br/>symbols, imports, lockfile]
    Extract --> Synth[Gemini Flash<br/>diff → Decision nodes]
    Synth --> Write[Graphiti add_episode<br/>+ post-hoc bitemporal SET]
    Write --> Decay[Scheduler<br/>nightly confidence decay]
    Decay -->|stale edges| Archive[expired_at = now]

    Serve[memex serve<br/>MCP stdio/HTTP] -.->|reads| Write
    Agent[AI agent] -->|14 MCP tools| Serve
    Serve -->|record_decision / record_problem| Write

    Cluster[memex cluster<br/>Leiden over hybrid edges] -.->|every N commits| Write

    style Init fill:#e8f4ff,color:#000
    style Watch fill:#fff4cf,color:#000
    style Synth fill:#ffe0cc,color:#000
    style Serve fill:#d4f5d4,color:#000

MCP tools

14 tools — eight read, four write, two analytic.

Read

Tool	When
`get_project_context`	Session start. Returns a cluster-level briefing under 1500 tokens regardless of repo size
`get_symbol_context`	Before editing a function or class. Returns callers, callees, linked decisions
`get_recent_decisions`	Last N days of architectural decisions, optionally module-scoped
`get_open_problems`	Active bugs and tech debt, sorted by severity
`search_context`	Hybrid search: semantic × keyword × graph traversal × RRF merge
`get_stale_context`	Edges whose composite confidence dropped below threshold
`explain_change`	Given a commit SHA, cross-references the diff with linked Decision/Problem nodes and asks Gemini Pro for a grounded explanation
`predict_impact`	Given a file path, returns a ranked list of modules likely affected based on graph coupling (no LLM call)

Write

Tool	When
`record_decision`	After making a technical choice. Supports `corroborates` (reinforce) and `supersedes` (replace)
`record_problem`	When discovering a bug or piece of tech debt
`resolve_problem`	When a tracked problem is fixed
`invalidate_edge`	When a stored fact is no longer true

Bitemporal confidence

Confidence is not a stored number that mutates. It is computed at query time from base_confidence, validation status, time since last reinforcement, and access count.

mermaid

flowchart LR
    Edge[Edge created<br/>base_confidence] --> Q{Validated by<br/>a human?}
    Q -->|yes| Slow[Slow regime<br/>half-life ~139d]
    Q -->|no| Fast[Fast regime<br/>stale at exactly 30d]
    Slow --> Score[Composite score<br/>conf × recency × rehearsal]
    Fast --> Score
    Score -->|below floor| Stale[get_stale_context surfaces it]
    Score -->|access| Bump[last_reinforced_at updated]
    Bump --> Score

    style Slow fill:#d4f5d4,color:#000
    style Fast fill:#ffd4d4,color:#000

Property	Value
Validated half-life	~139 days
Unvalidated stale threshold	30 days (composite < 0.3)
Recency τ	90 days (exponential decay)
Composite formula	`conf × recency × (1 + rehearsal_w × log(1 + access_count))`
Conflict similarity threshold	0.4 (below this + overlapping validity = conflict)
Intent-confirmation threshold	0.85 (MCP write similarity check)

Hierarchical clusters

memex cluster runs hierarchical Leiden over a hybrid edge graph:

Edge type	Weight
Directory co-location	1.0
Module imports	2.0
Symbol calls	`log(1 + calls)`

Property	Value
Algorithm	`graspologic.partition.hierarchical_leiden` with fixed seed
Naming	TF-IDF top-3 over module docstrings + symbol names, parent-dir fallback
ID pinning	Jaccard ≥ 0.5 across reruns (cluster names stay stable through renames)
User overrides	`.memex/clusters.yaml` — any assignment can be locked
Context budget	`get_project_context` stays under 1500 tokens whether your repo has 50 or 5000 modules

Measure Your Savings

memex tracks token reduction metrics and human review actions locally in a SQLite database (~/.config/memex/telemetry.db).

You can query your savings at any time using the CLI:

bash

memex stats

Or view the raw JSON payload:

bash

memex stats --json

Read the full README →View source on GitHub →

Related MCP Servers

View all in Knowledge & Memory View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

4d ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Memex

It extracts modules, symbols, architectural decisions, open problems, and lockfile facts from every commit and file change.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/stifler7-memex?style=directory)](https://allmcps.com/mcp/stifler7-memex)

HTML Embed

<a href="https://allmcps.com/mcp/stifler7-memex"><img src="https://allmcps.com/api/badge/stifler7-memex?style=directory" alt="Memex on AllMCPs" /></a>

Technical Specs & Signals

CategoryKnowledge & Memory

9/10 checks healthy over the last 31d

59Quality signal: Good · 59/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools28/30

Adoption & activity6/15

Community engagement0/10

A guidance signal from public completeness & health data — not a user rating. New listings start lower and rise as they add docs, get verified, and grow adoption. Signals we can't observe for a listing are skipped, not counted against it.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · stifler-memex-mcp (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

This directory is pre-filled from public sources. Claim via GitHub README, site badge, or DNS TXT to unlock edit access and the Official badge — proof is checked automatically, then reviewed by our team.

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🧠 Knowledge & Memory →Best MCP servers for Memory & Knowledge →Alternatives to Memex →Install in Claude Desktop Install in Cursor Install in VS Code

Memex

Provides a bitemporal knowledge graph of git repo modules, symbols, decisions, and problems for AI coding agents via MCP.

Quick Install

Automated & IDE Setup

Copy the AI prompt to install this server into Claude Code, Cursor, or another agent — or use 1-click editor setup below.

Add to Cursor Add to VS Code

Not yet automatically verified

We haven't yet run this listing's install command through our automated sandbox check. This isn't a red flag — we're steadily working through the catalog.

Manual Client & Custom JSON ConfigExpand JSON ▾

Client Config & Setup

Choose your client or environment

Target File:~/Library/Application Support/Claude/claude_desktop_config.json

claude_desktop_config.json

{
  "mcpServers": {
    "stifler7-memex": {
      "command": "npx",
      "args": [
        "-y",
        "stifler-memex-mcp"
      ]
    }
  }
}

💡 Paste the JSON block into your client's configuration file under mcpServers, then restart the application.

Overview

Use cases

Maintain persistent codebase context for AI coding agents across sessions

Query recent architectural decisions and open problems in a repository

Retrieve symbol-level call graphs and linked decisions before editing

Record new decisions or problems discovered during AI-assisted coding

Analyze repository structure and confidence decay of knowledge over time

Key features

Bitemporal knowledge graph with created_at and expired_at timestamps

Confidence scores on edges that decay with a two-regime half-life

14 MCP tools including read, write, and analytic operations

Integration with multiple AI coding agents via MCP over stdio or HTTP

Automated extraction from git commits using tree-sitter and Gemini Flash

Support for team deployments with authentication and access control

Capabilities & Tool Schemas (12)Self-reported

Inspect callable tools, capabilities, and parameters exposed to AI agents by Memex.

get_project_context

Session start. Returns a cluster-level briefing under 1500 tokens regardless of repo size

get_symbol_context

Before editing a function or class. Returns callers, callees, linked decisions

get_recent_decisions

Last N days of architectural decisions, optionally module-scoped

get_open_problems

Active bugs and tech debt, sorted by severity

search_context

Hybrid search: semantic × keyword × graph traversal × RRF merge

get_stale_context

Edges whose composite confidence dropped below threshold

Documentation Overview

memex — trusted engineering context for agentic software engineering

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.

memex — temporal knowledge graph MCP server for AI coding agents, built on Graphiti and Neo4j

mermaid

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

Code

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

Restart your Claude Code session.

Manual

Terminal

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

Add the memex provider to Hermes' profile configuration:

yaml

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 get_engineering_context tool. Both paths share the protocol-neutral memex core and fail open when retrieval is unavailable.

Channel	Command
Claude Code marketplace	`/plugin install memex-mcp@stifler-marketplace`
npx (no install)	`npx stifler-memex-mcp <cmd>`
uv	`uv add memex-mcp`
pip	`pip install memex-mcp`
source	`git clone github.com/STiFLeR7/memex && uv sync`

Self-hosted team deployment

For a shared team setup (one Neo4j + one memex-server, auth on by default, Neo4j's ports never exposed to the host):

bash

bash docker/bootstrap-team-env.sh
docker compose -f docker/docker-compose.team.yml up -d

See docker/TEAM-DEPLOY.md for the full flow, capturing the initial admin key, and the down -v footgun to avoid.

At a glance

Property	Value
Output	A Neo4j graph populated continuously from your repo
Storage	Neo4j via Graphiti. Bitemporal — every edge has `created_at` and optional `expired_at`
Context	Bounded, ranked, provenance-aware `ContextPacket`
Integrations	Hermes MemoryProvider, MCP resources/tools, Claude Code, Cursor, Codex, Gemini CLI
Failure mode	Fail-open; agent execution continues without memex
Granularity	Scales from 50 to 5000+ modules via hierarchical Leiden clusters
Synthesis	Gemini Flash distills commits into `Decision` nodes; Pro for grounded synthesis
Confidence	Computed at query time. Two-regime decay (validated half-life ~139d, unvalidated stale at 30d)
Write governance	Per-node-type ACL, intent-confirmation on agent writes, explicit `corroborates` / `supersedes` semantics
Goal 10 evidence	8/8 valid paired runs, 0 treatment failures, 0 treatment regressions

The lifecycle

mermaid

flowchart TD
    Init[memex init<br/>extract baseline] --> Watch[memex watch<br/>daemon + git hooks]
    Watch -->|commit| Extract[tree-sitter extract<br/>symbols, imports, lockfile]
    Extract --> Synth[Gemini Flash<br/>diff → Decision nodes]
    Synth --> Write[Graphiti add_episode<br/>+ post-hoc bitemporal SET]
    Write --> Decay[Scheduler<br/>nightly confidence decay]
    Decay -->|stale edges| Archive[expired_at = now]

    Serve[memex serve<br/>MCP stdio/HTTP] -.->|reads| Write
    Agent[AI agent] -->|14 MCP tools| Serve
    Serve -->|record_decision / record_problem| Write

    Cluster[memex cluster<br/>Leiden over hybrid edges] -.->|every N commits| Write

    style Init fill:#e8f4ff,color:#000
    style Watch fill:#fff4cf,color:#000
    style Synth fill:#ffe0cc,color:#000
    style Serve fill:#d4f5d4,color:#000

MCP tools

14 tools — eight read, four write, two analytic.

Read

Tool	When
`get_project_context`	Session start. Returns a cluster-level briefing under 1500 tokens regardless of repo size
`get_symbol_context`	Before editing a function or class. Returns callers, callees, linked decisions
`get_recent_decisions`	Last N days of architectural decisions, optionally module-scoped
`get_open_problems`	Active bugs and tech debt, sorted by severity
`search_context`	Hybrid search: semantic × keyword × graph traversal × RRF merge
`get_stale_context`	Edges whose composite confidence dropped below threshold
`explain_change`	Given a commit SHA, cross-references the diff with linked Decision/Problem nodes and asks Gemini Pro for a grounded explanation
`predict_impact`	Given a file path, returns a ranked list of modules likely affected based on graph coupling (no LLM call)

Write

Tool	When
`record_decision`	After making a technical choice. Supports `corroborates` (reinforce) and `supersedes` (replace)
`record_problem`	When discovering a bug or piece of tech debt
`resolve_problem`	When a tracked problem is fixed
`invalidate_edge`	When a stored fact is no longer true

Bitemporal confidence

Confidence is not a stored number that mutates. It is computed at query time from base_confidence, validation status, time since last reinforcement, and access count.

mermaid

flowchart LR
    Edge[Edge created<br/>base_confidence] --> Q{Validated by<br/>a human?}
    Q -->|yes| Slow[Slow regime<br/>half-life ~139d]
    Q -->|no| Fast[Fast regime<br/>stale at exactly 30d]
    Slow --> Score[Composite score<br/>conf × recency × rehearsal]
    Fast --> Score
    Score -->|below floor| Stale[get_stale_context surfaces it]
    Score -->|access| Bump[last_reinforced_at updated]
    Bump --> Score

    style Slow fill:#d4f5d4,color:#000
    style Fast fill:#ffd4d4,color:#000

Property	Value
Validated half-life	~139 days
Unvalidated stale threshold	30 days (composite < 0.3)
Recency τ	90 days (exponential decay)
Composite formula	`conf × recency × (1 + rehearsal_w × log(1 + access_count))`
Conflict similarity threshold	0.4 (below this + overlapping validity = conflict)
Intent-confirmation threshold	0.85 (MCP write similarity check)

Hierarchical clusters

memex cluster runs hierarchical Leiden over a hybrid edge graph:

Edge type	Weight
Directory co-location	1.0
Module imports	2.0
Symbol calls	`log(1 + calls)`

Property	Value
Algorithm	`graspologic.partition.hierarchical_leiden` with fixed seed
Naming	TF-IDF top-3 over module docstrings + symbol names, parent-dir fallback
ID pinning	Jaccard ≥ 0.5 across reruns (cluster names stay stable through renames)
User overrides	`.memex/clusters.yaml` — any assignment can be locked
Context budget	`get_project_context` stays under 1500 tokens whether your repo has 50 or 5000 modules

Measure Your Savings

memex tracks token reduction metrics and human review actions locally in a SQLite database (~/.config/memex/telemetry.db).

You can query your savings at any time using the CLI:

bash

memex stats

Or view the raw JSON payload:

bash

memex stats --json

Read the full README →View source on GitHub →

Related MCP Servers

View all in Knowledge & Memory View all alternatives

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

GitHub stars

Stargazers on the source repository.

Last commit

4d ago

Most recent push to the default branch.

Tools exposed

Callable tools this server registers over MCP.

Directory activity

1 views

Config copies, upvotes, and views on AllMCPs.

Reviews

No reviews yet — be the first to share how this listing worked for you.

Frequently Asked Questions about Memex

It extracts modules, symbols, architectural decisions, open problems, and lockfile facts from every commit and file change.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:

Live Dynamic SVG Preview

Markdown (GitHub README)

[![AllMCPs](https://allmcps.com/api/badge/stifler7-memex?style=directory)](https://allmcps.com/mcp/stifler7-memex)

HTML Embed

<a href="https://allmcps.com/mcp/stifler7-memex"><img src="https://allmcps.com/api/badge/stifler7-memex?style=directory" alt="Memex on AllMCPs" /></a>

Technical Specs & Signals

CategoryKnowledge & Memory

9/10 checks healthy over the last 31d

59Quality signal: Good · 59/100How this signal is calculated ▾

Server availabilityNot measured

Not scored for repo-hosted servers — we can't reach the running server, only its GitHub page. Hosted MCP endpoints are health-checked live.

Verified ownership10/20

Documentation & tools28/30

Adoption & activity6/15

Community engagement0/10

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 13d ago via OSV.dev · stifler-memex-mcp (npm)

★ Spotlight Slot

Feature Your MCP Server

Get maximum visibility for your server across our directory, search results, and detail pages.

Spotlight Your Server

Own this project?

Free dofollow backlink: add your website and place the AllMCPs badge on it — no claim needed. We detect it automatically and keep it verified as long as the badge stays live.

Claim & get free dofollow

Share & Embed

Add our SVG badge (dark/light directory styles) or embeddable widget to your site.

Explore more

More in 🧠 Knowledge & Memory →Best MCP servers for Memory & Knowledge →Alternatives to Memex →Install in Claude Desktop Install in Cursor Install in VS Code