OpenFate Bazi MCP
NPM · @OPENFATE/BAZI-MCP
OpenFate Bazi MCP with True Solar Time, Four Pillars, Da Yun, and branch interactions.
Available components
Last scanned (9 hours ago)
Scores higher than 91% of npm servers
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to openfate-ai/openfate-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 46 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1008 tokens (~168/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 86% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −5
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +2
- Stability: 0.87 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 6 Nov 2026 · Analysed npm/@openfate/bazi-mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | openfate-ai/openfate-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/openfate-ai/openfate-mcp/.github/workflows/npm-publish.yml@refs/tags/v0.3.1 |
| Rekor log index | 2903473315 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:87a09cd15773de1c398e8beffa27cfb2af2e64c4f25827c9d457eda7fb21577df31f2fed1b523f28bc80d7845f3d73eb2cc10ed033174c7c2bdb5aa1e |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_bazi_chart Calculate Bazi Chart ~376
Calculate a deterministic OpenFate Bazi/Four Pillars chart with True Solar Time correction, Day Master, DAYUN_SECOND_V2 onset receipts, Da Yun cycles, and branch interactions. Pass an exact birth time plus timezone or timezoneId for a calculated V2 onset; otherwise inspect the explicit unavailable/fallback receipt.
| Name | Type | Req | Description |
|---|---|---|---|
| calendarType | string | – | Input calendar type. |
| day | integer | yes | Birth day, 1-31. |
| dayBoundaryMode | string | – | Day-change rule. ZI_HOUR_23 means 23:00 starts the next day pillar. |
| dstOffset | number | – | Daylight saving offset in hours to remove from civil clock time. Use 1 for one-hour DST. |
| enableTrueSolarTime | boolean | – | Apply true solar time when longitude and timezone data are available. |
| gender | string | yes | Birth gender used for Da Yun direction. |
| hour | integer | – | Birth hour in local civil time, 0-23. Omit when birth time is unknown. |
| isLeapMonth | boolean | – | Whether the lunar input month is a leap month. Used only when calendarType is lunar. |
| longitude | number | – | Birthplace longitude in decimal degrees. Enables true solar time correction. |
| minute | integer | – | Birth minute in local civil time. |
| month | integer | yes | Birth month, 1-12. |
| second | integer | – | Birth second in local civil time. |
| timezone | number | – | UTC offset in hours for the birth clock time, such as 8 for China or -5 for US Eastern Standard Time. |
| timezoneId | string | – | Optional IANA timezone ID, such as Asia/Shanghai or America/New_York. |
| year | integer | yes | Birth year. Use the lunar year when calendarType is lunar. |
No output schema declared.
No examples provided.
calculate_true_solar_time Calculate True Solar Time ~143
Calculate OpenFate True Solar Time from civil birth time, longitude, timezone, and optional DST offset. Use this when explaining why the hour pillar may differ from ordinary clock-time tools.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | – |
| dstOffset | number | – | Daylight saving offset in hours. |
| hour | integer | yes | – |
| longitude | number | yes | Birthplace longitude in decimal degrees. |
| minute | integer | – | – |
| month | integer | yes | – |
| timezone | number | – | UTC offset in hours for the clock time. |
| timezoneId | string | – | IANA timezone ID, such as Asia/Shanghai. |
| year | integer | yes | – |
No output schema declared.
No examples provided.
detect_bazi_interactions Detect Bazi Interactions ~207
Detect raw Earthly Branch relationship occurrences for a natal chart and optional annual and Da Yun branches. Preserves every matching pillar position, including repeated branches. Covers clashes, six-combinations, the eight central-branch half-trines (COMBINATION_HALF), full trines, directionals, punishments, destructions, and harms. Results establish relationship presence, not weights, cancellation, or automatic transformation; targetElement is an affinity, not transformed energy.
| Name | Type | Req | Description |
|---|---|---|---|
| annualBranch | – | – | Optional annual or target branch. Preserved as the annual pillar role, independently of repeated natal branches. |
| dayBranch | string | yes | Natal day branch. |
| dayunBranch | – | – | Optional Da Yun branch. Preserved as the dayun pillar role, independently of the annual and natal branches. |
| hourBranch | string | – | Natal hour branch. Omit when birth time is unknown. |
| monthBranch | string | yes | Natal month branch. |
| yearBranch | string | yes | Natal year branch. |
No output schema declared.
No examples provided.
get_openfate_bazi_policy Get OpenFate Bazi Policy ~29
Return OpenFate calculation policy and LLM guidance for Bazi chart calls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_openfate_bazi_resources Get OpenFate Bazi Resources ~38
Return canonical OpenFate URLs for charting, readings, compatibility, wealth, true solar time, and AI crawler metadata.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reverse_bazi_to_solar_times Reverse Bazi To Solar Times ~152
Find possible Gregorian datetimes that produce a given four-pillar Bazi string. This is useful when a user only has a Bazi chart or screenshot. This lookup uses clock-time pillars without location-based true solar correction.
| Name | Type | Req | Description |
|---|---|---|---|
| bazi | string | yes | Four pillars separated by spaces, for example: 戊寅 己未 己卯 辛未. |
| dayBoundaryMode | string | – | Day-change rule used during lookup. |
| endYear | integer | – | End year for brute-force lookup. Defaults to the current year. |
| limit | integer | – | Maximum number of matching datetimes to return. |
| startYear | integer | – | Start year for brute-force lookup. |
No output schema declared.
No examples provided.
How do I install the OpenFate Bazi MCP server?
OpenFate Bazi MCP runs locally as an npm package, launched with npx -y @openfate/bazi-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @openfate/bazi-mcp
claude mcp add openfate-ai-bazi-mcp -- npx -y @openfate/bazi-mcp
What is the OpenFate Bazi MCP server?
OpenFate Bazi MCP is listed in the public MCP registry as io.github.openfate-ai/bazi-mcp. OpenFate Bazi MCP with True Solar Time, Four Pillars, Da Yun, and branch interactions. This page covers its npm package (@openfate/bazi-mcp).
Is the OpenFate Bazi MCP server safe to use?
OpenFate Bazi MCP scores 87 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the OpenFate Bazi MCP server expose?
OpenFate Bazi MCP exposes 6 tools: calculate_bazi_chart, detect_bazi_interactions, calculate_true_solar_time, reverse_bazi_to_solar_times, get_openfate_bazi_policy, get_openfate_bazi_resources. Their descriptions and schemas cost roughly 945 tokens of context every time the server is loaded.
Is the OpenFate Bazi MCP server still maintained?
OpenFate Bazi MCP is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the OpenFate Bazi MCP server under?
OpenFate Bazi MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the OpenFate Bazi MCP server?
VerifyMCP ran 16 checks on OpenFate Bazi MCP, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.