Elicitly
NPM · ELICITLY
Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor
Available components
Last scanned (2 hours ago)
Scores higher than 98% of npm servers
Category Productivity and Notes
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to elicitly/elicitly). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 22 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 935 tokens (~187/item across 5 items; 4 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (75% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 −1
- Stability: pass → 0.93 functional
- 2 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 28 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/elicitly@0.8.4
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | elicitly/elicitly |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/elicitly/elicitly/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3245729724 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7b7edf4f6b5b04e5a5ea36843ab30766fb085ebedfb7cc6c5488a4ff915467b9f43573bf95d1b0ccdb8e9cef6395f22e56af1abdfdbeee34d308f6597 |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
elicit_confirm Ask the user to confirm (OK/Cancel) ~187
Ask the user an OK/Cancel confirmation via elicitation (convenience wrapper over elicit_form), modeled on JavaScript's confirm(). Use this for a single yes/no question; use elicit_form to collect arbitrary fields. Returns three-state {confirmed}: true = proceed, false = a human explicitly said no, null = no answer was obtained (reason: "dismissed" | "error") — ask again later.
| Name | Type | Req | Description |
|---|---|---|---|
| labels | object | – | Relabel or localize the OK/Cancel buttons. Each label is trimmed, 1-40 characters; unknown keys are rejected. Button placement and styling stay fixed. |
| message | string | yes | The yes/no question shown to the user in the host's elicitation dialog. |
| timeoutSeconds | number | – | How long to wait for the answer, in seconds (default 300, clamped 60-3600). |
| Name | Type | Req | Description |
|---|---|---|---|
| confirmed | boolean|null | yes | true = the user chose OK; false = an explicit no (Cancel choice or declined elicitation); null = no answer was obtained. |
| reason | string | – | Present only when confirmed is null: "dismissed" = the elicitation was closed unanswered (including timeout), "error" = it failed. |
No examples provided.
elicit_display Show the user rendered content ~363
Show information to the user as rendered HTML instead of Markdown: pass a LiquidJS template and a JSON context, and hosts that support MCP Apps render it inline in the conversation. Use it for tables, reports, and summaries the user should scan; it does not collect a decision (use elicit_confirm or elicit_form for that). Values interpolated with {{ context.* }} are HTML-escaped; truthiness is JavaScript-style. Templates may load Tailwind (https://cdn.jsdelivr.net/npm/@tailwindcss/browser@4) and DaisyUI (https://cdn.jsdelivr.net/npm/daisyui@5) with their own <script>/<link> tags; the view follows the host's light/dark theme via data-theme. External images, scripts, styles, and fonts load only from: https://cdn.jsdelivr.net — anything else is blocked. Use data: URIs for images you already have that are not publicly reachable (generated, read from a local file, or from a private source the user gave you), passed in context rather than the template (64 KB vs 32 KB). Don't download a public image just to work around the allowlist: if its origin isn't allowed, leave it out and tell the user which origin to allow. The rendered HTML is not returned to you — the result only says whether it could be shown.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | JSON data exposed to the template as `context`. Max 64 KB serialized. |
| summary | string | – | One or two sentences describing what is shown; returned as the tool's text result. |
| template | string | yes | LiquidJS template producing an HTML fragment, rendered against {{ context.* }}. Max 32768 characters. |
| title | string | – | Heading shown above the render. |
No output schema declared.
No examples provided.
elicit_doctor Diagnose the host's elicitation support ~170
Check whether the connected MCP host actually supports elicitation (and sampling/roots) before relying on it — advertising a capability is not the same as it working. Use it to decide whether to call elicit_form/elicit_confirm, to explain why a prompt did or didn't appear, or to contribute a host capability fingerprint. Returns a passive report derived from the initialize handshake; set probeElicitation: true to also run one live form round-trip (the user may see a dialog) and classify what really happened. Read-only; safe to call anytime.
| Name | Type | Req | Description |
|---|---|---|---|
| probeElicitation | boolean | – | Also fire one live form-elicitation round-trip (the user may see a dialog) and report the outcome under probes.elicitationForm. Default false: passive capability report only, no prompt. |
| Name | Type | Req | Description |
|---|---|---|---|
| deprecations | array | yes | Spec-level deprecation advisories (MCP 2026-07-28, SEP-2577) for the client features the report surfaces. |
| initialize | object | yes | The MCP initialize handshake echoed verbatim: { request: { clientInfo, capabilities }, response: { protocolVersion, capabilities, serverInfo } }. |
| probes | object | – | Present only when probeElicitation was true: the live round-trip's attempted/action/latencyMs/verdict. |
| support | object | yes | Elicitly's derived support booleans, inferred from the advertised capabilities. |
No examples provided.
elicit_form Ask the user to fill a form ~197
Trigger a form elicitation with a caller-supplied JSON schema; returns the raw {action, content}. For a plain OK/Cancel question, prefer elicit_confirm. MUST NOT be used to request secrets, credentials, or other sensitive information.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | yes | The instruction shown to the user above the form fields. |
| requestedSchema | object | yes | JSON Schema for the form, restricted to the MCP elicitation requestedSchema subset: a flat object whose properties are strings, numbers/integers, booleans, or enums — no nested objects, arrays of obj… |
| timeoutSeconds | number | – | How long to wait for the answer, in seconds (default 300, clamped 60-3600) — raise it for forms with several fields. |
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | accept = the user submitted the form; decline = an explicit no; cancel = dismissed unanswered (including timeout); error = the elicitation failed. |
| content | – | yes | On accept, the submitted values keyed by requestedSchema property name; null for every other action. |
No examples provided.
How do I install the Elicitly MCP server?
Elicitly runs locally as an npm package, launched with npx -y elicitly. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · elicitly
claude mcp add ai-elicitly-elicitly -- npx -y elicitly
What is the Elicitly MCP server?
Elicitly is an MCP server listed in the public MCP registry as ai.elicitly/elicitly. Human-in-the-loop for AI agents over MCP elicitation: confirm/form dialogs plus a capability doctor. This page covers its npm package (elicitly).
Is the Elicitly MCP server safe to use?
Elicitly scores 95 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Elicitly MCP server expose?
Elicitly exposes 4 tools: elicit_confirm, elicit_doctor, elicit_form, elicit_display. Their descriptions and schemas cost roughly 917 tokens of context every time the server is loaded.
Is the Elicitly MCP server still maintained?
Elicitly is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Elicitly MCP server under?
Elicitly declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.