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

io.github.ghdejr11-beep/saju-mcp

NPM · SAJU-MCP

Korean Four Pillars of Destiny (Saju/Bazi): calculate, interpret, compatibility & daily fortune.

Available components

−8 this week 67 Trust /100

Last scanned (7 hours ago)

Scores higher than 35% of npm servers

Trust breakdown (7 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 → 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
  • 74 of 259 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency6
  • Repository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository. View diagnostics → Unverified
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (LicenseRef-Proprietary) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 141 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 701 tokens (~175/item across 4 items; 4 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 Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
What we tested

Checks we ran (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Provenance in Provenance & TransparencyRepository presence not verified: we could not reach the forge to check. This is a gap on our side, not a finding about the repository.

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 →

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.

  • 5 Nov 26 −8
    • Provenance: pass → unverified ▼ security
    • Stability: pass → 0.80 functional
  • 31 Oct 26 0
    • CVE-2026-118764 affects this package: high ▼ security
  • 24 Oct 26 −3
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. security
    • Stability: 0.97 → pass security
  • 23 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 −1
    • Stability: pass → 0.93 functional
  • 16 Oct 26 0
    • Stability: 0.97 → pass security
  • 15 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

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 5 Nov 2026 · Analysed npm/saju-mcp@0.1.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Vulnerabilities 3 findings
ID CVE Severity Vector Fix available
GHSA-c475-qrg2-pj4r CVE-2026-102990 high yes
GHSA-g3hv-75wg-m249 CVE-2026-118764 medium yes
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 259 packages
Packages resolved 259
Deprecated 1
Stale 74
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~701 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. 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 →

Tool Tokens
saju_calculate ~214

Compute the Korean Four Pillars of Destiny (사주팔자 / Bazi) from a solar birthdate. Returns the year/month/day/hour pillars (heavenly stem + earthly branch, with hanja), the five-element distribution (wood/fire/earth/metal/water), the Day Master, and the zodiac animal.

NameTypeReqDescription
dayintegeryesBirth day, 1–31
genderstringyesGender: 'M' or 'F' (affects Daeun / luck-pillar direction).
hourintegeryesBirth hour in 24h time (0–23). Use -1 if the hour is unknown.
langstring–Output language (default ko). One of: ko, en, ja, zh, es, pt-br, vi, id, hi, th
monthintegeryesBirth month, 1–12
yearintegeryesSolar (Gregorian) birth year, 1920–2050

No output schema declared.

No examples provided.

saju_compatibility ~91

Score two-person compatibility (궁합) from 0–100 based on both people's Saju. Returns the overall score and a breakdown (element balance, Day Master relation, branch harmony, branch clash) plus each person's Day Master and zodiac.

NameTypeReqDescription
lang–––
person_aobjectyesFirst person (birth details).
person_bobjectyesSecond person (birth details).

No output schema declared.

No examples provided.

saju_daily ~191

Daily fortune snapshot (0–100 score + advice) for a given Day Master and date. Provide the Day Master either as a Korean stem character (갑, 을, 병, 정, 무, 기, 경, 신, 임, 계) or an English alias (e.g. wood_yang, water_yin). The Day Master comes from a prior saju_calculate / saju_interpret call (day_master.stem).

NameTypeReqDescription
datestring–Target date in YYYY-MM-DD. Defaults to today (UTC).
day_masterstringyesDay Master: Korean stem (갑..계) or English alias (wood_yang, wood_yin, fire_yang, ... water_yin).
langstring–Output language (default ko). One of: ko, en, ja, zh, es, pt-br, vi, id, hi, th

No output schema declared.

No examples provided.

saju_interpret ~205

Full Saju interpretation from a solar birthdate: the Four Pillars plus Ten Gods (십신), hidden stems, life stages, interactions, Yongshin (용신 / useful god), Daeun (대운 / luck pillars), and human-readable summaries in the requested language.

NameTypeReqDescription
dayintegeryesBirth day, 1–31
genderstringyesGender: 'M' or 'F' (affects Daeun / luck-pillar direction).
hourintegeryesBirth hour in 24h time (0–23). Use -1 if the hour is unknown.
langstring–Output language (default ko). One of: ko, en, ja, zh, es, pt-br, vi, id, hi, th
monthintegeryesBirth month, 1–12
yearintegeryesSolar (Gregorian) birth year, 1920–2050

No output schema declared.

No examples provided.

Install

How do I install the io.github.ghdejr11-beep/saju-mcp server?

io.github.ghdejr11-beep/saju-mcp runs locally as an npm package, launched with npx -y saju-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 · saju-mcp

# add to Claude Code
claude mcp add ghdejr11-beep-saju-mcp -- npx -y saju-mcp
Common questions

What is the io.github.ghdejr11-beep/saju-mcp server?

io.github.ghdejr11-beep/saju-mcp is listed in the public MCP registry as io.github.ghdejr11-beep/saju-mcp. Korean Four Pillars of Destiny (Saju/Bazi): calculate, interpret, compatibility & daily fortune. This page covers its npm package (saju-mcp).

Is the io.github.ghdejr11-beep/saju-mcp server safe to use?

io.github.ghdejr11-beep/saju-mcp scores 67 out of 100 on VerifyMCP. We recorded 3 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.ghdejr11-beep/saju-mcp server expose?

io.github.ghdejr11-beep/saju-mcp exposes 4 tools: saju_calculate, saju_interpret, saju_compatibility, saju_daily. Their descriptions and schemas cost roughly 701 tokens of context every time the server is loaded.

Is the io.github.ghdejr11-beep/saju-mcp server still maintained?

io.github.ghdejr11-beep/saju-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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 io.github.ghdejr11-beep/saju-mcp server under?

io.github.ghdejr11-beep/saju-mcp declares the LicenseRef-Proprietary licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

What did VerifyMCP test on the io.github.ghdejr11-beep/saju-mcp server?

VerifyMCP ran 15 checks on io.github.ghdejr11-beep/saju-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.ghdejr11-beep/saju-mcp: Provenance. 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.