Huly (bgx4k3p) MCP Server

@bgx4k3p/huly-mcp-server npm v3.0.3 Source verified

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

MCP server for Huly issue tracking with stdio and Streamable HTTP transports

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 (src/tokenCount.mjs)MTC-SRC-002

In the server's implementation (`src/tokenCount.mjs:1`): 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: spawnSync } from 'node:child_process'; const ANTHROPIC_VERSION = '2023-06-01'; export const DEFAULT_TOKEN_MODEL = 'cla

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 src/tokenCount.mjs

Tools 84

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

  • batch_create_issuesnetwork egress
  • create_issuenetwork egress
  • create_issues_from_templatenetwork egress
  • add_blocked_byno sensitive capability
  • add_commentno sensitive capability
  • add_email_social_idno sensitive capability
  • add_labelno sensitive capability
  • add_relationno sensitive capability
  • archive_projectno sensitive capability
  • change_passwordno sensitive capability
Show 74 more tools ↓
  • change_usernameno sensitive capability
  • create_componentno sensitive capability
  • create_integrationno sensitive capability
  • create_invite_linkno sensitive capability
  • create_labelno sensitive capability
  • create_mailboxno sensitive capability
  • create_milestoneno sensitive capability
  • create_projectno sensitive capability
  • create_workspaceno sensitive capability
  • delete_commentno sensitive capability
  • delete_componentno sensitive capability
  • delete_integrationno sensitive capability
  • delete_issueno sensitive capability
  • delete_labelno sensitive capability
  • delete_mailboxno sensitive capability
  • delete_milestoneno sensitive capability
  • delete_projectno sensitive capability
  • delete_time_reportno sensitive capability
  • delete_workspaceno sensitive capability
  • find_person_by_social_keyno sensitive capability
  • get_account_infono sensitive capability
  • get_commentno sensitive capability
  • get_componentno sensitive capability
  • get_huly_contextno sensitive capability
  • get_integrationno sensitive capability
  • get_issueno sensitive capability
  • get_labelno sensitive capability
  • get_memberno sensitive capability
  • get_milestoneno sensitive capability
  • get_my_issuesno sensitive capability
  • get_projectno sensitive capability
  • get_social_idsno sensitive capability
  • get_statusno sensitive capability
  • get_task_typeno sensitive capability
  • get_time_reportno sensitive capability
  • get_user_profileno sensitive capability
  • get_workspace_infono sensitive capability
  • get_workspace_membersno sensitive capability
  • Huly Issueno sensitive capability
  • Huly Projectno sensitive capability
  • list_commentsno sensitive capability
  • list_componentsno sensitive capability
  • list_integrationsno sensitive capability
  • list_issuesno sensitive capability
  • list_labelsno sensitive capability
  • list_mailboxesno sensitive capability
  • list_membersno sensitive capability
  • list_milestonesno sensitive capability
  • list_project_typesno sensitive capability
  • list_projectsno sensitive capability
  • list_statusesno sensitive capability
  • list_subscriptionsno sensitive capability
  • list_task_typesno sensitive capability
  • list_time_reportsno sensitive capability
  • list_workspacesno sensitive capability
  • log_timeno sensitive capability
  • move_issueno sensitive capability
  • remove_labelno sensitive capability
  • resend_inviteno sensitive capability
  • search_issuesno sensitive capability
  • send_inviteno sensitive capability
  • set_milestoneno sensitive capability
  • set_my_profileno sensitive capability
  • set_parentno sensitive capability
  • summarize_projectno sensitive capability
  • update_commentno sensitive capability
  • update_componentno sensitive capability
  • update_integrationno sensitive capability
  • update_issueno sensitive capability
  • update_labelno sensitive capability
  • update_milestoneno sensitive capability
  • update_projectno sensitive capability
  • update_workspace_nameno sensitive capability
  • update_workspace_roleno sensitive capability

What this scan could not see

Versions 4

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
v3.0.3 latest A 94/100 1 1.13.0 2026-09-07
v3.0.1 A 94/100 1 1.13.0 2026-09-01
v2.4.7 A 97/100 1 1.13.0 2026-08-31
v2.4.5 A 97/100 1 1.12.1 2026-08-20

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/bgx4k3p-huly-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/bgx4k3p-huly-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/bgx4k3p-huly-mcp-server"><img src="https://mcptrustchecker.com/registry/bgx4k3p-huly-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/bgx4k3p-huly-mcp-server/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 @bgx4k3p/huly-mcp-server --online

Use the free API → How scoring works

Other implementations of Huly 5

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

More in Productivity & Workflow