Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mcparmory/asana

OCI · GHCR.IO/MCPARMORY/ASANA:1.0.5 · 2 COMPONENTS · SCANNED SEP 20

Manage tasks, projects, portfolios, and team workflows

0 this week 50 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security0
  • Malware scan not yet available for this package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.Unverified
Provenance & Transparency32
Schema Quality & AI Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 25088 tokens (~114/item across 220 items; 220 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 36 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 220 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Install

How do I install the com.mcparmory/asana MCP server?

com.mcparmory/asana runs locally as a container image, launched with docker run --rm -i ghcr.io/mcparmory/asana:1.0.5. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

oci · ghcr.io/mcparmory/asana:1.0.5

# add to Claude Code
claude mcp add com-mcparmory-asana -- docker run --rm -i ghcr.io/mcparmory/asana:1.0.5
// .cursor/mcp.json
{
  "mcpServers": {
    "com-mcparmory-asana": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/asana:1.0.5"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-mcparmory-asana": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/asana:1.0.5"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add com-mcparmory-asana -- docker run --rm -i ghcr.io/mcparmory/asana:1.0.5
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mcparmory-asana": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/asana:1.0.5"
      ],
      "enabled": true
    }
  }
}
# ~/.hermes/config.yaml
mcp_servers:
  com-mcparmory-asana:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/mcparmory/asana:1.0.5"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-mcparmory-asana": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/asana:1.0.5"
      ]
    }
  }
}
// mcp.json
{
  "mcpServers": {
    "com-mcparmory-asana": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/mcparmory/asana:1.0.5"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 20 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 15 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 11 Sept 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed oci/ghcr.io/mcparmory/asana:1.0.5

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem oci
Reason No attestation published

Background: How many MCP packages publish verified provenance →

MCP tools · 220 exposed · ~25,088 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
delete_portfolio ~46

Permanently deletes an existing portfolio by its unique identifier. Returns an empty data record upon successful deletion.

NameTypeReqDescription
portfolio_gidstringyesThe globally unique identifier of the portfolio to delete.

No output schema declared.

No examples provided.

delete_project ~54

Permanently deletes an existing project by its unique identifier. This action is irreversible and returns an empty data record upon success.

NameTypeReqDescription
project_gidstringyesThe globally unique identifier (GID) of the project to be deleted.

No output schema declared.

No examples provided.

delete_project_brief ~51

Permanently deletes an existing project brief by its unique identifier. Returns an empty data record upon successful deletion.

NameTypeReqDescription
project_brief_gidstringyesThe globally unique identifier of the project brief to delete.

No output schema declared.

No examples provided.

delete_project_status ~58

Permanently deletes a specific project status update by its unique identifier. Note: this endpoint is deprecated; new integrations should use the status updates route instead.

NameTypeReqDescription
project_status_gidstringyesThe unique identifier of the project status update to delete.

No output schema declared.

No examples provided.

delete_project_template ~53

Permanently deletes an existing project template by its unique identifier. This action is irreversible and returns an empty data record upon success.

NameTypeReqDescription
project_template_gidstringyesThe globally unique identifier of the project template to delete.

No output schema declared.

No examples provided.

delete_rate ~41

Permanently deletes a rate by its unique identifier. This action cannot be undone.

NameTypeReqDescription
rate_gidstringyesThe globally unique identifier of the rate to delete.

No output schema declared.

No examples provided.

delete_section ~56

Permanently deletes an existing section by its unique identifier. The section must be empty and cannot be the last remaining section in the project.

NameTypeReqDescription
section_gidstringyesThe globally unique identifier (GID) of the section to delete.

No output schema declared.

No examples provided.

delete_status_update ~48

Permanently deletes a specific status update by its unique identifier. Returns an empty data record upon successful deletion.

NameTypeReqDescription
status_update_gidstringyesThe unique identifier of the status update to delete.

No output schema declared.

No examples provided.

delete_story ~52

Permanently deletes a story by its unique identifier. Only the story's creator can delete it; returns an empty data record on success.

NameTypeReqDescription
story_gidstringyesThe globally unique identifier of the story to delete.

No output schema declared.

No examples provided.

delete_tag ~45

Permanently deletes an existing tag by its unique identifier. Returns an empty data record upon successful deletion.

NameTypeReqDescription
tag_gidstringyesThe globally unique identifier of the tag to delete.

No output schema declared.

No examples provided.

delete_task ~61

Permanently deletes a specific task by moving it to the requesting user's trash, where it can be recovered within 30 days before being completely removed from the system.

NameTypeReqDescription
task_gidstringyesThe unique global identifier (GID) of the task to delete.

No output schema declared.

No examples provided.

delete_task_template ~53

Permanently deletes an existing task template by its unique identifier. This action is irreversible and returns an empty data record upon success.

NameTypeReqDescription
task_template_gidstringyesThe globally unique identifier of the task template to delete.

No output schema declared.

No examples provided.

delete_time_tracking_entry ~57

Permanently deletes a specific time tracking entry by its unique identifier. Returns an empty data record upon successful deletion.

NameTypeReqDescription
time_tracking_entry_gidstringyesThe globally unique identifier (GID) of the time tracking entry to delete.

No output schema declared.

No examples provided.

delete_webhook ~63

Permanently deletes a webhook, stopping all future event deliveries to its target URL. Note that in-flight requests sent before deletion may still arrive, but no new requests will be issued.

NameTypeReqDescription
webhook_gidstringyesThe globally unique identifier of the webhook to permanently delete.

No output schema declared.

No examples provided.

duplicate_portfolio ~137

Creates a duplicate of an existing portfolio and returns an asynchronous job that handles the duplication process. Custom field settings and views are always copied; additional elements such as members, rules, and child projects can be optionally included.

NameTypeReqDescription
includestringA comma-separated list of optional elements to copy into the duplicate portfolio. Custom field settings and views are always included automatically. Valid values are: description, members, permission…
namestringThe display name to assign to the newly duplicated portfolio.
portfolio_gidstringyesThe globally unique identifier of the portfolio to duplicate.

No output schema declared.

No examples provided.

duplicate_project ~341

Creates an asynchronous duplication job that copies an existing project into a new project, with configurable options for which elements (members, tasks, dates, etc.) to include. Returns a job object that can be polled to track duplication progress.

NameTypeReqDescription
due_onstringAn ISO 8601 date (YYYY-MM-DD) to set as the last due date in the duplicated project; all other due dates are offset proportionally relative to this anchor date.
includestringA comma-separated list of optional elements to copy into the duplicate project. Tasks, project views, and rules are always included automatically. Explicitly specify any combination of optional field…
namestringThe display name to assign to the newly created duplicate project.
project_gidstringyesThe globally unique identifier (GID) of the source project to duplicate.
should_skip_weekendsbooleanRequired when shifting task dates: determines whether auto-shifted due and start dates should skip Saturday and Sunday when recalculating offsets.
start_onstringAn ISO 8601 date (YYYY-MM-DD) to set as the first start date in the duplicated project; all other start dates are offset proportionally relative to this anchor date.
teamstringThe GID of the team to assign the new project to. If omitted, the duplicate inherits the same team as the source project.

No output schema declared.

No examples provided.

duplicate_task ~128

Duplicates an existing task and returns an asynchronous job that handles the duplication process. You can specify a new name and choose which fields to carry over to the duplicated task.

NameTypeReqDescription
includestringA comma-separated list of fields to copy from the original task to the duplicate. Supported fields include: assignee, attachments, dates, dependencies, followers, notes, parent, projects, subtasks, a…
namestringThe name to assign to the newly duplicated task.
task_gidstringyesThe unique identifier (GID) of the task to duplicate.

No output schema declared.

No examples provided.

export_graph ~87

Initiates an asynchronous graph export job for a goal, team, portfolio, or project. Use the jobs endpoint to monitor progress; exports exceeding 1,000 tasks are cached for 4 hours, with subsequent requests returning the cached result.

NameTypeReqDescription
parentstringThe globally unique ID of the parent object (goal, project, portfolio, or team) whose graph data should be exported.

No output schema declared.

No examples provided.

get_allocation ~59

Retrieves the complete record for a single allocation, including all associated details and metadata. Use this to fetch full information about a specific allocation by its unique identifier.

NameTypeReqDescription
allocation_gidstringyesThe globally unique identifier for the allocation you want to retrieve.

No output schema declared.

No examples provided.

get_attachment ~48

Retrieves the full record for a single attachment, including its metadata and download URL. Requires the attachments:read scope.

NameTypeReqDescription
attachment_gidstringyesThe globally unique identifier of the attachment to retrieve.

No output schema declared.

No examples provided.

get_budget ~53

Retrieves the complete record for a single budget, including all associated details and metadata. Use this to inspect a specific budget by its unique identifier.

NameTypeReqDescription
budget_gidstringyesThe globally unique identifier of the budget to retrieve.

No output schema declared.

No examples provided.

get_custom_field ~55

Retrieves the complete metadata definition for a specific custom field, including type-specific properties such as enum options, validation rules, and display settings.

NameTypeReqDescription
custom_field_gidstringyesThe globally unique identifier of the custom field to retrieve.

No output schema declared.

No examples provided.

get_custom_type ~57

Retrieves the complete record for a single custom type by its unique identifier. Use this to inspect the full definition and configuration of a specific custom type.

NameTypeReqDescription
custom_type_gidstringyesThe globally unique identifier of the custom type to retrieve.

No output schema declared.

No examples provided.

get_goal ~64

Retrieves the complete record for a single goal, including all associated fields and metadata. Requires the goals:read scope, with additional time_periods:read scope needed to access the time_period field.

NameTypeReqDescription
goal_gidstringyesThe globally unique identifier of the goal to retrieve.

No output schema declared.

No examples provided.

get_goal_relationship ~76

Retrieves the complete record for a single goal relationship, including details about how two goals are linked. Use this to inspect the nature and status of a specific goal-to-goal connection.

NameTypeReqDescription
goal_relationship_gidstringyesThe unique identifier of the goal relationship to retrieve. This ID is returned when a goal relationship is created or listed.

No output schema declared.

No examples provided.

get_job ~64

Retrieves the full record for a specific asynchronous job by its unique identifier. Useful for polling job status and accessing output resources such as new tasks, projects, portfolios, or templates created by the job.

NameTypeReqDescription
job_gidstringyesThe globally unique identifier of the job to retrieve.

No output schema declared.

No examples provided.

get_membership ~78

Retrieves a single membership record by its unique identifier, returning details for any supported membership type including project, goal, portfolio, custom type, or custom field memberships.

NameTypeReqDescription
membership_gidstringyesThe globally unique identifier of the membership record to retrieve, applicable across all membership types (project, goal, portfolio, custom type, or custom field).

No output schema declared.

No examples provided.

get_organization_export ~58

Retrieves the current status and details of a previously requested organization export. Use this to check export progress or access the resulting download URL once complete.

NameTypeReqDescription
organization_export_gidstringyesThe globally unique identifier of the organization export request to retrieve.

No output schema declared.

No examples provided.

get_portfolio ~47

Retrieves the complete record for a single portfolio, including all associated metadata. Requires the portfolios:read scope.

NameTypeReqDescription
portfolio_gidstringyesThe globally unique identifier of the portfolio to retrieve.

No output schema declared.

No examples provided.

get_portfolio_membership ~58

Retrieves the complete details of a single portfolio membership record. Use this to inspect a specific user's membership relationship within a portfolio.

NameTypeReqDescription
portfolio_membership_gidstringyesThe unique identifier (GID) of the portfolio membership to retrieve.

No output schema declared.

No examples provided.

get_project ~67

Retrieves the complete record for a single project, including all available fields and metadata. Requires the `projects:read` scope; accessing the `team` field additionally requires `teams:read`.

NameTypeReqDescription
project_gidstringyesThe globally unique identifier (GID) of the project to retrieve.

No output schema declared.

No examples provided.

get_project_brief ~51

Retrieves the full record for a specific project brief, including its title, description, and associated project details.

NameTypeReqDescription
project_brief_gidstringyesThe globally unique identifier for the project brief to retrieve.

No output schema declared.

No examples provided.

get_project_membership ~57

Retrieves the complete details of a single project membership record, including the member's role and access level within the project.

NameTypeReqDescription
project_membership_gidstringyesThe unique identifier (GID) of the project membership record to retrieve.

No output schema declared.

No examples provided.

get_project_portfolio_setting ~56

Retrieves the complete record for a single project portfolio setting. Requires the `project_portfolio_settings:read` scope.

NameTypeReqDescription
project_portfolio_setting_gidstringyesThe globally unique identifier of the project portfolio setting to retrieve.

No output schema declared.

No examples provided.

get_project_status ~66

Retrieves the complete record for a single project status update by its unique identifier. Note: this endpoint is deprecated; new integrations should use the `/status_updates/{status_gid}` route instead.

NameTypeReqDescription
project_status_gidstringyesThe unique global identifier of the project status update to retrieve.

No output schema declared.

No examples provided.

get_project_task_counts ~71

Retrieves task count statistics for a specific project, including total, incomplete, and completed task counts (milestones are included). All fields are excluded by default and must be explicitly requested using opt_fields.

NameTypeReqDescription
project_gidstringyesThe globally unique identifier of the project whose task counts you want to retrieve.

No output schema declared.

No examples provided.

get_project_template ~53

Retrieves the complete record for a single project template, including all its configuration and metadata. Requires the project_templates:read scope.

NameTypeReqDescription
project_template_gidstringyesThe globally unique identifier of the project template to retrieve.

No output schema declared.

No examples provided.

get_rate ~42

Retrieves the complete record for a single rate, including all associated pricing details and metadata.

NameTypeReqDescription
rate_gidstringyesThe globally unique identifier for the rate to retrieve.

No output schema declared.

No examples provided.

get_section ~58

Retrieves the complete details for a single section by its unique identifier. Useful for inspecting section metadata such as its name, project association, and ordering.

NameTypeReqDescription
section_gidstringyesThe globally unique identifier (GID) of the section to retrieve.

No output schema declared.

No examples provided.

get_status_update ~56

Retrieves the complete record for a single status update by its unique identifier. Useful for fetching the full details of a specific project or task status update.

NameTypeReqDescription
status_update_gidstringyesThe unique identifier of the status update to retrieve.

No output schema declared.

No examples provided.

get_story ~63

Retrieves the full record for a single story by its unique identifier. Requires the stories:read scope, with additional attachments:read scope needed to access previews and attachments fields.

NameTypeReqDescription
story_gidstringyesThe globally unique identifier (GID) of the story to retrieve.

No output schema declared.

No examples provided.

get_tag ~55

Retrieves the complete record for a single tag, including its name, color, and associated metadata. Requires the tags:read scope.

NameTypeReqDescription
tag_gidstringyesThe globally unique identifier (GID) of the tag to retrieve.

No output schema declared.

No examples provided.

get_task ~71

Retrieves the complete record for a single task, including all fields and metadata. Note that accessing memberships requires projects:read and project_sections:read scopes, and actual_time_minutes requires time_tracking_entries:read scope.

NameTypeReqDescription
task_gidstringyesThe unique global identifier (GID) of the task to retrieve.

No output schema declared.

No examples provided.

get_task_by_custom_id ~100

Retrieves a task using its human-readable custom ID shortcode within a specified workspace. Useful when referencing tasks by their display identifiers rather than internal GIDs.

NameTypeReqDescription
custom_idstringyesThe custom ID shortcode assigned to the task, typically formatted as a prefix followed by a number (e.g., a project code and sequence number).
workspace_gidstringyesThe globally unique identifier for the workspace or organization in which to search for the task.

No output schema declared.

No examples provided.

get_task_template ~57

Retrieves the complete record for a single task template, including all its fields and configuration. Requires the task_templates:read scope.

NameTypeReqDescription
task_template_gidstringyesThe globally unique identifier (GID) of the task template to retrieve.

No output schema declared.

No examples provided.

get_team ~49

Retrieves the full details for a single team by its unique identifier. Requires the teams:read scope.

NameTypeReqDescription
team_gidstringyesThe globally unique identifier (GID) for the team to retrieve.

No output schema declared.

No examples provided.

get_team_membership ~80

Retrieves the complete membership record for a single team membership, including details about the member and their associated team. Requires the `team_memberships:read` scope, with additional `teams:read` scope needed to access team details.

NameTypeReqDescription
team_membership_gidstringyesThe unique identifier (GID) of the team membership record to retrieve.

No output schema declared.

No examples provided.

get_time_period ~57

Retrieves the full details of a specific time period by its unique identifier. Useful for accessing goal-tracking intervals such as fiscal quarters or annual periods.

NameTypeReqDescription
time_period_gidstringyesThe globally unique identifier of the time period to retrieve.

No output schema declared.

No examples provided.

get_time_tracking_entry ~55

Retrieves the complete record for a single time tracking entry. Requires the time_tracking_entries:read scope.

NameTypeReqDescription
time_tracking_entry_gidstringyesThe globally unique identifier (GID) of the time tracking entry to retrieve.

No output schema declared.

No examples provided.

get_timesheet_approval_status ~73

Retrieves the complete record for a single timesheet approval status, including its current state and associated metadata. Requires the timesheet_approval_statuses:read scope.

NameTypeReqDescription
timesheet_approval_status_gidstringyesThe globally unique identifier (GID) of the timesheet approval status record to retrieve.

No output schema declared.

No examples provided.

Common questions

What is the com.mcparmory/asana MCP server?

com.mcparmory/asana is an MCP server listed in the public MCP registry as com.mcparmory/asana. Manage tasks, projects, portfolios, and team workflows. This page covers its container image (ghcr.io/mcparmory/asana:1.0.5).

Is the com.mcparmory/asana MCP server safe to use?

com.mcparmory/asana scores 50 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.mcparmory/asana MCP server expose?

com.mcparmory/asana exposes 220 tools: list_access_requests, request_access, approve_access_request, reject_access_request, get_allocation, and 215 more. Their descriptions and schemas cost roughly 25,088 tokens of context every time the server is loaded.

Is the com.mcparmory/asana MCP server still maintained?

com.mcparmory/asana is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.