Is Hummingbot MCP safe to use?

Hummingbot MCP has an HVTrust score of 38.0/100 (Grade D), ranked #1197 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Hummingbot MCP?

Hummingbot MCP scores 38.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 59 GitHub stars and is categorized under MCP Servers.

Hummingbot MCP

hummingbot/mcp

MCP Servers Python Listed Apache-2.0

Is Hummingbot MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 3.5 / 10

Provenance None

Signed commits 9%

Last push 187d ago

Compare Hummingbot MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Hummingbot MCP scores 38.0/100 (Grade D), ranked #1197 of 1325 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 3.5/10; 9% of recent commits are signed; last pushed 2026-03-23. Every point is earned from checkable signals — never paid placement. How scoring works →

How Hummingbot MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Hummingbot MCP’s 38.0.

Where the 38.0 comes from

HVTrust dimensions vs the MCP Servers average

38.0 / 100 · 100.0% confidence

Hummingbot MCP MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

4.8 / 25

5.5 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.5 / 17

0.7 below avg 12.2

Maintenance60% last-push freshness · 40% commit activity

0 / 20

12.1 below avg 12.1

AdoptionLog-scaled stars · package downloads

9.9 / 20

2.7 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Rank Moved

Rank rose 77 spots (#1273 → #1196)

2026-09-25

HVTrust Changed

HVTrust up 5.6pts (32.4 → 38.0)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.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.

Refresh maintenance signals The repo was last pushed 187 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Hummingbot MCP View MCP Servers Report missing data

18.2

Activity sub-score · out of 100

#714

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 D 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-03-23

187 days ago

Commits (4 wk)

Downloads (7d)

16,258

docker

HN mentions (30d)

—

Open Issues

Rank Change

▼1

was #1196

Analysis

Activity Inputs

18.2 / 100

StarsRepository reach

10.7 / 30

FreshnessLast push recency

0.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.5 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.5 / 10

OpenSSF Scorecard · scanned Sep 15, 2026

Signed Commits

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 6

CI-Tests 10

CII-Best-Practices 0

Code-Review 2

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 0

Vulnerabilities 0

Common questions about Hummingbot MCP

Public trust evidence for Hummingbot MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Hummingbot MCP publish package provenance?

No published build provenance is currently detected for Hummingbot 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 Hummingbot MCP have an OpenSSF Scorecard?

Hummingbot MCP has an OpenSSF Scorecard score of 3.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 Hummingbot MCP actively maintained?

Stale. The repository has not been pushed to in 187 days. Consider whether the project is still being maintained.

What license does Hummingbot MCP use?

Hummingbot MCP ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Hummingbot MCP's commits signed?

9% of the last 100 commits to Hummingbot 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

medium confidence

Implemented

Hummingbot MCP appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Postgres

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

N/A

No package source configured

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 Hummingbot 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

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain Hummingbot MCP?

For maintainers

HVTrust scores Hummingbot 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

2026-09-25

Rank Moved

Rank rose 77 spots (#1273 → #1196)

2026-09-25

HVTrust Changed

HVTrust up 5.6pts (32.4 → 38.0)

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Postgres

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 13 spots (#1259 → #1272)

2026-09-23

HVTrust Changed

HVTrust up 17.4pts (15.0 → 32.4)

2026-09-22

Newly Listed

First tracked at rank #1259

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 49 spots (#1271 → #1320)

2026-09-20

HVTrust Changed

HVTrust down 10.5pts (32.4 → 21.9)

2026-09-16

Rank Moved

Rank rose 48 spots (#1317 → #1269)

2026-09-16

HVTrust Changed

HVTrust up 10.5pts (22.1 → 32.6)

2026-09-15

Rank Moved

Rank dropped 44 spots (#1273 → #1317)

2026-09-15

HVTrust Changed

HVTrust down 10.6pts (32.7 → 22.1)

2026-09-14

Rank Moved

Rank rose 44 spots (#1317 → #1273)

2026-09-14

HVTrust Changed

HVTrust up 10.5pts (22.2 → 32.7)

2026-09-12

Rank Moved

Rank dropped 55 spots (#1261 → #1316)

2026-09-12

HVTrust Changed

HVTrust down 10.6pts (32.9 → 22.3)

2026-09-09

Rank Moved

Rank dropped 10 spots (#1249 → #1259)

2026-09-08

Rank Moved

Rank dropped 10 spots (#1239 → #1249)

2026-09-07

Rank Moved

Rank dropped 14 spots (#1225 → #1239)

2026-09-06

Rank Moved

Rank rose 69 spots (#1294 → #1225)

2026-09-06

HVTrust Changed

HVTrust up 10.8pts (22.5 → 33.3)

2026-09-05

Rank Moved

Rank dropped 118 spots (#1176 → #1294)

2026-09-05

HVTrust Changed

HVTrust down 10.9pts (33.4 → 22.5)

2026-09-04

Rank Moved

Rank dropped 16 spots (#1160 → #1176)

2026-09-03

Rank Moved

Rank rose 83 spots (#1243 → #1160)

2026-09-03

HVTrust Changed

HVTrust up 10.8pts (22.7 → 33.5)

2026-09-02

Rank Moved

Rank dropped 171 spots (#1072 → #1243)

2026-09-02

HVTrust Changed

HVTrust down 10.9pts (33.6 → 22.7)

2026-09-01

Rank Moved

Rank dropped 43 spots (#1029 → #1072)

2026-08-31

Rank Moved

Rank dropped 32 spots (#997 → #1029)

2026-08-30

Rank Moved

Rank dropped 52 spots (#945 → #997)

2026-08-29

Rank Moved

Rank dropped 50 spots (#895 → #945)

2026-08-28

Rank Moved

Rank dropped 31 spots (#864 → #895)

2026-08-27

Rank Moved

Rank dropped 24 spots (#840 → #864)

2026-08-26

Scorecard Added

OSSF Scorecard: 3.5/10

2026-08-26

Rank Moved

Rank rose 441 spots (#1281 → #840)

2026-08-26

HVTrust Changed

HVTrust up 20.1pts (13.9 → 34.0)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1253 → #1279)

2026-08-10

Rank Moved

Rank dropped 79 spots (#1172 → #1251)

2026-08-08

Newly Listed

First tracked at rank #1172

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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

Other agents in MCP Servers

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