updated 2026-10-16 20:06 UTC

Huly MCP

Repository Website

Huly MCP and CLI: Feature-complete MCP server and CLI for Huly platform. Intabia partially compatible.

MCP Servers TypeScript Listed MIT

Is Huly MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 4.5 / 10
Provenance None
Signed commits 5%
Last push today
Advisories None known
Compare Huly MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Huly MCP scores 62.3/100 (Grade C), ranked #618 of 1378 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 4.5/10; 5% of recent commits are signed; no published advisory affects its latest release (@firfi/huly-mcp); last pushed 2026-10-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Huly MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Huly MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/dearlordylord/huly-mcp, MIT, last pushed 2026-10-16. 5% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Mixed

    OpenSSF Scorecard rates the repository's practices 4.5/10 (scanned Oct 14, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 0
    CI-Tests 5
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 10
    Fuzzing 10
    License 10
    Maintained 10
    Packaging -1
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked, not attested

    • npm @firfi/huly-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: @firfi/huly-mcp 0.53.1. No published advisory affects it (OSV, checked 2026-10-16).

Changes to this chain

  • 2026-09-04 OSSF Scorecard: 4.6/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Huly MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Huly MCP compares in MCP Servers

  1. #338 MCP Cn Commerce 62.3 ±0
  2. #339 CrowdSentinels AI MCP 62.3 ±0
  3. #340 Huly MCP 62.3 this agent
  4. #341 Computer Use 62.3 ±0
  5. #342 CN Scraper MCP 62.3 ±0

Bars show each HVTrust score; the tick marks Huly MCP’s 62.3.

Where the 62.3 comes from

HVTrust dimensions vs the MCP Servers average

62.3 / 100 · 100.0% confidence

Huly MCP MCP Servers average (781 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.9 / 25
4.6 below avg 10.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.7 below avg 13.5
Transparency50% declared license · 50% OSSF Scorecard
12.3 / 17
in line with avg 12.3
Maintenance60% last-push freshness · 40% commit activity
20.0 / 20
7.7 above avg 12.3
AdoptionLog-scaled stars · package downloads
8.3 / 20
0.9 above avg 7.4

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-10-16
Rank Moved
Rank rose 13 spots (#631 → #618)
2026-10-14
Rank Moved
Rank dropped 10 spots (#622 → #632)
2026-10-03
Rank Moved
Rank dropped 14 spots (#578 → #592)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.5/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Huly MCP View MCP Servers Report missing data
67.2
Activity sub-score · out of 100
#340
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-10-16 20:06 UTC · Repo last pushed today

Rank Trend

2026-09-29 2026-10-16

Activity & Reach

Stars
59
Forks
24
Last Push
2026-10-16
today
Commits (4 wk)
511
Downloads (7d)
1,042
npm
HN mentions (30d)
—
Open Issues
27
Rank Change
▲13
was #631

Analysis

Activity Inputs

67.2 / 100
StarsRepository reach
10.7 / 30
FreshnessLast push recency
25.0 / 25
ActivityRecent commits
25 / 25
CommunityFork signal
6.5 / 20

Common questions about Huly MCP

Huly MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Huly MCP publish package provenance?
No published build provenance is currently detected for Huly MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Huly MCP have an OpenSSF Scorecard?
Huly MCP has an OpenSSF Scorecard score of 4.5/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Huly MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Huly MCP use?
Huly MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Huly MCP's commits signed?
5% of the last 100 commits to Huly MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.

AI agent surface

MCP, providers, tool surface
Scored in HVTrust

These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →

MCP Server Support
high confidence
Implemented
Huly MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
low confidence
None detected
No clear third-party provider dependency detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Huly MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.

2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Huly MCP?

For maintainers

HVTrust scores Huly MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 23HVTrust 3Listed 2Grade 2Scorecard 1Delisted 1MCP 1
2026-10-16
Rank Moved
Rank rose 13 spots (#631 → #618)
2026-10-14
Rank Moved
Rank dropped 10 spots (#622 → #632)
2026-10-03
Rank Moved
Rank dropped 14 spots (#578 → #592)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 199 spots (#758 → #559)
2026-09-23
HVTrust Changed
HVTrust up 32.5pts (29.8 → 62.3)
2026-09-22
Newly Listed
First tracked at rank #758
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank dropped 15 spots (#534 → #549)
2026-09-11
Rank Moved
Rank dropped 12 spots (#519 → #531)
2026-09-08
Rank Moved
Rank dropped 10 spots (#506 → #516)
2026-09-07
Rank Moved
Rank dropped 22 spots (#484 → #506)
2026-09-06
Rank Moved
Rank dropped 12 spots (#472 → #484)
2026-09-05
Rank Moved
Rank dropped 67 spots (#405 → #472)
2026-09-04
Scorecard Added
OSSF Scorecard: 4.6/10
2026-09-04
Grade Changed
Trust grade D → C
2026-09-04
Rank Moved
Rank rose 695 spots (#1100 → #405)
2026-09-04
HVTrust Changed
HVTrust up 25.4pts (36.9 → 62.3)
2026-09-03
Rank Moved
Rank dropped 52 spots (#1048 → #1100)
2026-09-02
Rank Moved
Rank rose 168 spots (#1216 → #1048)
2026-09-02
HVTrust Changed
HVTrust up 14.4pts (22.5 → 36.9)
2026-09-01
Rank Moved
Rank dropped 29 spots (#1187 → #1216)
2026-08-31
Rank Moved
Rank dropped 25 spots (#1162 → #1187)
2026-08-30
Rank Moved
Rank dropped 41 spots (#1121 → #1162)
2026-08-29
Rank Moved
Rank dropped 29 spots (#1092 → #1121)
2026-08-28
Rank Moved
Rank dropped 36 spots (#1056 → #1092)
2026-08-26
Rank Moved
Rank dropped 71 spots (#976 → #1047)
2026-08-24
Rank Moved
Rank dropped 11 spots (#958 → #969)
2026-08-21
Rank Moved
Rank rose 12 spots (#974 → #962)
2026-08-16
Rank Moved
Rank dropped 27 spots (#949 → #976)
2026-08-10
Rank Moved
Rank dropped 56 spots (#890 → #946)
2026-08-08
Newly Listed
First tracked at rank #884
GitHub → Website → npm: @firfi/huly-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 62.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/huly-mcp.svg)](https://hvtracker.net/agents/huly-mcp)
HTML:
<a href="https://hvtracker.net/agents/huly-mcp"><img src="https://hvtracker.net/badge/huly-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON