Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
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.
The repository archive could not be read at scan time (tarball fetch returned 404), so no tool declarations could be extracted from it. Nothing here is a statement about what this exposes.
Read and write Mission Control state via MCP — projects, tasks, subtasks, templates, status updates.
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.