Skip to main content
Glama
molpass

mcp-taiyi

by molpass
OverviewSchemaRelated ServersScoreDiscussions
Python
Local

mcp-taiyi

기준 일시를 받아 태을신수(太乙神數) 국·산법을 계산해 구조화 텍스트와 포국 PNG를 반환하는 MCP 서버. (Python 런타임)

구조·네이밍·PNG·설치 규약은 STANDARD.md를 따른다(§6 Python 블록). mcp-qimen / mcp-liuren과 동일한 Python 패턴.

구성 / 계산

  • 산법 엔진: kintaiyi — 太乙 年計/月計/日計/時計/分計.

  • 천체력/유틸 의존: sxtwl, ephem, numpy, cn2an (kintaiyi 내부 사용, 미선언이라 명시 설치).

  • 렌더: Pillow — 산법 결과 그리드, 한자/한글 폰트.

  • 결정론적: 같은 입력 → 같은 국.

Related MCP server: mcp-ziwei

도구

get_taiyi

파라미터

타입

필수

기본

설명

datetime_str

string YYYY-MM-DD HH:MM

✅

—

기준 일시

mode

year|month|day|hour|minute|ming

day

計 단위(年計~分計/命法)

  • mode 매핑: year→年計, month→月計, day→日計, hour→時計, minute→分計.

  • ⚠️ ming(命法): kintaiyi 0.2.3은 命法을 직접 제공하지 않는다. 太乙命法이 출생 年計 반을 토대로 함에 따라 年計(ji_style 0)로 근사하며, 출력·PNG에 근사임을 명시한다. (집에서 함께 검증 예정)

출력 (둘 다 반환):

  1. 구조화 텍스트 — 局式·紀元·太歲·太乙落宮·文昌·始擊·主客算將參·定算·君臣民基 등

  2. 포국 PNG (1080×약760, 局式 배너 + 산법 그리드)

예제 출력: examples/taiyi_example.png (2024-02-10 14:30, 日計).

설치 (Python 3.10/3.11)

⚠️ sxtwl/ephem은 바이너리 휠이 필요하다. Windows에서는 Python 3.10 또는 3.11을 쓴다 (3.12+는 sxtwl 휠 부재 → 빌드 실패). Linux는 3.12도 manylinux 휠로 가능.

git clone https://github.com/molpass/mcp-taiyi.git
cd mcp-taiyi
python -m venv .venv && . .venv/bin/activate   # Windows: .venv\Scripts\activate
pip install -r requirements.txt

예제 포국을 직접 생성해 보려면:

python examples/generate-example.py   # examples/taiyi_example.png 재생성 + 전 mode 점검

폰트: 한자·한글 라벨을 위해 한글 가능 폰트가 필요하다. Windows는 Malgun Gothic 기본 탑재. Linux는 Noto CJK / Nanum 권장.

MCP 등록 (서버명 taiyi, STANDARD §6 Python)

{
  "mcpServers": {
    "taiyi": {
      "command": "/abs/path/mcp-taiyi/.venv/bin/python",
      "args": ["/abs/path/mcp-taiyi/server.py"]
    }
  }
}

Windows 예: "command": "C:/Users/<you>/mcp-taiyi/.venv/Scripts/python.exe", "args": ["C:/Users/<you>/mcp-taiyi/server.py"]

스킬

페어링 스킬: skill/taiyi.skill.md.

About / 제작

Hermes Agent용 MCP — molpass의 바이브 코딩(vibe coding) 프로젝트.

  • 아이디어·방향: molpass (이정훈) · https://zeolinex.com

  • 기획: Claude (Chat)

  • 개발: Claude Code

자가 호스팅 Hermes Agent에 도구로 붙여 쓰는 MCP 서버입니다.

같은 모음:

License

MIT

Available Tools

1 tool
get_taiyiA

태을신수 포국/산법을 계산한다.

Args:
    datetime_str: 기준 일시 "YYYY-MM-DD HH:MM".
    mode: 계산 단위 — year(年計)/month(月計)/day(日計)/hour(時計)/minute(分計)/ming(命法).
        ⚠️ ming(命法)은 kintaiyi 0.2.3이 직접 지원하지 않아 年計 기반으로 근사하며,
        출력에 그 사실을 명시한다.

Returns:
    구조화 텍스트(局式·紀元·主客算將參·太乙落宮 등 산법)와 포국 PNG.
ParametersJSON Schema
NameRequiredDescriptionDefault
datetime_strYes
modeNoday

TDQS

A4.6/5.0
Behavior4/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It discloses that the tool returns structured text and a PNG, and that 'ming' mode uses an approximation. It does not discuss authorization or side effects, but the read-only nature is implied.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness5/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is well-structured with Args and Returns sections, uses bullet points for the mode enum, and is front-loaded with the core purpose. Every sentence adds value without redundancy.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness5/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given the tool has 2 parameters, no output schema, and no annotations, the description covers all essential aspects: purpose, parameters, behavior (including approximation warning), and return format (structured text and PNG). It is fully sufficient for a specialized tool.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters5/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description fully compensates by explaining datetime_str as a date-time string with format, and mode as the calculation unit with enum values and a specific warning about 'ming'. This adds significant value beyond the schema.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose5/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool calculates Taiyi Divine Number layout/calculation method, with a specific verb ('계산한다') and resource ('태을신수 포국/산법'). It distinguishes itself from potential siblings by detailing its specific function, even though no siblings are listed.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines4/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides context on when to use the tool (calculating Taiyi for various time units) and includes a warning about the 'ming' mode approximation. It does not explicitly state when not to use, but given the specialized nature, the guidance is clear.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.

  1. 1 tool updatev1.0.0
    • First observedget_taiyi
Install Server
RayrunBuild, deploy, and operate MCP servers without becoming an infrastructure team.ray.runAd

TDQS

A4.6/5.0
Disambiguation5/5

With only one tool, there is no possibility of confusion or overlap between tools.

Naming Consistency5/5

The single tool follows a clear verb_noun pattern, which is consistent and descriptive.

Tool Count4/5

The server has a narrow, specialized purpose (Taiyi calculations), so one comprehensive tool is appropriate, though slightly thin for a general-purpose server.

Completeness4/5

The tool covers multiple calculation modes (year, month, day, hour, minute, ming) and returns both text and PNG, making it fairly complete for its domain.

Maintenance

ActivityStale
ResponsivenessNo issues

Resources

Unclaimed servers have limited discoverability.

Looking for Admin?

If you are the server author, to access and configure the admin panel.

Related MCP Connectors

Related MCP Servers

  • LiuRen MCP Server

    wuunicorn
    F
    license
    Not graded
    quality
    D
    maintenance
    Enables traditional Chinese divination calculations through Liu Ren (六壬) chart generation. Provides tools for calculating Liu Ren divination charts based on specified dates and times, along with current time retrieval functionality.
    -

  • mcp-ziwei

    molpass
    A
    license
    A
    quality
    C
    maintenance
    Calculates and returns a Ziwei Doushu (Purple Star Astrology) chart based on birth date, time, and gender. Returns both structured text of the 12 palaces and a PNG image of the chart.
    1
    MIT

  • liuren

    molpass
    A
    license
    A
    quality
    C
    maintenance
    Enables 大六壬 divination by computing the chart (三傳, 四課, etc.) and generating a 天地盤 PNG from a given datetime.
    1
    MIT

  • mcp-qimen

    molpass
    A
    license
    Not graded
    quality
    C
    maintenance
    Evaluates Qimen Dunjia divination for a given date and time, returning structured text and a 9-palace PNG chart.
    MIT

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/molpass/mcp-taiyi'

If you have feedback or need assistance with the MCP directory API, please join our Discord server