Add items to your tidee workspace from ordinary language, read what is there, and mark things done.
Inferred from the transports this listing declares (stdio, streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
TIDEE_API_TOKENAPI keyrequiredA tidee personal access token, created in the app under Application Settings, Integrations. Only needed for this local package — the hosted server above authenticates with OAuth and needs no token.
Declared by the author in the official MCP registry. Forge does not store, broker, or ever see these values — the config below is scaffolded with placeholders you fill in locally.
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.
captureNo description publishedThis tool published no description. Forge does not invent one.
create_itemNo description publishedThis tool published no description. Forge does not invent one.
list_boxesThe user’s boxes — the containers items are filed in. Call this when you need a box id for capture or create_item, or when the user asks what they have.The user’s boxes — the containers items are filed in. Call this when you need a box id for capture or create_item, or when the user asks what they have.
No input schema was published for this tool.
list_itemsRead items from the workspace. Narrow with q to search titles, or parentId to look inside one box. Use this before completing something, to find the item’s id.Read items from the workspace. Narrow with q to search titles, or parentId to look inside one box. Use this before completing something, to find the item’s id.
No input schema was published for this tool.
complete_itemMark an item done. Needs the item’s id, which comes from list_items — find the item first rather than guessing an id.Mark an item done. Needs the item’s id, which comes from list_items — find the item first rather than guessing an id.
No input schema was published for this tool.
3 of 5 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.
Add items to your tidee workspace from ordinary language, read what is there, and mark things done.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
The crawl stopped at the depth-4 limit. Anything below that level was never resolved.
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)
54 declared dependencies never landed in the tree. They are missing from Forge's resolution, not from the package.
+42 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.