todoglow
NPM · TODOGLOW-MCP · SCANNED OCT 2
See what each of your coding agents is working on, and read or advance your todos.
Available components
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
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 51 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability77
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 778 tokens (~97/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 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
How do I install the todoglow MCP server?
todoglow runs locally as an npm package, launched with npx -y todoglow-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · todoglow-mcp
claude mcp add app-devglow-todoglow -- npx -y todoglow-mcp
{
"mcpServers": {
"app-devglow-todoglow": {
"command": "npx",
"args": [
"-y",
"todoglow-mcp"
]
}
}
} {
"servers": {
"app-devglow-todoglow": {
"command": "npx",
"args": [
"-y",
"todoglow-mcp"
]
}
}
} codex mcp add app-devglow-todoglow -- npx -y todoglow-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"app-devglow-todoglow": {
"type": "local",
"command": [
"npx",
"-y",
"todoglow-mcp"
],
"enabled": true
}
}
} openclaw mcp add app-devglow-todoglow --command npx --arg -y --arg todoglow-mcp
mcp_servers:
app-devglow-todoglow:
command: "npx"
args: ["-y", "todoglow-mcp"] {
"McpServers": {
"app-devglow-todoglow": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"todoglow-mcp"
]
}
}
} assistant mcp add app-devglow-todoglow -t stdio -c npx -a -y todoglow-mcp
{
"mcpServers": {
"app-devglow-todoglow": {
"command": "npx",
"args": [
"-y",
"todoglow-mcp"
]
}
}
} 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.
- 2 Oct 26 −3
- Stability: pass → 0.77 functional
- 1 Oct 26 0
- Stability: 0.97 → pass security
- 30 Sept 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.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 −3
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 0
- Stability: 0.97 → pass security
- 23 Sept 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.
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 2 Oct 2026 · Analysed npm/todoglow-mcp@1.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| 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 →
advance_todo Advance Todo Status ~44
Advance a todo's status: pending → in_progress → completed. Use this when a todo is started or finished.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | The todo ID to advance |
No output schema declared.
No examples provided.
get_active_todo Get Active Todo ~30
Get the currently active (in_progress) todo — the one the user is focused on right now.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_threads Get Agent Threads ~25
List all agent threads in todoglow. Shows background work status from AI agents.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_receipt_todos List Receipt Todos ~127
List completed todos for a month as they appear in todoglow's receipt view, with their current receipt display title. Use this before set_receipt_titles to see what needs a public title. In the receipt's privacy mode, a todo is shown in the clear ONLY if it has a display title; everything else is masked.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | Month to list, as YYYY-MM (e.g. 2026-07). |
| only | string | – | Filter: 'masked' = no display title yet, 'public' = has one. Default all. |
No output schema declared.
No examples provided.
list_todos List Todos ~45
List all active todos in todoglow. Returns id, text, status, and timing info.
| Name | Type | Req | Description |
|---|---|---|---|
| status | string | – | Filter by status. Omit to list all. |
No output schema declared.
No examples provided.
set_receipt_titles Set Receipt Titles ~101
Set the receipt display title for one or more todos, in a single batch. A todo with a display title is shown in the clear when the receipt's privacy mode is on; everything else is masked. Pass title: null to clear one (back to masked). Only give a title to todos the user is willing to publish in a screenshot — when in doubt, leave it masked.
| Name | Type | Req | Description |
|---|---|---|---|
| entries | array | yes | Batch of id/title pairs to apply. |
No output schema declared.
No examples provided.
set_topic Set Work Topic ~132
Add a todo to the user's todoglow app. Only use this when the user explicitly asks to add a todo (e.g. 'todo 추가해줘', 'add this to my todos'). Do NOT call this automatically at conversation start — use update_thread instead. If called again in the same session with a pending todo, it will UPDATE the text instead of creating a new one.
| Name | Type | Req | Description |
|---|---|---|---|
| source | string | – | Source identifier (e.g. "claude", "cursor"). Defaults to "mcp" |
| text | string | yes | The overarching topic or goal (max 200 chars). Keep it concise. |
No output schema declared.
No examples provided.
update_thread Update Agent Thread ~101
Register and update your work status in todoglow's AGENTS section. Call this at the START of every conversation with status 'working' and a short task description. Update status as work progresses (working → done/failed). Creates a new thread or updates an existing one by name.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Thread name (e.g. task description). Used to find or create the thread. |
| status | string | yes | Current status of the thread |
No output schema declared.
No examples provided.
What is the todoglow MCP server?
todoglow is an MCP server listed in the public MCP registry as app.devglow/todoglow. See what each of your coding agents is working on, and read or advance your todos. This page covers its npm package (todoglow-mcp).
Is the todoglow MCP server safe to use?
todoglow scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 2 October 2026. It declares no install or post-install scripts. 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 todoglow MCP server expose?
todoglow exposes 8 tools: set_topic, list_todos, list_receipt_todos, set_receipt_titles, get_active_todo, and 3 more. Their descriptions and schemas cost roughly 605 tokens of context every time the server is loaded.
Is the todoglow MCP server still maintained?
todoglow is still listed as active in the MCP registry. We last reached this channel on 2 October 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 todoglow MCP server under?
todoglow declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.