Case file No.345 · npm · stdio

Elicitly

ai.elicitly/elicitly · v0.8.4

Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor

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 3 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

101 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.8.4)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 Elicitly safe?

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

Does Elicitly have known CVEs or vulnerabilities?

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

When was Elicitly last updated?

The latest registry version is 0.8.4, published Oct 13, 2026. The last push to elicitly/elicitly was on Oct 20, 2026. MCPWatch last checked it on Oct 24, 2026.

What license does Elicitly use?

GitHub reports the license of elicitly/elicitly as Apache-2.0.

Related servers

same publisher / similar score