Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, email [email protected] and we’ll put it right.

OpenFate Bazi MCP

NPM · @OPENFATE/BAZI-MCP · SCANNED AUG 3

OpenFate Bazi MCP with True Solar Time, Four Pillars, Da Yun, and branch interactions.

Available components

+33 this week 71 Trust /100
Trust breakdown (6 categories)

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 →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Only part of the dependency tree could be resolved (98 of 102), so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency71
  • Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to openfate-ai/bazi-mcp). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 32 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 864 tokens (~144/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 Management23
  • Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% of tool parameters carry a description.Partial
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @openfate/bazi-mcp

# add to Claude Code
claude mcp add openfate-ai-bazi-mcp -- npx -y @openfate/bazi-mcp
# add to Codex CLI
codex mcp add openfate-ai-bazi-mcp -- npx -y @openfate/bazi-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "openfate-ai-bazi-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@openfate/bazi-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add openfate-ai-bazi-mcp --command npx --arg -y --arg @openfate/bazi-mcp
# ~/.hermes/config.yaml
mcp_servers:
  openfate-ai-bazi-mcp:
    command: "npx"
    args: ["-y", "@openfate/bazi-mcp"]
// mcp.json
{
  "mcpServers": {
    "openfate-ai-bazi-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "@openfate/bazi-mcp"
      ]
    }
  }
}
Changelog

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 Aug 26 +3
    • Stability: unverified → 0.23 functional
  • 2 Aug 26 +54
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Provenance: unverified → pass security
    • Malware scan: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • The attested source repository moved: openfate-ai/bazi-mcp security
    • Security disclosure: fail → unverified functional
    • Tool coverage: 100 → unverified functional
    • License: unverified → pass functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Schema quality: unverified → good functional
    • First check of Schema quality: unverified functional
    • Licence: MIT functional
  • 31 Jul 26 −6
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 38

    First indexed and scored.

Diagnostics

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 3 Aug 2026 · Analysed npm/@openfate/[email protected]

Provenance verified

Ecosystem: npm · Outcome: verified

Reason: verified

Source repo:
openfate-ai/bazi-mcp
Certificate issuer:
https://token.actions.githubusercontent.com
Certificate SAN:
https://github.com/openfate-ai/bazi-mcp/.github/workflows/npm-publish.yml@refs/tags/v0.2.6
Rekor log index:
2044483129
Predicate type:
https://slsa.dev/provenance/v1
Subject digest:
sha512:d54e8f23fd0790e3d891fa185468bd215c85a374d2dd351eba32017fcad32004cd6f374a77c1986f079752be8a27ece88b632a612a28ff4998087c043
Discovery method:
attestation_endpoint
Dependencies 98 packages

98 packages in the resolved dependency tree · 95 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 6 exposed · ~825 tokens

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.

Tool Tokens
calculate_bazi_chart ~341

Calculate a deterministic OpenFate Bazi/Four Pillars chart with True Solar Time correction, Day Master, Da Yun cycles, and branch interactions. For best accuracy, pass longitude plus timezone or timezoneId.

NameTypeReqDescription
calendarTypestringInput calendar type.
dayintegeryesBirth day, 1-31.
dayBoundaryModestringDay-change rule. ZI_HOUR_23 means 23:00 starts the next day pillar.
dstOffsetnumberDaylight saving offset in hours to remove from civil clock time. Use 1 for one-hour DST.
enableTrueSolarTimebooleanApply true solar time when longitude and timezone data are available.
genderstringyesBirth gender used for Da Yun direction.
hourintegerBirth hour in local civil time, 0-23. Omit when birth time is unknown.
isLeapMonthbooleanWhether the lunar input month is a leap month. Used only when calendarType is lunar.
longitudenumberBirthplace longitude in decimal degrees. Enables true solar time correction.
minuteintegerBirth minute in local civil time.
monthintegeryesBirth month, 1-12.
timezonenumberUTC offset in hours for the birth clock time, such as 8 for China or -5 for US Eastern Standard Time.
timezoneIdstringOptional IANA timezone ID, such as Asia/Shanghai or America/New_York.
yearintegeryesBirth year. Use the lunar year when calendarType is lunar.

No output schema declared.

No examples provided.

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.

NameTypeReqDescription
dayintegeryes
dstOffsetnumberDaylight saving offset in hours.
hourintegeryes
longitudenumberyesBirthplace longitude in decimal degrees.
minuteinteger
monthintegeryes
timezonenumberUTC offset in hours for the clock time.
timezoneIdstringIANA timezone ID, such as Asia/Shanghai.
yearintegeryes

No output schema declared.

No examples provided.

detect_bazi_interactions ~122

Detect deterministic Earthly Branch interactions for natal charts, synastry checks, annual triggers, or target-branch comparison. Covers clashes, combinations, trines, directionals, punishments, destructions, and harms.

NameTypeReqDescription
annualBranchOptional annual or target branch for dynamic interaction detection.
dayBranchstringyesNatal day branch.
hourBranchstringNatal hour branch. Omit when birth time is unknown.
monthBranchstringyesNatal month branch.
yearBranchstringyesNatal year branch.

No output schema declared.

No examples provided.

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 ~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 ~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.

NameTypeReqDescription
bazistringyesFour pillars separated by spaces, for example: 戊寅 己未 己卯 辛未.
dayBoundaryModestringDay-change rule used during lookup.
endYearintegerEnd year for brute-force lookup. Defaults to the current year.
limitintegerMaximum number of matching datetimes to return.
startYearintegerStart year for brute-force lookup.

No output schema declared.

No examples provided.