Webull OpenAPI

Webull OpenAPI MCP

MCP Servers Python Grade C Listed Apache-2.0
56.1/100
Rank #578 of 1320
Compare Webull OpenAPI

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-15 · 20d ago
Recent change
Rank +9

Is Webull OpenAPI safe? Webull OpenAPI scores 56.1/100 (Grade C), ranked #578 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 4.7/10; recent commits are unsigned; last pushed 2026-08-15. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

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 15 spots (#563 → #578)
2026-09-03
Rank Moved
Rank dropped 35 spots (#528 → #563)
2026-09-02
Rank Moved
Rank dropped 32 spots (#496 → #528)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.7/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.
42.3
Activity sub-score · out of 100
#273

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-09-04 23:32 UTC · Repo last pushed 20 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
21
Forks
4
Last Push
2026-08-15
20 days ago
Commits (4 wk)
4
Downloads (7d)
1,314
pypi
HN mentions (30d)
Open Issues
0
Rank Change
▼15
was #563

Analysis

HVTrust Dimensions vs MCP Servers

56.1 / 100 · 100.0% confidence

Webull OpenAPI MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
5.9 / 25
3.7 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
12.5 / 17
0.7 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
13.5 / 20
1.3 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.4 / 20
1.1 above avg 6.3

Activity Inputs

42.3 / 100
StarsRepository reach
8.1 / 30
FreshnessLast push recency
22.2 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
3.3 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.7 / 10
OpenSSF Scorecard · scanned Sep 4, 2026
Signed Commits
0%
of last 100 commits verified
Binary-Artifacts 10
Branch-Protection 0
CI-Tests -1
CII-Best-Practices 0
Code-Review 0
Contributors 0
Dangerous-Workflow 10
Dependency-Update-Tool 0
Fuzzing 0
License 10
Maintained 10
Packaging 10
Pinned-Dependencies 1
SAST 0
Security-Policy 0
Signed-Releases 0
Token-Permissions 10
Vulnerabilities 10

Is Webull OpenAPI safe?

Webull OpenAPI 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 Webull OpenAPI publish package provenance?
No published build provenance is currently detected for Webull OpenAPI. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Webull OpenAPI have an OpenSSF Scorecard?
Webull OpenAPI has an OpenSSF Scorecard score of 4.7/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 Webull OpenAPI actively maintained?
Maintained. Last push was 20 days ago.
What license does Webull OpenAPI use?
Webull OpenAPI ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Webull OpenAPI's commits signed?
0% of the last 100 commits to Webull OpenAPI 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
Webull OpenAPI appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
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

Maintain Webull OpenAPI?

For maintainers

HVTrust scores Webull OpenAPI 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.

Reputation Timeline

Signal history
Rank 11Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 15 spots (#563 → #578)
2026-09-03
Rank Moved
Rank dropped 35 spots (#528 → #563)
2026-09-02
Rank Moved
Rank dropped 32 spots (#496 → #528)
2026-09-01
Rank Moved
Rank dropped 16 spots (#480 → #496)
2026-08-31
Rank Moved
Rank dropped 38 spots (#442 → #480)
2026-08-29
Scorecard Added
OSSF Scorecard: 4.7/10
2026-08-29
Grade Changed
Trust grade D → C
2026-08-29
Rank Moved
Rank rose 456 spots (#902 → #446)
2026-08-29
HVTrust Changed
HVTrust up 23.7pts (33.7 → 57.4)
2026-08-28
Rank Moved
Rank dropped 39 spots (#863 → #902)
2026-08-27
Rank Moved
Rank dropped 35 spots (#828 → #863)
2026-08-26
Rank Moved
Rank dropped 107 spots (#721 → #828)
2026-08-16
Rank Moved
Rank dropped 15 spots (#698 → #713)
2026-08-10
Rank Moved
Rank dropped 35 spots (#675 → #710)
2026-08-08
Newly Listed
First tracked at rank #670

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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