Case file No.134 · pypi · stdio

io.github.Mibayy/token-savior

io.github.Mibayy/token-savior · v4.13.0

Structural codebase MCP server with persistent memory: navigate by symbol, recall across sessions.

Package ↗GitHub ↗

Security score

93/100

Strong

Normalized over 100 points of available evidence.

Score breakdown

Known advisories40/40

0 affecting current version, 0 historical

Maintenance20/20

last push 5 days ago

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

826 weekly downloads

Known advisories

source: OSV.dev

No advisories found in OSV for this package name. (Not proof of safety.)

Metadata change timeline

rug-pull detection

First snapshot (v4.13.0)Oct 16, 2026

No changes observed yet across 1 snapshot(s).

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is io.github.Mibayy/token-savior safe?

MCPWatch gives io.github.Mibayy/token-savior a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does io.github.Mibayy/token-savior have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the pypi package token-savior-recall. That is not proof of safety.

When was io.github.Mibayy/token-savior last updated?

The latest registry version is 4.13.0, published Jul 26, 2026. The last push to Mibayy/token-savior was on Oct 15, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does io.github.Mibayy/token-savior use?

GitHub reports the license of Mibayy/token-savior as MIT.

Related servers

same publisher / similar score