@hasna/todos — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor this implementation for changes in adoption, MCP interface, maintenance and permission boundary.

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

Best fit

Manage agent task lists using CLI, MCP tools and terminal UI

What we know

Universal task management for AI coding agents - CLI + MCP server + interactive TUI Manage agent task lists using CLI, MCP tools and terminal UI.

Maintenance / activity evidence

npm downloads 155075 in 2026-09-08..2026-10-07

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

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation. Reported action classes: create tasks; update tasks; delete tasks. Complete write authority is not verified.
Local CLI and task storage
Tasks, notes and local state

Task modification and deletion are possible; do not describe as read-only.

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

Popularity

· 155.1k package downloads / 30 days

Downloads observed Oct 9, 2026.

Exact npm package @hasna/todos; provider interval 2026-09-08–2026-10-07 (inclusive); observed 2026-10-09.

All limitations / Review context

Has @hasna/todos changed its specific MCP integration, install method or privilege scope, and does it justify shortlist promotion?

High-impact permissions explicitly documented; no known blocker to an accurately caveated public Radar listing in limited first-party review.

Task modification and deletion are possible; do not describe as read-only.
Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Local CLI and task storage
Tasks, notes and local state
Reviewed write actions: create tasks; update tasks; delete tasks
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
No exhaustive advisory or runtime review performed; never infer installation safety.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
npm package downloads explicitly observed

Original activity observations

npm downloads 155075 in 2026-09-08..2026-10-07

Technical identity

npm/@hasna/todos

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

Evidence & Sources

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

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Package registry ↗
@hasna/todos
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
CLI/MCP service with distinct hosted credential resolution and local storage; inspect official command for MCP launch and storage route before configuring; no guessed launcher.
cli install · Publisher instructions
bun install -g @hasna/todos
Configure / authenticate
MCP100 setup guide
The publisher exposes a CLI and MCP integration with a separate hosted API-key route and local SQLite route. Establish the intended storage authority first (`HASNA_TODOS_LOCAL=1` for explicit local choice); hosted credential resolution may use keychain/config, not just shell env. No verified universal client launch command is included.
Check connection
Suggested check
Publisher `todos storage status --json` checks storage configuration. Then inspect MCP get_health/read-only tools as available. Do not create tasks in smoke check.
Remove / uninstall / revoke
MCP100 setup guide
Remove the actual MCP registration from the host (Claude Code example `claude mcp remove todos` only if named `todos`), stop its CLI process, and if globally installed with Bun use `bun remove -g @hasna/todos`. Preserve local SQLite and hosted task records.
MCP client unregister, stopping hosted processes, package uninstall, OAuth disconnect and token revocation are distinct actions.
A claude mcp remove command is only valid for Claude Code when the local registration actually has that name. Other MCP hosts require their own UI/config cleanup.
Separate credential guidance / limitations: @hasna/todos has credential-source precedence across env, Keychain and ~/.hasna/todos/config/credentials; removing a local credential or updating it is not server-side revocation. Official package README does not establish a fleet-server API token revoke step.
Package / application cleanup · matching installation environment · MCP100 composed guide
bun remove -g @hasna/todos

Official Documentation & Sources

What it does

Universal task management for AI coding agents - CLI + MCP server + interactive TUI Manage agent task lists using CLI, MCP tools and terminal UI.

Capability: Productivity & Collaboration
Resource type: MCP Server
Best fit: Manage agent task lists using CLI, MCP tools and terminal UI

Representative uses

Create and update agent task lists
Track completed and pending project tasks
Use CLI or MCP integration for task workflows
Manage agent task lists using CLI, MCP tools and terminal UI

Limitations

Task modification and deletion are possible; do not describe as read-only.
Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation.
npm package downloads explicitly observed

Reviewed access

Access & risk

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

Authentication: Local CLI and task storage
Permissions: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.
Data handling: Tasks, notes and local state
Cost: may incur external API or infrastructure charges; unverified
Risk and cautions: Task modification and deletion are possible; do not describe as read-only.

Access scope and cautions

Write actions: Not verified create tasks update tasks delete tasks
Risk level: moderate
Security notes: Task modification and deletion are possible; do not describe as read-only.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

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

Which tasks are documented for this implementation?

The reviewed tasks include: Create and update agent task lists; Track completed and pending project tasks; Use CLI or MCP integration for task workflows; Manage agent task lists using CLI, MCP tools and terminal UI.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Command provided only where first-party command or package existence is established; verify the client configuration against upstream documentation. This is a diagnostic CLI invocation, not an MCP client installation/configuration recipe. Installation/authentication detail is incomplete; do not infer settings from package name. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Local CLI and task storage

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: create tasks; update tasks; delete tasks. Recorded permission context: Scoped by connected account, local OS, and configuration; verify exact permissions before installation.

What data-handling boundary should I consider?

Tasks, notes and local state

What limitations and risks should I check before use?

Task modification and deletion are possible; do not describe as read-only. Setup and runtime permissions are implementation- and account-specific; follow linked upstream documentation. npm package downloads explicitly observed. No exhaustive advisory or runtime review performed; never infer installation safety.