# Aether Cache (pypi · aether-cache)

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

- Trust score: 0/100 (low)
- Change this week: −63
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-25

> **Recent critical change**: CVE-2026-112398 affects this package (2026-10-24). See the changelog below before you install this server.

## Components

- pypi · `aether-cache`: 0/100 (this document), [markdown](https://verifymcp.io/servers/anishchugh05-aether-cache/aether-cache.md), [page](https://verifymcp.io/servers/anishchugh05-aether-cache/aether-cache)

## Channel facts

- Registry: `pypi`
- Package: `aether-cache`
- Version: `0.1.9`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-25.

- **Supply Chain Security**: 74/100
  - No malware found by supply-chain analysis.
  - CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - Dependency health was assessed across the 68 of 70 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 71/100
  - Repository check failed: the declared repository URL redirects; it must resolve directly.
  - Cryptographically verified build provenance (signed, bound to anishchugh05/Aether-Cache-Redis-Compatible-Vector-Store).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 836 tokens (~83/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Aether Cache MCP server?

Aether Cache runs locally as a PyPI package, launched with uvx aether-cache. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add anishchugh05-aether-cache -- uvx aether-cache
```

### Cursor

```json
{
  "mcpServers": {
    "anishchugh05-aether-cache": {
      "command": "uvx",
      "args": [
        "aether-cache"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "anishchugh05-aether-cache": {
      "command": "uvx",
      "args": [
        "aether-cache"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add anishchugh05-aether-cache -- uvx aether-cache
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "anishchugh05-aether-cache": {
      "type": "local",
      "command": [
        "uvx",
        "aether-cache"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add anishchugh05-aether-cache --command uvx --arg aether-cache
```

### Hermes

```yaml
mcp_servers:
  anishchugh05-aether-cache:
    command: "uvx"
    args: ["aether-cache"]
```

### Netclaw

```json
{
  "McpServers": {
    "anishchugh05-aether-cache": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "aether-cache"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add anishchugh05-aether-cache -t stdio -c uvx -a aether-cache
```

### Other

```json
{
  "mcpServers": {
    "anishchugh05-aether-cache": {
      "command": "uvx",
      "args": [
        "aether-cache"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-24 (score 0, 0)

- [critical regression] CVE-2026-112398 affects this package: high

### 2026-10-23 (score 0, 0)

- [critical regression] CVE-2026-96639 affects this package: high

### 2026-10-22 (score 0, 0)

- [critical regression] CVE-2026-112393 affects this package: high
- [critical regression] CVE-2026-112900 affects this package: high
- [security improvement] GHSA-6q48-6c7w-9gw2 no longer affects this package

### 2026-10-21 (score 0, −74)

- [critical regression] GHSA-6q48-6c7w-9gw2 affects this package: none
- [critical regression] CVE-2026-112403 affects this package: none
- [critical regression] Known CVEs: partial → fail
- [critical regression] Score status: scored → failed

### 2026-10-20 (score 74, +11)

- [security regression] Source repository: pass → fail
- [security improvement] Malware scan: unverified → pass

### 2026-10-19 (score 63, 0)

- [security regression] Tool safety: pass → unverified
- [security improvement] Malware scan: unverified → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.7 → 0.1.9
- [functional] Package version: 0.1.7 → 0.1.8

### 2026-10-18 (score 63)

First indexed and scored.

## MCP tools (10)

### `remember` (~135 tokens)

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.

Good facts: conventions ("we use pnpm, not npm"), setup gotchas ("tests need DOCKER_HOST set"),
decisions and their reasons. Not: temporary task details or anything in the code already.
files: repo-relative paths this fact depends on (e.g. ["docker-compose.yml"]), so the memory
can be flagged when those files change.

Input parameters:

- `fact` (string, required)
- `files`

Output parameters:

- `result` (string)

### `recall` (~71 tokens)

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.

Input parameters:

- `limit` (integer)
- `query` (string, required)

Output parameters:

- `result` (string)

### `explain_memory` (~55 tokens)

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.

Input parameters:

- `memory_id` (string, required)

Output parameters:

- `result` (string)

### `mark_outdated` (~63 tokens)

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.

Input parameters:

- `memory_id` (string, required)
- `reason` (string, required)

Output parameters:

- `result` (string)

### `replace_memory` (~68 tokens)

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.

Input parameters:

- `new_id` (string, required)
- `old_id` (string, required)

Output parameters:

- `result` (string)

### `check_stale` (~43 tokens)

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.

Output parameters:

- `result` (string)

### `confirm_memory` (~54 tokens)

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.

Input parameters:

- `memory_id` (string, required)

Output parameters:

- `result` (string)

### `sync_to_files` (~69 tokens)

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.

Output parameters:

- `result` (string)

### `list_conflicts` (~26 tokens)

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

Output parameters:

- `result` (string)

### `resolve_conflict` (~77 tokens)

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.

Input parameters:

- `new_id` (string, required)
- `old_id` (string, required)
- `replaces_old` (boolean, required)

Output parameters:

- `result` (string)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/anishchugh05-aether-cache/aether-cache#diagnostics

## Score history

- 2026-10-25: 0
- 2026-10-24: 0
- 2026-10-23: 0
- 2026-10-22: 0
- 2026-10-21: 0
- 2026-10-20: 74
- 2026-10-19: 63
- 2026-10-18: 63

## Common questions

### What is the Aether Cache MCP server?

Aether Cache is an MCP server listed in the public MCP registry as io.github.anishchugh05/aether-cache. Shared local memory for AI coding tools that stays true to your code. This page covers its PyPI package (aether-cache).

### What tools does the Aether Cache MCP server expose?

Aether Cache exposes 10 tools: remember, recall, explain_memory, mark_outdated, replace_memory, and 5 more. Their descriptions and schemas cost roughly 661 tokens of context every time the server is loaded.

### Is the Aether Cache MCP server still maintained?

Aether Cache is still listed as active in the MCP registry. We last reached this channel on 25 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Aether Cache MCP server under?

Aether Cache declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/aether-cache/
- Socket report: https://socket.dev/pypi/package/aether-cache
- Website: https://anishchugh05.github.io/Aether-Cache-Redis-Compatible-Vector-Store/
- Changelog RSS feed: https://verifymcp.io/servers/anishchugh05-aether-cache/aether-cache.xml
- Changelog JSON feed: https://verifymcp.io/servers/anishchugh05-aether-cache/aether-cache.json
- HTML version of this page: https://verifymcp.io/servers/anishchugh05-aether-cache/aether-cache