One list every AI tool you use can write to — scoped per project, local-first, self-hostable.
Inferred from the transports this listing declares (stdio). 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 out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
todo_addCapture work the moment it comes up, from any tool or project, without the ceremony of a ticket. Automatically filed under the current project — you never need to say which. Add sourceUrl when it maps to something in Notion/GitLab/Obsidian/GitHub so it can be picked back up there. Use list="backlog…Capture work the moment it comes up, from any tool or project, without the ceremony of a ticket. Automatically filed under the current project — you never need to say which. Add sourceUrl when it maps to something in Notion/GitLab/Obsidian/GitHub so it can be picked back up there. Use list="backlog…
No input schema was published for this tool.
todo_editprivilegedEdit an existing item's title/description/category/priority/dueDate/sourceUrl/list by id. Only fields you pass are changed. Pass an empty string ("") for description/category/priority/dueDate/sourceUrl to clear that field.Edit an existing item's title/description/category/priority/dueDate/sourceUrl/list by id. Only fields you pass are changed. Pass an empty string ("") for description/category/priority/dueDate/sourceUrl to clear that field.
No input schema was published for this tool.
todo_claimMark an item as actively being worked on by you (the calling agent). Advisory, not a lock — check todo_list(inProgress: true) before starting new work to avoid duplicating another agent's active item. Call todo_release or todo_complete when you stop.Mark an item as actively being worked on by you (the calling agent). Advisory, not a lock — check todo_list(inProgress: true) before starting new work to avoid duplicating another agent's active item. Call todo_release or todo_complete when you stop.
No input schema was published for this tool.
todo_releaseClear the in-progress claim on an item without completing it (e.g. you're pausing this work).Clear the in-progress claim on an item without completing it (e.g. you're pausing this work).
No input schema was published for this tool.
todo_listWhat's open here. Scoped to the current project (plus unfiled items) unless you ask otherwise, and compact by default — one line per item. Pass workspace:"*" to see every project, or verbose:true for full records.What's open here. Scoped to the current project (plus unfiled items) unless you ask otherwise, and compact by default — one line per item. Pass workspace:"*" to see every project, or verbose:true for full records.
No input schema was published for this tool.
todo_completeMark a todo as done by id.Mark a todo as done by id.
No input schema was published for this tool.
todo_historyShow the change history (create/edit/claim/release/complete) for one item, who made each change and when.Show the change history (create/edit/claim/release/complete) for one item, who made each change and when.
No input schema was published for this tool.
todo_versionReport this docket process's data format version and start time. Use to sanity-check whether your MCP connection is running stale code (e.g. right after an update) — if todo_list output looks wrong (missing/undefined fields), check this first and reconnect if the process looks old.Report this docket process's data format version and start time. Use to sanity-check whether your MCP connection is running stale code (e.g. right after an update) — if todo_list output looks wrong (missing/undefined fields), check this first and reconnect if the process looks old.
No input schema was published for this tool.
todo_check_updateCheck whether a newer version of docket is published on npm. Read-only — never installs anything. If one is available, tell the user and let THEM decide whether to run `docket update` in their own terminal (it asks for confirmation before installing).Check whether a newer version of docket is published on npm. Read-only — never installs anything. If one is available, tell the user and let THEM decide whether to run `docket update` in their own terminal (it asks for confirmation before installing).
No input schema was published for this tool.
todo_deleteprivilegedPermanently remove a todo by id.Permanently remove a todo by id.
No input schema was published for this tool.
10 of 10 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.
One list every AI tool you use can write to — scoped per project, local-first, self-hostable.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the 60-package limit. The rest of the tree was never resolved.
36 more resolved packages are not drawn here (display cap: 24). Every dependency carrying an advisory is drawn regardless of the cap. Full inventory (CycloneDX SBOM)
75 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+63 more not listed. The counts by reason above cover all of them.
Not followed: peerDependencies. This tree covers runtime dependencies only, so anything those pull in was never resolved.