Elicitly Free Edition — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to MCP confirmation and form elicitation with host capability diagnostics: Can the doctor still distinguish working elicitation from advertised but auto-cancelled host support?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Local human-in-the-loop confirmations and structured form collection for agent workflows.

What we know

Local stdio MCP exposing confirmation, form and capability-doctor tools for MCP elicitation; hosted browser review belongs to a distinct Pro product.

Maintenance / activity evidence

elicitly 0.7.2 published 2026-09-07T20:03:46.775Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Can solicit user confirmations/forms through host. Writes: No external write action; downstream agent may act based on approval.
Authentication not yet verified.
Sensitive access: Potentially sensitive form answers

Low operational authority, but form responses can contain sensitive information.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Can the doctor still distinguish working elicitation from advertised but auto-cancelled host support?

The bounded review of the publisher's documented MCP confirmation and form elicitation with host capability diagnostics and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Low operational authority, but form responses can contain sensitive information.
Can solicit user confirmations/forms through host.
Package says interactions remain between MCP host and local process.
Reviewed write actions: No external write action; downstream agent may act based on approval
Sensitive access: Potentially sensitive form answers
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
host-specific support varies by client/version
Host support varies; some Claude Desktop builds do not advertise local elicitation.
Free Edition is local; remote/browser approval is Pro.
Schema is limited to MCP requestedSchema subset.
Do not collapse local Free and hosted Pro into one deployment.
Publisher lifecycle: active Free Edition
Successor/context: Hosted Pro Edition is separate

Original activity observations

elicitly 0.7.2 published 2026-09-07T20:03:46.775Z

Technical identity

npm/elicitly

Exact implementation source: https://www.npmjs.com/package/elicitly ↗
Reviewed resource type: MCP Server
Repository identity: elicitly/elicitly
Package identity: npm:elicitly

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
elicitly
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
GitHub repository ↗
elicitly/elicitly
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.
Evidence source ↗
www.elicitly.ai/docs/elicitation/support-matrix/
Source material retained for this review.
Includes references whose attribution is not established.
Evidence source ↗
www.elicitly.ai/privacy/
Source material retained for this review.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Warning

Not runtime tested, no third-party installation, network authorization, paid calls, or mutation executed.
Do not claim production service is available based on README alone.
Publisher documented stdio registration; exercises are tool-dependent
Official npm publisher package page README inspected for this exact npm identity; static research only. Some setup statements are conservatively summarized; no source code or live client execution checked. V2 review did not run any live client.
Check actual host syntax and supply credentials in secure client environment; do not paste placeholders verbatim.
Avoid write, payment, token transfer, publishing, sending, booking and remote account changes as tests.
Replace credential, action and registration placeholders; follow the matching publisher/client prerequisites. No execution performed.
Use the matching host, actual registration name and original installation environment; this does not revoke credentials.

Install / connect
Publisher instructions
Publisher documented stdio registration; exercises are tool-dependent | Publisher npm README revisited on 2026-10-14; exact identity retained.
Reviewed setup example · Claude Code only · Publisher instructions
claude mcp add elicitly -- npx -y elicitly
Configure / authenticate
MCP100 setup guide
Claude Desktop publisher .mcpb alternative; host must support elicitation for some features.
Check connection
Suggested check
Call `elicit_doctor` for host support. Do not trigger a user dialog unless intentionally testing elicitation.
Remove / uninstall / revoke
MCP100 setup guide
If registered by the publisher Claude Code example under `elicitly`, run the provided unregister command; for a different MCP client or name, delete the actual client registration. Removing a local client entry is distinct from deleting a vendor account/token.
Remove named client registration · Claude Code only · MCP100 composed guide
claude mcp remove elicitly

Official Documentation & Sources

What it does

Local stdio MCP exposing confirmation, form and capability-doctor tools for MCP elicitation; hosted browser review belongs to a distinct Pro product.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Local human-in-the-loop confirmations and structured form collection for agent workflows.

Representative uses

Request approve/cancel decisions
Collect structured form input
Probe host elicitation capability
Run live diagnostic round trips

Limitations

Host support varies; some Claude Desktop builds do not advertise local elicitation.
Free Edition is local; remote/browser approval is Pro.
Schema is limited to MCP requestedSchema subset.
Do not collapse local Free and hosted Pro into one deployment.
Publisher lifecycle: active Free Edition
Successor/context: Hosted Pro Edition is separate

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Can solicit user confirmations/forms through host.
Data handling: Package says interactions remain between MCP host and local process.
Cost: free
Risk and cautions: Low operational authority, but form responses can contain sensitive information.

Access scope and cautions

Write actions: No external write action; downstream agent may act based on approval
Sensitive access: Potentially sensitive form answers
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Request approve/cancel decisions; Collect structured form input; Probe host elicitation capability; Run live diagnostic round trips.

What setup information is documented?

Recorded installation/entrypoint step: npx -y elicitly. Recorded transport: stdio. Prerequisites: MCP host with stdio; elicitation-capable host for dialogs. Client notes: Run `elicit_doctor` before depending on dialogs. These are the documented setup details, not a claim that installation or client compatibility was independently tested.

Can it modify data or perform write operations?

Documented write actions include: No external write action; downstream agent may act based on approval. Recorded permission boundary: Can solicit user confirmations/forms through host.

What data-handling boundary should I consider?

Package says interactions remain between MCP host and local process. Recorded sensitive-access context: Potentially sensitive form answers.

What limitations and risks should I check before use?

Low operational authority, but form responses can contain sensitive information. Host support varies; some Claude Desktop builds do not advertise local elicitation. Free Edition is local; remote/browser approval is Pro. Schema is limited to MCP requestedSchema subset. Do not collapse local Free and hosted Pro into one deployment. Publisher lifecycle: active Free Edition. Successor/context: Hosted Pro Edition is separate. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.

Is this an official MCP?

Elicitly is listed as First-party MCP in MCP100’s current evidence.