The 通胜 MCP 服务 (Tung Shing MCP Service) provides traditional Chinese almanac calculations with these features:
📅 Calendar Conversion: Convert between Gregorian and Lunar calendars
🍀 Daily Guidance: Retrieve daily auspicious and inauspicious activities (宜忌)
🕐 Hourly Information: Access luck and activity details for the 12 Chinese two-hour periods
🔮 Metaphysical Elements: Query traditional elements like Five Elements, Deities, and Constellations
Date Flexibility: Get almanac information for specific dates or consecutive days
Provides installation and distribution of the MCP server through npm packages, allowing users to install via npx or global CLI commands
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type @ followed by the MCP server name and your instructions, e.g., "@mcp-tung-shing what are the auspicious activities for today?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
简体中文 | English
中国传统黄历（通胜）计算服务，基于 Model Context Protocol (MCP)
📅 公历农历转换 - 支持公历与农历日期的相互转换
🍀 每日宜忌 - 提供每日吉凶、宜忌活动的详细信息
🕐 时辰信息 - 十二时辰（子、丑、寅等）的吉凶宜忌
🔮 命理元素 - 五行、神煞、星宿等传统命理学详细数据
Related MCP server: Bazi (Eight Characters) Calculation MCP Server
在你的 MCP 配置文件中添加以下内容：
{
"mcpServers": {
"tung-shing": {
"command": "npx",
"args": ["-y", "mcp-tung-shing@latest"]
}
}
}获取指定日期的黄历信息
参数:
参数名 | 类型 | 必填 | 默认值 | 描述 |
| string | 否 | 当天 | 开始日期，格式："YYYY-MM-DD" |
| number | 否 | 1 | 获取天数 |
| boolean | 否 | false | 是否包含时辰信息 |
| array | 否 | - | 筛选宜忌事项类型，条件之间为或关系 |
| 1 | 2 | 是 | - | 过滤类型：宜(1)、忌(2) |
| string | 是 | - | 要筛选的宜忌事项 |
欢迎提交 Issues 和 Pull Requests 来完善此项目。
获取通胜黄历，包括公历、农历、宜忌、吉凶、冲煞等信息
| Name | Required | Description | Default |
|---|---|---|---|
| startDate | No | 开始日期，格式为"YYYY-MM-DD"的字符串 | 2026-05-03 |
| days | No | 要获取的连续天数 | |
| includeHours | No | 是否包含时辰信息 | |
| tabooFilters | No | 多个筛选宜忌事项，条件之间为或关系 |
Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?
No annotations are provided, so the description must fully disclose behavioral traits. It only lists the types of information included, but does not mention any side effects, data volume, performance implications, or whether it requires network access. As a read operation, it is safe, but details are minimal.
Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.
Is the description appropriately sized, front-loaded, and free of redundancy?
The description is a single concise sentence in Chinese, front-loading the core purpose without any superfluous words. Every word adds value, making it highly efficient.
Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.
Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?
Given the absence of an output schema, the description should explain what the returned data looks like or its structure. It only vaguely mentions types of information but does not describe the format, nesting, or example output. For a tool with 4 parameters, more detail is needed for complete understanding.
Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.
Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?
The input schema has 100% coverage with descriptions for all 4 parameters. The description adds no additional meaning beyond the schema, meeting the baseline of 3. It does not explain parameter relationships or provide examples.
Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.
Does the description clearly state what the tool does and how it differs from similar tools?
The description clearly states the tool retrieves a Tong Sheng almanac with specific content (Gregorian, lunar, auspicious/inauspicious, conflicts, etc.). It uses a specific verb '获取' (get) and resource '通胜黄历', and since there are no sibling tools, no differentiation needed.
Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.
Does the description explain when to use this tool, when not to, or what alternatives exist?
The description implies the tool is used when almanac data is needed, but it does not provide explicit guidance on when to use it vs alternatives (none exist) or when not to use it. Lacks context on prerequisites or typical use cases.
Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.
Only one tool exists, so there is no possibility of confusion between tools.
Single tool with a consistent naming pattern following 'verb_noun' style.
With only one tool, the server feels thin for a typical MCP server, though the narrow domain may justify it.
The single tool covers the entire intended functionality of retrieving the Chinese almanac without any obvious gaps.
Unclaimed servers have limited discoverability.
If you are the server author, to access and configure the admin panel.
BaZi four pillars, Chinese zodiac, lunisolar calendar and almanac days for AI agents.
Chinese almanac: lunar calendar, BaZi 八字, daily 宜忌, lucky-day picker, public holidays.
Read-only Bazi, True Solar Time, and Chinese almanac tools in English and Traditional Chinese.
Deterministic calendars and cosmic date JSON for AI agents via MCP (Gregorian 1900-2100).
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/baranwang/mcp-tung-shing'
If you have feedback or need assistance with the MCP directory API, please join our Discord server
