Case file No.050 · npm · stdio

io.github.Looted/kibi-mcp

io.github.Looted/kibi-mcp · v3.17.0

Kibi requirements, traceability, and proof MCP. Install as a project dev dependency.

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 0 days ago

Source transparency15/15

public repo, license AGPL-3.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

746 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

v3.16.0 → v3.17.0Oct 24, 2026
- version changed version bump
```
"3.16.0" → "3.17.0"
```
- packages.0.version changed package version bump
```
"3.16.0" → "3.17.0"
```
First snapshot (v3.16.0)Oct 17, 2026

Tool lists: not published by the registry — unknown.

FAQ

auto-generated from the data above

Is io.github.Looted/kibi-mcp safe?

MCPWatch gives io.github.Looted/kibi-mcp 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.Looted/kibi-mcp have known CVEs or vulnerabilities?

No advisories were found in OSV.dev for the npm package kibi-mcp. That is not proof of safety.

When was io.github.Looted/kibi-mcp last updated?

The latest registry version is 3.17.0, published Oct 23, 2026. The last push to Looted/kibi was on Oct 24, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does io.github.Looted/kibi-mcp use?

GitHub reports the license of Looted/kibi as AGPL-3.0.

Related servers

same publisher / similar score