Case file No.086 · npm · stdio

ZapSign (unofficial)

io.github.BlancasJ/zapsign-mcp · v1.0.1

ZapSign e-signature API: reads run freely, writes ask first, personal data filtered out.

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

Source transparency15/15

public repo, license MIT

Metadata stability15/15

0 risky metadata change(s) without a version bump

Adoption3/10

486 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 (v1.0.1)Oct 24, 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 ZapSign (unofficial) safe?

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

Does ZapSign (unofficial) have known CVEs or vulnerabilities?

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

When was ZapSign (unofficial) last updated?

The latest registry version is 1.0.1, published Oct 16, 2026. The last push to BlancasJ/zapsign-mcp was on Oct 16, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does ZapSign (unofficial) use?

GitHub reports the license of BlancasJ/zapsign-mcp as MIT.

Related servers

same publisher / similar score