Asana (mcp-wormhole) MCP Server

@mcp-wormhole/asana npm v0.2.0

Published by @mcp-wormhole — 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 — 66 tools, 18 prompt workflows, and browsable resources via the Asana REST API.

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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
Moderate
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 = 96/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 − 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:

PointsAdoption-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.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 66

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

  • asana_get_attachmentingests untrusted input
  • asana_get_tasks_batchingests untrusted input
  • asana_get_useringests untrusted input
  • asana_add_commentno sensitive capability
  • asana_add_comment_htmlno sensitive capability
  • asana_add_portfolio_itemno sensitive capability
  • asana_add_tag_to_taskno sensitive capability
  • asana_add_task_dependencyno sensitive capability
  • asana_add_task_to_projectno sensitive capability
  • asana_add_task_to_sectionno sensitive capability
Show 56 more tools ↓
  • asana_attach_external_urlno sensitive capability
  • asana_create_custom_fieldno sensitive capability
  • asana_create_goalno sensitive capability
  • asana_create_portfoliono sensitive capability
  • asana_create_projectno sensitive capability
  • asana_create_sectionno sensitive capability
  • asana_create_subtaskno sensitive capability
  • asana_create_tagno sensitive capability
  • asana_create_taskno sensitive capability
  • asana_create_time_entryno sensitive capability
  • asana_delete_attachmentno sensitive capability
  • asana_delete_projectno sensitive capability
  • asana_delete_sectionno sensitive capability
  • asana_delete_tagno sensitive capability
  • asana_delete_taskno sensitive capability
  • asana_delete_time_entryno sensitive capability
  • asana_duplicate_taskno sensitive capability
  • asana_get_goalno sensitive capability
  • asana_get_meno sensitive capability
  • asana_get_portfoliono sensitive capability
  • asana_get_projectno sensitive capability
  • asana_get_taskno sensitive capability
  • asana_get_teamno sensitive capability
  • asana_list_attachmentsno sensitive capability
  • asana_list_custom_fieldsno sensitive capability
  • asana_list_goalsno sensitive capability
  • asana_list_my_tasksno sensitive capability
  • asana_list_portfolio_itemsno sensitive capability
  • asana_list_portfoliosno sensitive capability
  • asana_list_project_sectionsno sensitive capability
  • asana_list_project_tasksno sensitive capability
  • asana_list_projectsno sensitive capability
  • asana_list_section_tasksno sensitive capability
  • asana_list_storiesno sensitive capability
  • asana_list_subtasksno sensitive capability
  • asana_list_tagsno sensitive capability
  • asana_list_task_dependenciesno sensitive capability
  • asana_list_task_dependentsno sensitive capability
  • asana_list_task_tagsno sensitive capability
  • asana_list_teamsno sensitive capability
  • asana_list_time_entriesno sensitive capability
  • asana_list_workspace_usersno sensitive capability
  • asana_list_workspacesno sensitive capability
  • asana_remove_portfolio_itemno sensitive capability
  • asana_remove_tag_from_taskno sensitive capability
  • asana_remove_task_dependencyno sensitive capability
  • asana_remove_task_from_projectno sensitive capability
  • asana_remove_task_from_sectionno sensitive capability
  • asana_search_tasksno sensitive capability
  • asana_set_task_parentno sensitive capability
  • asana_typeaheadno sensitive capability
  • asana_update_goalno sensitive capability
  • asana_update_projectno sensitive capability
  • asana_update_sectionno sensitive capability
  • asana_update_tagno sensitive capability
  • asana_update_taskno sensitive capability

What this scan could not see

Versions 1

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.2.0 latest A 96/100 0 1.13.0 2026-09-07

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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/mcp-wormhole-asana/badge.svg)](https://mcptrustchecker.com/registry/mcp-wormhole-asana)
HTML
<a href="https://mcptrustchecker.com/registry/mcp-wormhole-asana"><img src="https://mcptrustchecker.com/registry/mcp-wormhole-asana/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/mcp-wormhole-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 @mcp-wormhole/asana --online

Use the free API → How scoring works

Other implementations of Asana 5

Independent packages implementing the same tool, scanned with the same engine. Compare all 6 side by side →

More in Developer Tools