# Legend Saju

> Source-traceable Saju, Zi Wei, Qimen, Daliuren, Tieban, naming, and related calculations

- name: io.github.SihyeonJeon/legend-saju
- version: 0.4.0
- connection class: unknown (unknown)
- trust: 64/100 flags: unreachable
- quality: 86/100 (good)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/io.github.SihyeonJeon%2Flegend-saju
- tools: https://api.protogrid.dev/v1/servers/io.github.SihyeonJeon%2Flegend-saju/tools

**Not classified yet.** The remote endpoints have not been probed successfully, or the listing has nothing to connect to.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "legend-saju": {
      "type": "http",
      "url": "https://legend-saju-mcp-production.up.railway.app/mcp"
    }
  }
}
```


## Trust

- hygiene: 100
- liveness: 0
- freshness: 85
- provenance: 90
- drivers: +repository +namespace-matches-repo +website -unreachable(11 failures) ~updated-58d-ago
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 86/100 (good)

### protocol: 88 (weight 25)

- pass `protocol.modern`: supports 2026-07-28 (server/discover)
- pass `protocol.stateless`: answers without a session
- pass `protocol.transport`: streamable HTTP
- warn `protocol.list_ttl`: tools/list declares ttlMs 0, so clients re-fetch it on every use

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 79 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 13 of 13 tools declare readOnlyHint or destructiveHint
- fail `tools.directory_hints`: no tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: legend_saju_manifest (idempotentHint); legend_saju_capabilities (idempotentHint); legend_saju_read_fortune (idempotentHint); …
- warn `tools.token_cost`: about 11,435 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 13, about 11,435 tokens to load them all
- tool set hash: 1febad5cc9c4cfcc50b1f05e647b8860
- badge: [![protogrid quality](https://protogrid.dev/badge/io.github.SihyeonJeon/legend-saju.svg)](https://protogrid.dev/servers/io.github.SihyeonJeon/legend-saju)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://legend-saju-mcp-production.up.railway.app/mcp (streamable-http, auth none, reachable false, uptime30d 0.6857143)

## Packages

_none_

## Tools (13)

- `legend_saju_analyze_compatibility`: Use this when the user asks 궁합, 결혼 가능성, relationship compatibility, or wants two birth charts compared. Requires both people's birth data.
- `legend_saju_analyze_name`: Use this for 작명, 성명학, 81수, 이름 한자, 인명용 한자, 획수, or 파자 questions. It keeps legal Hanja observations, declared stroke standards, and birth-based naming guidance separate.
- `legend_saju_capabilities`: Use this when a user asks which Saju, Myeongri, Zi Wei, Qimen, Daliuren, I Ching, Tieban, Dang Saju, Tojeong, Feng Shui, naming, dream, or other traditional calculation method fits a specialized question. Do not use it for an ordinary fortune reading.
- `legend_saju_card_compatibility`: Render a two-person compatibility card (사주 궁합 봐주세요). Shows both day pillars and deterministic 합·충·형·파·해 signals. Compute chart facts server-side and render them in a widget card. Write the narrative/text fields yourself, grounded in a prior legend_saju_read_fortune call — the card labels them as AI interpretation. After the card renders, add only brief text the card does not already show.
- `legend_saju_card_fortune`: Render domain fortune cards (재물운·연애운·결혼운·직업운·건강운·학업운·이동운·재회운·총운). Pick only the domains the user asked about and write each card's text yourself. Compute chart facts server-side and render them in a widget card. Write the narrative/text fields yourself, grounded in a prior legend_saju_read_fortune call — the card labels them as AI interpretation. After the card renders, add only brief text the card does not already show.
- `legend_saju_card_natal`: Render a natal-chart card (사주 봐주세요·원국 풀이·신살 질문). Shows four pillars, day-master identity, element balance, 왕쇠·격국·용신 verdicts, 신살, and 합충. Compute chart facts server-side and render them in a widget card. Write the narrative/text fields yourself, grounded in a prior legend_saju_read_fortune call — the card labels them as AI interpretation. After the card renders, add only brief text the card does not already show.
- `legend_saju_card_timeline`: Render the 대운 flow timeline (대운 흐름·결혼 시기·이직/창업 시기 질문). Marks the current 대운 and an optional focus year with its 세운. Compute chart facts server-side and render them in a widget card. Write the narrative/text fields yourself, grounded in a prior legend_saju_read_fortune call — the card labels them as AI interpretation. After the card renders, add only brief text the card does not already show.
- `legend_saju_cast_divination`: Use this for 기문둔갑, 대육임, 주역, 점괘, or a concrete decision cast from a question time or six line values. Do not use it for a general natal fortune reading.
- `legend_saju_interpret_dream`: Use this for 해몽, 꿈풀이, or dream interpretation. It currently handles five cross-culturally audited concepts and returns both shared motifs and conflicting conditions with primary-source excerpts; it does not turn the remaining raw corpus into invented meanings.
- `legend_saju_manifest`: Return the live, source-traceable deterministic engine manifest. No model or network call.
- `legend_saju_read_fortune`: Use this for natal, current, annual, career, wealth, relationship, health, and action readings. Use detailLevel for calculation breadth and outputMode for action, readable, evidence, or debug results. Consumer responses always carry verdicts (왕쇠·격국·용신 후보 conclusions) plus an evidenceIndex of omitted internal claims; repeat the identical call with claimIds from that index to selectively pull deeper grounding such as strength axes, pattern structure, or methodology notes.
- `legend_saju_run_methods`: Use this for expert, mixed-system, or named-method requests. It covers Myeongri details such as 십성·지장간·투간·통근·합충형파해·삼합·방합·육합·월령·격국·조후·억부·통관·병약·궁통보감·적천수·삼명통회·연해자평·종격·화격·특수격; Zi Wei 12궁·삼방사정·대한·유년·유월·유일·유시·생년사화·궁간사화·자화·비성·흠천사화·중주파; and Qimen, Daliuren, I Ching, Tieban, Dang Saju, Tojeong, Feng Shui, naming, 81-number, Hanja decomposition, and dream traditions. Pass discovered capability IDs together in requestedCapabilities, or let the server plan from the question. Use focused tools for ordinary single-goal requests.
- `legend_saju_select_dates`: Use this only when the user explicitly asks for 택일, 좋은 날, 계약일, 이사일, 개업일, 수술일, or another date-selection task. Do not use it merely because a fortune request mentions this year.