MCP.Market

Aether Cache MCP server

by anishchugh05·io.github.anishchugh05/aether-cache·v0.1.9·3 stars

Shared local memory for AI coding tools that stays true to your code.

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

3 stars273 downloads/wk

Reviews

Write one

Nobody has reviewed Aether Cache yet.

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

Aether Cache tools (10, 1 write)

write = sends, deletes, buys or posts

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

  • check_stale

    Check whether any memory's linked files have changed since it was saved, and retire those memories. recall already does this automatically; call it directly after big changes.

  • confirm_memory

    Mark a memory as still true (e.g. after it was retired because a linked file changed, but the fact itself didn't). Re-links it to the current version of its files.

  • explain_memory

    Show where a memory came from (which tool and session saved it, which files it's linked to) and everything that has happened to it since. Use it when a memory looks wrong or surprising.

  • list_conflicts

    List pairs of memories in this project that may contradict each other and need a decision.

  • mark_outdated

    Mark a memory as no longer true, with a short reason. It stops showing up in recall but keeps its history, so you can still see what it said and why it was retired.

  • recall

    Search this project's shared memory by meaning. Call it at the start of every task, and whenever project-specific knowledge (setup, conventions, past decisions) might matter. Only current (active) memories are returned; outdated or replaced ones are skipped.

  • remember

    Save a durable fact about this project so future sessions, in any AI tool, know it. Use this, not a built-in memory or notes file, whenever the user asks you to remember something about the project.

  • replace_memory

    Retire an older memory because a newer one replaces it (e.g. "we use Postgres" replaced by "we migrated to MySQL"). The old memory stops showing up in recall but keeps its history.

  • resolve_conflict

    Settle a possible conflict. replaces_old=True: the new memory replaces the old one (the old one is retired). replaces_old=False: both are true, keep both. Ask the user if you're not sure.

  • sync_to_fileswrite action

    Write this project's current memories into the managed section of AGENTS.md / CLAUDE.md, so they're committed with the code: teammates and tools without Aether Cache see them, and changes show up in reviews. Call it when the user asks, or after a batch of new memories.

Public scan report

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

no findings
  • Code scan12 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 3 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Aether Cache compares

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

Safety score
92/100
higher than 95% of 48,255 servers
Tools
10
the typical server has 7
Tools that change things
10%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
3
more than 80% of 28,688 servers
Downloads a week
273
more than 80% of 12,191 servers with a package

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

Install Aether Cache in Claude Code, Cursor or VS Code

claude mcp add aether-cache -- uvx aether-cache
Add to Cursor

What the publisher says

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

Mnemolith

Shared memory for AI coding tools that stays true to your code.

Mnemolith (NEE-mo-lith): "memory stone." What your AI learns, carved where every tool can read it. (Why the name)

Formerly Aether Cache. If you installed aether-cache, see Moving from Aether Cache: your memories come with you.

<!-- mcp-name: io.github.anishchugh05/mnemolith -->

Website · PyPI

Claude Code, Cursor, and other AI tools each forget your project between sessions, and when they do remember things, nothing checks whether those memories are still correct. Mnemolith gives every tool one shared, local memory, and keeps it honest:

git content hash. When docker-compose.yml changes, the memory about it is retired automatically instead of being fed to your AI forever.

  • Memories go stale when the code changes. Each memory is linked to the files it's about, with a snapshot of their

next to it and confusing the model. Near-identical repeats are merged.

  • Contradictions get replaced, not hoarded. "We migrated to MySQL" retires "we use Postgres" instead of sitting

change since: created, seen again, went stale, confirmed, replaced.

  • Every memory can explain itself. Which tool and session saved it, which file versions it was based on, and every

CLAUDE.md, so they're committed, reviewed in PRs, and visible to teammates who don't run Mnemolith.

  • It works with the files you already use. Current memories sync into a managed section of AGENTS.md and

It runs entirely on your machine, on top of a database engine I wrote from scratch.

Not a Redis clone

Mnemolith started as a from-scratch rebuild of Redis in Java, then kept going. Every layer here is written from scratch, and each one does something the layer beneath it can't:

The bottom layer alone is a working Redis: redis-cli, redis-benchmark, and redis-py talk to it unchanged. The memory layer, git awareness, and MCP server are things Redis doesn't do at all.

Claude Code ─┐                       ┌─────────────────────────────────────────────┐
Cursor ──────┼─ MCP ─► mnemolith ─┼─ RESP ─► Java engine (Main.java)            │
other tools ─┘   (Python: embeddings,│          memories, HNSW vector index,       │
                  git hashing, sync) │          history, append-only file on disk  │
                                     └─────────────────────────────────────────────┘

What it looks like

The dashboard (mnemolith ui): memories whose files changed wait for a decision, with the file versions side by side.

And from your AI tool's side, a memory linked to a file, the file changes, and the next lookup catches it:

Shortened. The full README is on GitHub.

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

Aether Cache: common questions

Is Aether Cache MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Aether Cache safety report
How do I install Aether Cache?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Aether Cache need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Aether Cache maintained?
The last commit was 11 days ago (2026-10-23). The latest release is v0.1.9.
What can I use instead of Aether Cache?
Servers from other publishers that do the same job: Deja Vu MCP server, Concord MCP server and Claudexor MCP server. Compare all Aether Cache alternatives.
How does Aether Cache compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 10 (the typical server has 7); tools that change things 10% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Aether Cache

Same job from other publishers: the closest match first, then the best rated.

All Aether Cache alternatives →
  • Deja Vu
    deja-vu: local memory over the session histories of forty-three coding agents.
    A
  • Concord MCP
    Cross-harness communication and shared work-state for AI coding agents.
    A
  • Claudexor
    Route coding work across Claude Code, Codex, Cursor, and OpenCode with shared context.
    A
  • Visual Memory MCP
    Local visual UI cache for AI agents using perceptual hashing, CLIP, and 3D spatial grounding.
    A