io.github.varaprasadreddy9676/huly-mcp
NPM · HULY-MCP-SDK
MCP server for Huly — manage projects, issues, documents and more via natural language.
Available components
Last scanned (1 hour ago)
Scores higher than 46% of npm servers
Category Project Management
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 Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 49 of 182 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (EPL-2.0).Pass
- Actively maintained (last published 231 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1664 tokens (~53/item across 31 items; 31 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_issue" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 31 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 −6
- Stability: pass → 0.60 functional
- 29 Oct 26 +1
- Stability: 0.97 → pass security
- 28 Oct 26 −1
- Stability: pass → 0.97 functional
- 24 Oct 26 −3
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
- 22 Oct 26 +1
- Stability: 0.97 → pass security
- 21 Oct 26 −1
- Stability: pass → 0.97 functional
- 17 Oct 26 +45
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
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 5 Nov 2026 · Analysed npm/huly-mcp-sdk@0.5.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-crpf-4hrx-3jrp | CVE-2026-27125 | medium | yes | |
| GHSA-f7gr-6p89-r883 | CVE-2026-27121 | medium | yes | |
| GHSA-m56q-vw4c-c2cp | CVE-2026-27122 | medium | yes | |
| GHSA-phwv-c562-gvmh | CVE-2026-27901 | medium | yes | |
| GHSA-pr6f-5x2q-rwfp | CVE-2026-42599 | medium | yes | |
| GHSA-rcqx-6q8c-2c42 | CVE-2026-42573 | medium | yes | |
| GHSA-w5hq-g745-h8pq | CVE-2026-41907 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 182 packages
| Packages resolved | 182 |
|---|---|
| Deprecated | 3 |
| Stale | 46 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
add_blocked_by ~60
Mark an issue as blocked by another issue
| Name | Type | Req | Description |
|---|---|---|---|
| blockedBy | string | yes | Issue that blocks it, e.g. "PROJ-100" |
| identifier | string | yes | Issue that is blocked, e.g. "PROJ-123" |
No output schema declared.
No examples provided.
add_comment ~42
Add a comment to an issue
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
| message | string | yes | Comment text |
No output schema declared.
No examples provided.
add_label ~64
Add a label to an issue (auto-creates the label if it does not exist)
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
| labelName | string | yes | Label name to add (auto-created if it does not exist) |
No output schema declared.
No examples provided.
add_relation ~58
Mark two issues as related to each other (bidirectional)
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
| relatedTo | string | yes | Related issue identifier, e.g. "PROJ-456" |
No output schema declared.
No examples provided.
create_component ~66
Create a new component in a project
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Component description |
| label | string | yes | Component name |
| lead | string | – | Lead member name (first/last/full) |
| projectIdentifier | string | yes | Project identifier, e.g. "PROJ" |
No output schema declared.
No examples provided.
create_document ~64
Create a new document in a teamspace
| Name | Type | Req | Description |
|---|---|---|---|
| parentId | string | – | Parent document _id (for nested docs); omit for top-level |
| teamspaceId | string | yes | Teamspace _id from list_teamspaces |
| title | string | yes | Document title |
No output schema declared.
No examples provided.
create_issue ~93
Create a new issue in a project
| Name | Type | Req | Description |
|---|---|---|---|
| dueDate | string | – | Due date as ISO 8601 string, e.g. "2026-04-01" |
| priority | string | – | Issue priority |
| projectIdentifier | string | yes | Project identifier, e.g. "PROJ" |
| statusName | string | – | Status name (defaults to project default) |
| title | string | yes | Issue title |
No output schema declared.
No examples provided.
create_label ~49
Create a new label with an optional hex color
| Name | Type | Req | Description |
|---|---|---|---|
| color | string | – | Hex color, e.g. "#FF6B6B" (optional) |
| title | string | yes | Label name |
No output schema declared.
No examples provided.
create_milestone ~86
Create a new milestone in a project with a target date
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | Milestone name |
| projectIdentifier | string | yes | Project identifier, e.g. "PROJ" |
| status | string | – | Milestone status |
| targetDate | string | yes | Target date as ISO 8601 string, e.g. "2026-06-01" |
No output schema declared.
No examples provided.
create_project ~66
Create a new tracker project with a unique ALL-CAPS identifier
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Project description |
| identifier | string | yes | Short ALL-CAPS identifier, e.g. "MYPROJ" |
| name | string | yes | Project name, e.g. "My Project" |
No output schema declared.
No examples provided.
delete_comment ~57
Delete a specific comment from an issue by its ID (get IDs from list_comments)
| Name | Type | Req | Description |
|---|---|---|---|
| commentId | string | yes | Comment _id from list_comments |
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
No output schema declared.
No examples provided.
delete_issue ~45
Permanently delete an issue by identifier (e.g. "PROJ-123")
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier to delete, e.g. "PROJ-123" |
No output schema declared.
No examples provided.
get_document ~39
Get metadata and content of a document (content requires HULY_FRONT_URL env)
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | Document _id from list_documents |
No output schema declared.
No examples provided.
get_issue ~44
Get full details of an issue by identifier (e.g. "PROJ-123")
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
No output schema declared.
No examples provided.
get_project ~38
Get a project by its identifier (e.g. "PROJ")
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Project identifier, e.g. "PROJ" |
No output schema declared.
No examples provided.
link_document ~61
Link a Huly document to an issue — appears in the Relations panel on the issue
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | Document _id from list_documents or create_document |
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
No output schema declared.
No examples provided.
list_comments ~53
List all comments on an issue (includes comment IDs for use with delete_comment)
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
| limit | integer | – | Max comments to return |
No output schema declared.
No examples provided.
list_components ~36
List components (sub-areas) in a project
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdentifier | string | yes | Project identifier, e.g. "PROJ" |
No output schema declared.
No examples provided.
list_documents ~32
List documents in a teamspace
| Name | Type | Req | Description |
|---|---|---|---|
| teamspaceId | string | yes | Teamspace _id from list_teamspaces |
No output schema declared.
No examples provided.
list_issues ~74
List issues in a project with optional filters
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max issues to return |
| priority | string | – | Filter by priority |
| projectIdentifier | string | yes | Project identifier, e.g. "PROJ" |
| status | string | – | Filter by status name, e.g. "In Progress" |
No output schema declared.
No examples provided.
list_labels ~32
List all labels in the workspace
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdentifier | string | – | Optional project filter (currently returns all workspace labels) |
No output schema declared.
No examples provided.
list_members ~15
List all members in the workspace
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_milestones ~33
List milestones for a project
| Name | Type | Req | Description |
|---|---|---|---|
| projectIdentifier | string | yes | Project identifier, e.g. "PROJ" |
No output schema declared.
No examples provided.
list_projects ~17
List all projects in the Huly workspace
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_teamspaces ~18
List all document teamspaces in the workspace
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
log_time ~63
Log hours spent on an issue
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | What was done (optional note) |
| hours | number | yes | Hours spent (e.g. 2.5) |
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
No output schema declared.
No examples provided.
remove_label ~45
Remove a label from an issue
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
| labelName | string | yes | Label name to remove |
No output schema declared.
No examples provided.
search_issues ~34
Full-text search across all issues
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Max results |
| query | string | yes | Search query |
No output schema declared.
No examples provided.
set_parent ~58
Set or clear the parent (epic) of an issue
| Name | Type | Req | Description |
|---|---|---|---|
| identifier | string | yes | Child issue identifier, e.g. "PROJ-123" |
| parentIdentifier | string|null | – | Parent issue identifier, or null to clear parent |
No output schema declared.
No examples provided.
update_document ~64
Set or replace the content of a document from Markdown (supports headings, paragraphs, code blocks, tables, bullet lists)
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | string | yes | Document _id from list_documents or create_document |
| markdown | string | yes | Markdown content to set as the document body |
No output schema declared.
No examples provided.
update_issue ~158
Update an existing issue (title, status, priority, due date, assignee, component, milestone)
| Name | Type | Req | Description |
|---|---|---|---|
| assignee | string|null | – | Assignee name (first/last/full) or null to unassign |
| componentLabel | string | – | Component name to assign, or null to unassign |
| dueDate | string|null | – | New due date (ISO 8601) or null to clear |
| identifier | string | yes | Issue identifier, e.g. "PROJ-123" |
| milestoneLabel | string|null | – | Milestone name to assign, or null to clear |
| priority | string | – | New priority |
| statusName | string | – | New status name |
| title | string | – | New title |
No output schema declared.
No examples provided.
How do I install the io.github.varaprasadreddy9676/huly-mcp server?
io.github.varaprasadreddy9676/huly-mcp runs locally as an npm package, launched with npx -y huly-mcp-sdk. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · huly-mcp-sdk
claude mcp add varaprasadreddy9676-huly-mcp -- npx -y huly-mcp-sdk
What is the io.github.varaprasadreddy9676/huly-mcp server?
io.github.varaprasadreddy9676/huly-mcp is listed in the public MCP registry as io.github.varaprasadreddy9676/huly-mcp. MCP server for Huly, manage projects, issues, documents and more via natural language. This page covers its npm package (huly-mcp-sdk).
Is the io.github.varaprasadreddy9676/huly-mcp server safe to use?
io.github.varaprasadreddy9676/huly-mcp scores 73 out of 100 on VerifyMCP. We recorded 8 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.varaprasadreddy9676/huly-mcp server expose?
io.github.varaprasadreddy9676/huly-mcp exposes 31 tools: list_projects, get_project, create_project, list_issues, get_issue, and 26 more. Their descriptions and schemas cost roughly 1,664 tokens of context every time the server is loaded.
Is the io.github.varaprasadreddy9676/huly-mcp server still maintained?
io.github.varaprasadreddy9676/huly-mcp is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.varaprasadreddy9676/huly-mcp server under?
io.github.varaprasadreddy9676/huly-mcp declares the EPL-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.