Asana MCP — wraps the Asana REST API (OAuth)
Inferred from the transports this listing declares (streamable-http). 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.
asana_list_workspacesNo description publishedThis tool published no description. Forge does not invent one.
asana_list_tasksNo description publishedThis tool published no description. Forge does not invent one.
asana_get_taskNo description publishedThis tool published no description. Forge does not invent one.
asana_create_taskNo description publishedThis tool published no description. Forge does not invent one.
asana_list_projectsNo description publishedThis tool published no description. Forge does not invent one.
asana_search_tasksNo description publishedThis tool published no description. Forge does not invent one.
0 of 6 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.
Asana MCP — wraps the Asana REST API (OAuth)
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.