Is TradeOS safe to use?

TradeOS has an HVTrust score of 41.5/100 (Grade D), ranked #1020 of 1320 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for TradeOS?

TradeOS scores 41.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 15 GitHub stars and is categorized under MCP Servers.

TradeOS

TradeOS-AI/tradeos-mcp

TradeOS MCP lets you connect TradeOS trading intelligence to MCP-compatible AI tools, so your assistant can analyze mark

MCP Servers JavaScript Grade D Listed MIT

41.5/100

Rank #1020 of 1320

Compare TradeOS

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-06-03 · 93d ago

Recent change

Rank +10

Is TradeOS safe? TradeOS scores 41.5/100 (Grade D), ranked #1020 of 1320 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.6/10; 17% of recent commits are signed; last pushed 2026-06-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#566 MCP Design System Extractor — 41.9 (D) → #567 Mac Control MCP — 41.5 (D) → #569 Pagecast — 41.4 (D) → #570 XcodeMCP — 41.4 (D) →

Quick Trust Read

What Would Improve It

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

Recent Changes

2026-09-04

Rank Moved

Rank dropped 24 spots (#996 → #1020)

2026-09-03

Rank Moved

Rank rose 198 spots (#1194 → #996)

2026-09-03

HVTrust Changed

HVTrust up 14.6pts (27.0 → 41.6)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.6/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 93 days ago. Fresh activity helps separate stable projects from stale ones.

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

24.1

Activity sub-score · out of 100

#568

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

Activity & Reach

Stars

Forks

Last Push

2026-06-03

93 days ago

Commits (4 wk)

Downloads (7d)

npm

HN mentions (30d)

—

Open Issues

Rank Change

▼24

was #996

Analysis

HVTrust Dimensions vs MCP Servers

41.5 / 100 · 100.0% confidence

TradeOS MCP Servers average (778 agents)

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

5.3 / 25

4.3 below avg 9.6

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

11.6 / 17

in line with avg 11.8

Maintenance60% last-push freshness · 40% commit activity

5.8 / 20

6.4 below avg 12.2

AdoptionLog-scaled stars · package downloads

5.3 / 20

1.0 below avg 6.3

Activity Inputs

24.1 / 100

StarsRepository reach

7.2 / 30

FreshnessLast push recency

12.1 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

4.8 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.6 / 10

OpenSSF Scorecard · scanned Sep 2, 2026

Signed Commits

17%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 0

CII-Best-Practices 0

Code-Review 1

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 0

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 3

SAST 0

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Is TradeOS safe?

Public trust evidence for TradeOS 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 TradeOS publish package provenance?

No published build provenance is currently detected for TradeOS. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does TradeOS have an OpenSSF Scorecard?

TradeOS has an OpenSSF Scorecard score of 3.6/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 TradeOS actively maintained?

Slowing down. Last push was 93 days ago — keep an eye on whether activity resumes.

What license does TradeOS use?

TradeOS ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are TradeOS's commits signed?

16% of the last 100 commits to TradeOS 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

Declared

MCP support appears present, but direct server implementation is less certain.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Anthropic

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration 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 TradeOS'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-01

Activity Went Stale

No commits for 90 days

Maintain TradeOS?

For maintainers

HVTrust scores TradeOS 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-04

Rank Moved

Rank dropped 24 spots (#996 → #1020)

2026-09-03

Rank Moved

Rank rose 198 spots (#1194 → #996)

2026-09-03

HVTrust Changed

HVTrust up 14.6pts (27.0 → 41.6)

2026-09-02

Rank Moved

Rank dropped 38 spots (#1156 → #1194)

2026-09-01

Activity Went Stale

No commits for 90 days

2026-09-01

Rank Moved

Rank dropped 52 spots (#1104 → #1156)

2026-08-31

Rank Moved

Rank dropped 29 spots (#1075 → #1104)

2026-08-30

Rank Moved

Rank dropped 53 spots (#1022 → #1075)

2026-08-29

Scorecard Added

OSSF Scorecard: 4.3/10

2026-08-29

Rank Moved

Rank rose 275 spots (#1297 → #1022)

2026-08-29

HVTrust Changed

HVTrust up 13.8pts (14.4 → 28.2)

2026-08-26

Rank Moved

Rank dropped 13 spots (#1277 → #1290)

2026-08-16

Rank Moved

Rank dropped 26 spots (#1249 → #1275)

2026-08-10

Rank Moved

Rank dropped 77 spots (#1164 → #1241)

2026-08-08

Newly Listed

First tracked at rank #1164

GitHub → npm: @tradeos/tradeos-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/tradeos.svg)](https://hvtracker.net/agents/tradeos)
            
HTML:
            <a href="https://hvtracker.net/agents/tradeos"><img src="https://hvtracker.net/badge/tradeos.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.3 · Raw JSON