@cristip73/mcp-server-asana
npm
v2.0.0
Published by @cristip73 — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
MCP Server for Asana API
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 − 4 = 96. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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.
In the server's implementation (`dist/index.js:9156`): A hardcoded outbound call to a fixed external host inside server code is a classic exfiltration/telemetry channel — especially paired with reads of local data. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: const response = await fetch("https://app.asana.com/api/1.0/attachments", { method: "POST", headers: { Auth
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/index.js
Each tool and what it can reach — statically extracted from the published source.
asana_download_attachmentingests untrusted inputasana_add_followers_for_projectno sensitive capabilityasana_add_followers_to_taskno sensitive capabilityasana_add_members_for_projectno sensitive capabilityasana_add_tags_to_taskno sensitive capabilityasana_add_task_dependenciesno sensitive capabilityasana_add_task_dependentsno sensitive capabilityasana_add_task_to_sectionno sensitive capabilityasana_create_projectno sensitive capabilityasana_create_project_statusno sensitive capabilityasana_create_section_for_projectno sensitive capabilityasana_create_subtaskno sensitive capabilityasana_create_taskno sensitive capabilityasana_create_task_storyno sensitive capabilityasana_delete_project_statusno sensitive capabilityasana_get_attachments_for_objectno sensitive capabilityasana_get_multiple_tasks_by_gidno sensitive capabilityasana_get_projectno sensitive capabilityasana_get_project_hierarchyno sensitive capabilityasana_get_project_sectionsno sensitive capabilityasana_get_project_statusno sensitive capabilityasana_get_project_statusesno sensitive capabilityasana_get_project_task_countsno sensitive capabilityasana_get_subtasks_for_taskno sensitive capabilityasana_get_tags_for_workspaceno sensitive capabilityasana_get_taskno sensitive capabilityasana_get_task_storiesno sensitive capabilityasana_get_tasks_for_projectno sensitive capabilityasana_get_tasks_for_sectionno sensitive capabilityasana_get_tasks_for_tagno sensitive capabilityasana_get_teams_for_userno sensitive capabilityasana_get_teams_for_workspaceno sensitive capabilityasana_list_workspace_usersno sensitive capabilityasana_list_workspacesno sensitive capabilityasana_reorder_sectionsno sensitive capabilityasana_search_projectsno sensitive capabilityasana_search_tasksno sensitive capabilityasana_set_parent_for_taskno sensitive capabilityasana_update_projectno sensitive capabilityasana_update_taskno sensitive capabilityasana_upload_attachment_for_objectno sensitive capabilitytask_idno sensitive capabilitytask-summaryno sensitive capabilityScan 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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v2.0.0 latest |
A 96/100 | 1 | 1.13.0 | 2026-09-07 |
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.
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 @cristip73/mcp-server-asana --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →
MCP Server for Asana
MCP server that gives AI assistants full access to the Asana API — 80 tools, 18 prompt templates, and browsable resources
Asana MCP — wraps the Asana REST API (OAuth)
MCP server for Asana — 66 tools, 18 prompt workflows, and browsable resources via the Asana REST API.
MCP server + typed TypeScript client for the Asana API. Read tools plus guarded, configurable write access (read_only / restricted / full). No delete operations by design.
Adapters for the FrontMCP framework
Transcend MCP Server — Admin tools.
Transcend MCP Server — Assessments tools.
MCP Server for Bling
MCP Server for Blogger API
Official MCP server for Brilliant Directories — manage members, posts, leads, reviews, and more.