simple task manager for your LLM
Inferred from the transports this listing declares (streamable-http, sse). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://doing-v2-d5286fe8.alpic.live2 tools · 478mshttps://doing-v2-d5286fe8.alpic.live2 tools · 3097msdoingManage the doing task stack. Add a task, complete one, list tasks, or view the full stack with UI.Manage the doing task stack. Add a task, complete one, list tasks, or view the full stack with UI.
| Parameter | Type | Description |
|---|---|---|
| command | string | add: push a task | done: complete a task | list: view the stack (default: inferred from other args) |
| task | string | Task description — if provided without 'command', defaults to 'add' |
| index | number | 0-based index to complete (defaults to last, only for 'done') |
historyView all completed tasks in chronological order (from oldest to most recent)View all completed tasks in chronological order (from oldest to most recent)
No input schema was published for this tool.
2 of 2 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
simple task manager for your LLM
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.