Case file No.248 · pypi · stdio

nable

io.github.getnable/finops-mcp · v0.12.0

Prices what your coding agents are about to do, before they do it. Plus local cloud and AI cost.

Package ↗GitHub ↗Website ↗

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

Source transparency15/15

public repo, license Apache-2.0

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

509 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 (v0.12.0)Oct 18, 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 nable safe?

MCPWatch gives nable a heuristic security score of 93/100 (strong), based on 100 points of available evidence. This is an automated heuristic, not an audit.

Does nable have known CVEs or vulnerabilities?

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

When was nable last updated?

The latest registry version is 0.12.0, published Oct 17, 2026. The last push to getnable/finopsmcp was on Oct 19, 2026. MCPWatch last checked it on Oct 20, 2026.

What license does nable use?

GitHub reports the license of getnable/finopsmcp as Apache-2.0.

Related servers

same publisher / similar score