Case file No.411 · npm · stdio

Askell

io.github.Neschadin/askell-mcp · v0.4.24

MCP server for the Askell payment and subscription API (Bun + stdio)

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

297 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.4.24)Oct 21, 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 Askell safe?

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

Does Askell have known CVEs or vulnerabilities?

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

When was Askell last updated?

The latest registry version is 0.4.24, published Oct 16, 2026. The last push to Neschadin/askell-mcp was on Oct 16, 2026. MCPWatch last checked it on Oct 21, 2026.

What license does Askell use?

GitHub reports the license of Neschadin/askell-mcp as MIT.

Related servers

same publisher / similar score