Is Openfate MCP safe to use?

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

What is the trust score for Openfate MCP?

Openfate MCP scores 48.0/100 on HVTracker's evidence-weighted HVTrust scale. It has 156 GitHub stars and is categorized under MCP Servers.

Openfate MCP

openfate-ai/openfate-mcp

OpenFate Bazi MCP server with deterministic Four Pillars calculation, True Solar Time, branch interactions, and reverse Bazi lookup.

MCP Servers TypeScript Listed MIT

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

OSSF Scorecard 3.9 / 10

Provenance None

Signed commits 0%

Last push 6d ago

Compare Openfate MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Openfate MCP scores 48.0/100 (Grade D), ranked #995 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.9/10; recent commits are unsigned; last pushed 2026-09-20. Every point is earned from checkable signals — never paid placement. How scoring works →

How Openfate MCP compares in MCP Servers

Bars show each HVTrust score; the tick marks Openfate MCP’s 48.0.

Where the 48.0 comes from

HVTrust dimensions vs the MCP Servers average

48.0 / 100 · 100.0% confidence

Openfate MCP MCP Servers average (775 agents)

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

4.9 / 25

5.4 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.8 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.2 / 20

1.1 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.3 / 20

1.9 below 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 dropped 16 spots (#979 → #995)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 417 spots (#560 → #977)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 3.9/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 Openfate MCP View MCP Servers Report missing data

53.5

Activity sub-score · out of 100

#583

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 C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

156

Forks

Last Push

2026-09-20

6 days ago

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

was #995

Analysis

Activity Inputs

53.5 / 100

StarsRepository reach

13.2 / 30

FreshnessLast push recency

24.2 / 25

ActivityRecent commits

9.7 / 25

CommunityFork signal

6.3 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

3.9 / 10

OpenSSF Scorecard · scanned Sep 26, 2026

Signed Commits

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 9

Packaging 10

Pinned-Dependencies 2

SAST 0

Security-Policy 0

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about Openfate MCP

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

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

Openfate MCP has an OpenSSF Scorecard score of 3.9/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 Openfate MCP actively maintained?

Actively maintained. The repository was pushed to within the last 6 day(s).

What license does Openfate MCP use?

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

Are Openfate MCP's commits signed?

0% of the last 100 commits to Openfate 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

Openfate MCP 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

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 Openfate 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 Openfate MCP?

For maintainers

HVTrust scores Openfate 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 dropped 16 spots (#979 → #995)

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank dropped 417 spots (#560 → #977)

2026-09-23

HVTrust Changed

HVTrust up 12.1pts (36.3 → 48.4)

2026-09-22

Newly Listed

First tracked at rank #560

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank rose 83 spots (#1099 → #1016)

2026-09-20

HVTrust Changed

HVTrust up 4.0pts (42.9 → 46.9)

2026-09-20

Activity Score Changed

Activity score up 12pts (43 → 54)

2026-09-12

Rank Moved

Rank dropped 11 spots (#1084 → #1095)

2026-09-09

Rank Moved

Rank dropped 15 spots (#1063 → #1078)

2026-09-07

Rank Moved

Rank dropped 35 spots (#1021 → #1056)

2026-09-06

Rank Moved

Rank rose 86 spots (#1107 → #1021)

2026-09-06

HVTrust Changed

HVTrust up 4.3pts (39.4 → 43.7)

2026-09-06

Activity Score Changed

Activity score up 9pts (35 → 44)

2026-09-05

Rank Moved

Rank dropped 39 spots (#1068 → #1107)

2026-09-04

Rank Moved

Rank dropped 30 spots (#1038 → #1068)

2026-09-03

Rank Moved

Rank dropped 56 spots (#982 → #1038)

2026-09-02

Rank Moved

Rank dropped 47 spots (#935 → #982)

2026-09-01

Scorecard Added

OSSF Scorecard: 2.5/10

2026-09-01

Rank Moved

Rank rose 334 spots (#1269 → #935)

2026-09-01

HVTrust Changed

HVTrust up 21.4pts (18.2 → 39.6)

2026-08-31

Rank Moved

Rank dropped 11 spots (#1258 → #1269)

2026-08-30

Rank Moved

Rank dropped 14 spots (#1244 → #1258)

2026-08-29

Rank Moved

Rank dropped 19 spots (#1225 → #1244)

2026-08-28

Rank Moved

Rank dropped 12 spots (#1213 → #1225)

2026-08-27

Rank Moved

Rank dropped 10 spots (#1203 → #1213)

2026-08-26

Rank Moved

Rank dropped 40 spots (#1163 → #1203)

2026-08-16

Rank Moved

Rank dropped 27 spots (#1124 → #1151)

2026-08-10

Rank Moved

Rank dropped 67 spots (#1056 → #1123)

2026-08-08

Newly Listed

First tracked at rank #1055

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

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