Aether Cache
PYPI · AETHER-CACHE
Shared local memory for AI coding tools that stays true to your code.
Available components
Last scanned (9 hours ago)
Scores higher than 0% of PyPI servers
Category Memory and Knowledge
Recent critical change
CVE-2026-112398 affects this package (24 Oct 2026). See the changelog before you install this server.
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. How we score → Why this is hard to score →
Supply Chain Security74
- No malware found by supply-chain analysis.Pass
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- Dependency health was assessed across the 68 of 70 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency71
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Cryptographically verified build provenance (signed, bound to anishchugh05/Aether-Cache-Redis-Compatible-Vector-Store). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 836 tokens (~83/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 24 Oct 26 0
- CVE-2026-112398 affects this package: high ▼ critical
- 23 Oct 26 0
- CVE-2026-96639 affects this package: high ▼ critical
- 22 Oct 26 0
- CVE-2026-112393 affects this package: high ▼ critical
- CVE-2026-112900 affects this package: high ▼ critical
- GHSA-6q48-6c7w-9gw2 no longer affects this package ▲ security
- 21 Oct 26 −74
- GHSA-6q48-6c7w-9gw2 affects this package: none ▼ critical
- CVE-2026-112403 affects this package: none ▼ critical
- Known CVEs: partial → fail ▼ critical
- Score status: scored → failed ▼ critical
- 20 Oct 26 +11
- Source repository: pass → fail ▼ security
- Malware scan: unverified → pass ▲ security
- 19 Oct 26 0
- Tool safety: pass → unverified ▼ security
- 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. security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 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 functional
- 18 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 25 Oct 2026 · Analysed pypi/aether-cache@0.1.9
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | anishchugh05/Aether-Cache-Redis-Compatible-Vector-Store |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/anishchugh05/Aether-Cache-Redis-Compatible-Vector-Store/.github/workflows/release.yml@refs/tags/v0.1.9 |
| Rekor log index | 3325735716 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:63a93aaae0a22e6f284cdfbea2f7c279b139fbaf9cb590585d9707515ab69202 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 41 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22hg-r758-rrw9 | CVE-2026-112390 | high | yes | |
| GHSA-24rc-8hj2-v98c | CVE-2026-96638 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| GHSA-254f-3936-288h | CVE-2026-112391 | medium | yes | |
| GHSA-27h8-gf7j-v5hc | CVE-2026-112392 | high | yes | |
| GHSA-332p-7hrc-92wf | CVE-2026-112393 | critical | yes | |
| GHSA-3j72-p6qg-6xp7 | CVE-2026-96642 | high | yes | |
| GHSA-4558-3h8r-v8xp | CVE-2026-112394 | medium | yes | |
| GHSA-462x-pgg6-55fp | CVE-2026-112395 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:L | yes |
| GHSA-4rm8-3hmm-39fg | CVE-2026-96641 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| GHSA-4rr5-89j8-mwwm | CVE-2026-112396 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-58r4-6rv3-gfh8 | CVE-2026-112397 | high | yes | |
| GHSA-5x8w-8jj5-q52h | CVE-2026-112398 | critical | yes | |
| GHSA-5xm2-6676-qcp9 | CVE-2026-112399 | high | yes | |
| GHSA-654x-cwwv-5j9c | CVE-2026-114501 | medium | yes | |
| GHSA-65qm-jvmh-6pqg | CVE-2026-112400 | high | yes | |
| GHSA-74r2-7ff9-mjj2 | CVE-2026-112401 | medium | yes | |
| GHSA-78g4-xqwv-q3g8 | high | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:H | yes | |
| GHSA-7mwm-ghpf-9vrm | CVE-2026-112402 | high | yes | |
| GHSA-8g5g-8vmr-9782 | CVE-2026-112403 | critical | yes | |
| GHSA-9v9v-9qvf-h2hj | CVE-2026-96644 | high | yes | |
| GHSA-c6hw-5grf-ff96 | CVE-2026-112404 | high | yes | |
| GHSA-cp9v-662q-vvx9 | CVE-2026-112405 | high | yes | |
| GHSA-f2g6-542v-9j58 | CVE-2026-112406 | high | yes | |
| GHSA-fc9g-5qg7-mf45 | CVE-2026-112891 | medium | yes | |
| GHSA-g4qv-2jxx-769h | CVE-2026-96643 | high | yes | |
| GHSA-g7cr-3p24-7wf7 | CVE-2026-96778 | high | yes | |
| GHSA-g842-9rc4-69pw | CVE-2026-96637 | high | yes | |
| GHSA-gg2r-wvfm-q9rx | CVE-2026-112892 | high | yes | |
| GHSA-j4m9-6w36-pw47 | CVE-2026-112893 | high | yes | |
| GHSA-jg86-v3jv-hrpm | CVE-2026-112894 | high | yes | |
| GHSA-mrfp-p49p-3hf2 | CVE-2026-96640 | high | yes | |
| GHSA-p4wg-p73j-c528 | CVE-2026-112895 | high | yes | |
| GHSA-p8hx-v2p6-rp84 | CVE-2026-96636 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:N/I:N/A:H | yes |
| GHSA-pchr-8j38-3x4p | CVE-2026-112896 | high | yes | |
| GHSA-q45j-58j2-45rg | CVE-2026-112897 | high | yes | |
| GHSA-rfgq-q3w2-pmv2 | CVE-2026-112898 | medium | yes | |
| GHSA-v9pv-5gc8-w2m6 | CVE-2026-96639 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H | yes |
| GHSA-vx6w-vv9f-6gvg | CVE-2026-112899 | medium | yes | |
| GHSA-w889-685w-c8fh | CVE-2026-112900 | critical | yes | |
| GHSA-xgh8-jp6q-p5x8 | CVE-2026-112901 | medium | yes | |
| GHSA-xvh5-g6gv-559v | CVE-2026-112902 | high | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 68 packages
| Packages resolved | 68 |
|---|---|
| Stale | 7 |
| No linked repository | 2 |
| Tree resolution | Partial |
The dependency tree was only partially resolved, so these counts may be incomplete.
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_stale ~43
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
confirm_memory ~54
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.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
explain_memory ~55
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.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
list_conflicts ~26
List pairs of memories in this project that may contradict each other and need a decision.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
mark_outdated ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| memory_id | string | yes | – |
| reason | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
recall ~71
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
remember ~135
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.
| Name | Type | Req | Description |
|---|---|---|---|
| fact | string | yes | – |
| files | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
replace_memory ~68
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.
| Name | Type | Req | Description |
|---|---|---|---|
| new_id | string | yes | – |
| old_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
resolve_conflict ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| new_id | string | yes | – |
| old_id | string | yes | – |
| replaces_old | boolean | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
sync_to_files ~69
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.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
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.
pypi · aether-cache
claude mcp add anishchugh05-aether-cache -- uvx aether-cache
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.