Cyber Asana MCP Server

cyber-asana npm v0.12.0 Source verified

Published by cyberuni — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Asana CLI and MCP server for AI agents

Trust grade
A
94/100
Last scanned get badge →
Trust
A · 94/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
High
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 94/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 6 = 94. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−6 capability blast radius (high) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 1

high Shell/command execution in server code (dist/composition-CpJAlqfK.js)MTC-SRC-002

In the server's implementation (`dist/composition-CpJAlqfK.js:1141`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: } = await import("node:child_process"); spawn(process.platform === "darwin" ? "open" : process.platform === "win32" ?

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/composition-CpJAlqfK.js

Tools 99

Each tool and what it can reach — statically extracted from the published source.

  • asana_attachment_createno sensitive capability
  • asana_attachment_deleteno sensitive capability
  • asana_attachment_getno sensitive capability
  • asana_attachment_listno sensitive capability
  • asana_custom_field_getno sensitive capability
  • asana_custom_field_listno sensitive capability
  • asana_custom_field_list_for_goalno sensitive capability
  • asana_custom_field_list_for_portfoliono sensitive capability
  • asana_custom_field_list_for_projectno sensitive capability
  • asana_custom_field_list_for_teamno sensitive capability
Show 89 more tools ↓
  • asana_event_listno sensitive capability
  • asana_goal_createno sensitive capability
  • asana_goal_deleteno sensitive capability
  • asana_goal_getno sensitive capability
  • asana_goal_listno sensitive capability
  • asana_goal_updateno sensitive capability
  • asana_job_getno sensitive capability
  • asana_membership_createno sensitive capability
  • asana_membership_deleteno sensitive capability
  • asana_membership_getno sensitive capability
  • asana_membership_listno sensitive capability
  • asana_membership_updateno sensitive capability
  • asana_ooo_createno sensitive capability
  • asana_ooo_deleteno sensitive capability
  • asana_ooo_getno sensitive capability
  • asana_ooo_listno sensitive capability
  • asana_ooo_updateno sensitive capability
  • asana_portfolio_createno sensitive capability
  • asana_portfolio_deleteno sensitive capability
  • asana_portfolio_getno sensitive capability
  • asana_portfolio_item_listno sensitive capability
  • asana_portfolio_listno sensitive capability
  • asana_portfolio_updateno sensitive capability
  • asana_project_countsno sensitive capability
  • asana_project_createno sensitive capability
  • asana_project_deleteno sensitive capability
  • asana_project_exportno sensitive capability
  • asana_project_getno sensitive capability
  • asana_project_listno sensitive capability
  • asana_project_searchno sensitive capability
  • asana_project_template_getno sensitive capability
  • asana_project_template_instantiateno sensitive capability
  • asana_project_template_listno sensitive capability
  • asana_project_updateno sensitive capability
  • asana_rule_triggerno sensitive capability
  • asana_search_objectsno sensitive capability
  • asana_section_createno sensitive capability
  • asana_section_deleteno sensitive capability
  • asana_section_getno sensitive capability
  • asana_section_listno sensitive capability
  • asana_section_moveno sensitive capability
  • asana_section_task_addno sensitive capability
  • asana_section_updateno sensitive capability
  • asana_status_createno sensitive capability
  • asana_status_deleteno sensitive capability
  • asana_status_getno sensitive capability
  • asana_status_listno sensitive capability
  • asana_status_overviewno sensitive capability
  • asana_tag_add_to_taskno sensitive capability
  • asana_tag_createno sensitive capability
  • asana_tag_deleteno sensitive capability
  • asana_tag_getno sensitive capability
  • asana_tag_listno sensitive capability
  • asana_tag_list_for_taskno sensitive capability
  • asana_tag_list_tasksno sensitive capability
  • asana_tag_remove_from_taskno sensitive capability
  • asana_tag_updateno sensitive capability
  • asana_task_createno sensitive capability
  • asana_task_deleteno sensitive capability
  • asana_task_dependency_addno sensitive capability
  • asana_task_dependency_listno sensitive capability
  • asana_task_dependency_removeno sensitive capability
  • asana_task_dependent_addno sensitive capability
  • asana_task_dependent_listno sensitive capability
  • asana_task_dependent_removeno sensitive capability
  • asana_task_follower_addno sensitive capability
  • asana_task_follower_removeno sensitive capability
  • asana_task_getno sensitive capability
  • asana_task_get_manyno sensitive capability
  • asana_task_listno sensitive capability
  • asana_task_my_tasksno sensitive capability
  • asana_task_project_addno sensitive capability
  • asana_task_project_removeno sensitive capability
  • asana_task_scan_todosno sensitive capability
  • asana_task_searchno sensitive capability
  • asana_task_subtask_createno sensitive capability
  • asana_task_subtask_listno sensitive capability
  • asana_task_template_getno sensitive capability
  • asana_task_template_instantiateno sensitive capability
  • asana_task_template_listno sensitive capability
  • asana_task_updateno sensitive capability
  • asana_team_getno sensitive capability
  • asana_team_listno sensitive capability
  • asana_url_parseno sensitive capability
  • asana_user_getno sensitive capability
  • asana_user_listno sensitive capability
  • asana_user_meno sensitive capability
  • asana_workspace_getno sensitive capability
  • asana_workspace_listno sensitive capability

What this scan could not see

Versions 6

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.12.0 latest A 94/100 1 1.13.0 2026-09-07
v0.10.0 A 94/100 1 1.13.0 2026-08-31
v0.9.0 A 94/100 1 1.12.1 2026-08-19
v0.8.0 A 94/100 1 1.12.1 2026-08-10
v0.7.0 A 94/100 1 1.12.1 2026-08-09
Show 1 more version ↓
v0.5.0 A 100/100 0 1.12.1 2026-08-04

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 94/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/cyber-asana/badge.svg)](https://mcptrustchecker.com/registry/cyber-asana)
HTML
<a href="https://mcptrustchecker.com/registry/cyber-asana"><img src="https://mcptrustchecker.com/registry/cyber-asana/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/cyber-asana/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan cyber-asana --online

Use the free API → How scoring works

More in Productivity & Workflow