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.

FateStar Ziwei

REMOTE · WWW.FATESTAR.TOP · SCANNED SEP 21

Zi Wei Dou Shu for AI agents: free natal charts, six transit levels, and optional readings.

Available components

0 this week 84 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability58
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1420 tokens (~473/item across 3 items; 3 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 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
Install

How do I install the FateStar Ziwei MCP server?

FateStar Ziwei is a hosted endpoint at https://www.fatestar.top/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.fatestar.top

# add to Claude Code
claude mcp add --transport http louislin0723-fatestar-ziwei 'https://www.fatestar.top/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "louislin0723-fatestar-ziwei": {
      "url": "https://www.fatestar.top/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "louislin0723-fatestar-ziwei": {
      "type": "http",
      "url": "https://www.fatestar.top/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.louislin0723-fatestar-ziwei]
url = "https://www.fatestar.top/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "louislin0723-fatestar-ziwei": {
      "type": "remote",
      "url": "https://www.fatestar.top/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add louislin0723-fatestar-ziwei --url 'https://www.fatestar.top/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  louislin0723-fatestar-ziwei:
    url: "https://www.fatestar.top/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "louislin0723-fatestar-ziwei": {
      "Transport": "http",
      "Url": "https://www.fatestar.top/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add louislin0723-fatestar-ziwei -t streamable-http -u 'https://www.fatestar.top/api/mcp'
// mcp.json
{
  "mcpServers": {
    "louislin0723-fatestar-ziwei": {
      "type": "http",
      "url": "https://www.fatestar.top/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

  • 30 Aug 26 0
    • Stability: 0.97 → pass security
  • 29 Aug 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.

  • 26 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 1 Aug 26 0
    • Authorization: unverified → partial security
    • Tool “ziwei_reading” rewrote its description, which is the text the model reads security
    • Tool “ziwei_transits” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 functional
    • Tool “ziwei_chart” now declares an output schema functional
    • Tool “ziwei_reading” now declares an output schema functional
    • Tool “ziwei_transits” now declares an output schema functional
    • First check of Tool coverage: 100 functional
    • “ziwei_transits” reworded the description of “targetDay” cosmetic
    • “ziwei_transits” reworded the description of “targetMonth” cosmetic
    • “ziwei_transits” reworded the description of “targetYear” cosmetic
  • 31 Jul 26 0

    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 21 Sept 2026 · Probed https://www.fatestar.top/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fatestar.top CN=YR1,O=Let's Encrypt,C=US 14 Aug 2026 12 Nov 2026 RSA 2048 SHA256-RSA 60b3889973711ef8355e6ef86eca5a2749b
SANs: *.fatestar.top, fatestar.top
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.fatestar.top. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
top. present 26780 8 Verified
fatestar.top. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.fatestar.top/api/mcp Verified 200
http (plaintext) http://www.fatestar.top/api/mcp HTTPS enforced 308 https://www.fatestar.top/api/mcp
MCP tools · 3 exposed · ~1,420 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
ziwei_chart ~404

生成紫微斗数 (Zi Wei Dou Shu / Purple Star Astrology) 完整本命盘。输入阳历或农历出生信息, 返回: 五行局/阴阳/命主身主、十二宫 (主星辅星煞星杂曜+庙旺亮度+生年四化+空宫借星+大限年龄+长生十二神)、生年四化所在宫、格局识别 (30+ 经典格局含古籍出处)、夹宫扫描、真实出生四柱 (万年历按节气)。引擎为 FateStar 自建 (102 颗星, 三合派四化, 真太阳时修正), 0 第三方排盘库。⚠️ 三合派庚干: 化科=天同 / 化忌=太阴。

NameTypeReqDescription
calendarTypestring历法: solar=公历(默认) / lunar=农历
dayintegeryes出生日 (1-31)
genderstringyes性别
hourintegeryes出生小时 0-23 (24 小时制, 非时辰地支)
isLeapMonthboolean是否闰月 (仅 calendarType=lunar 有效)
longitudenumber出生地经度 (东经正/西经负). 传了即启用真太阳时修正
minuteinteger出生分钟 (默认 0; 配合 longitude 做真太阳时精修)
monthintegeryes出生月 (1-12)
timezoneOffsetnumber时区偏移 (UTC+8=8, UTC-5=-5). 需配合 longitude
yearintegeryes出生年 (阳历; calendarType=lunar 时填农历年)
NameTypeReqDescription
servicestringyes
十二宫arrayyes
基础objectyes
夹宫arrayyes
本命四化objectyes
格局arrayyes
输入objectyes

No examples provided.

ziwei_reading ~546

调 FateStar「郑大钱」AI 命理师 —— 知识引擎 + 郑大钱人格深度解读命盘、回答命理问题 (感情/事业/财运/健康等)。解读会结合 FateStar 知识引擎与古籍检索上下文;排盘事实仍由确定性工具提供。【调用条件】仅在用户明确选择托管解读并确认可能扣积分后调用。普通命理问题默认先用免费排盘数据。⚠️ 付费: 按问题长度/模式扣积分 (短问免费), 需 FSFSKey 开发者 Key。【没 Key】引导用户去 https://www.fatestar.top 注册免费会员 → 做新手任务领积分 → 开发者中心拿 FSFSKey Key → 配进 MCP (环境变量 FATESTAR_API_KEY 或 apiKey 参数)。【积分用完 (402)】告知用户「已切回你自己的 LLM 解读, 请去 fatestar.top 充值或等北京时间 21:00 免费重置」, 然后改用 ziwei_chart 拿命盘数据 + 你自己解读。

NameTypeReqDescription
apiKeystringFSFSKey 开发者 Key (也可由 MCP server 环境变量 FATESTAR_API_KEY 提供; 旧 fs_live_ 仍兼容)
calendarTypestring历法: solar=公历(默认) / lunar=农历
dayintegeryes出生日 (1-31)
genderstringyes性别
hourintegeryes出生小时 0-23 (24 小时制, 非时辰地支)
isLeapMonthboolean是否闰月 (仅 calendarType=lunar 有效)
longitudenumber出生地经度 (东经正/西经负). 传了即启用真太阳时修正
minuteinteger出生分钟 (默认 0; 配合 longitude 做真太阳时精修)
monthintegeryes出生月 (1-12)
questionstringyes要问郑大钱的问题 (如「今年事业运如何」「该不该换工作」)
timezoneOffsetnumber时区偏移 (UTC+8=8, UTC-5=-5). 需配合 longitude
yearintegeryes出生年 (阳历; calendarType=lunar 时填农历年)
NameTypeReqDescription
剩余积分number
扣除积分number
提示string
现有积分number
积分不足boolean
运限object
郑大钱解读string
需注册boolean
需积分number

No examples provided.

ziwei_transits ~470

在本命盘基础上计算 6 层运限: 大限 (10 年运, 含全部 13 段列表) / 小限 (1 年) / 流年 / 流月 / 流日 / 流时。每层返回该层命宫地支 + 四化 (化禄/化权/化科/化忌) + 双轨干支 (真实干支 vs 宫位编号)。不传 target* 则默认: 当前农历年月日 + 出生时辰。⚠️ 双轨干支铁律: 对外讲「X 日签约 / X 月运势」必用「真实干支」, 严禁用「宫位编号」当日子说。

NameTypeReqDescription
calendarTypestring历法: solar=公历(默认) / lunar=农历
dayintegeryes出生日 (1-31)
genderstringyes性别
hourintegeryes出生小时 0-23 (24 小时制, 非时辰地支)
isLeapMonthboolean是否闰月 (仅 calendarType=lunar 有效)
longitudenumber出生地经度 (东经正/西经负). 传了即启用真太阳时修正
minuteinteger出生分钟 (默认 0; 配合 longitude 做真太阳时精修)
monthintegeryes出生月 (1-12)
targetDayinteger流日目标农历日 (默认当前农历日)
targetHourinteger流时目标小时 0-23 (默认出生时辰)
targetMonthinteger流月目标农历月 (默认当前农历月)
targetYearinteger流年目标年 (默认当前农历年)
timezoneOffsetnumber时区偏移 (UTC+8=8, UTC-5=-5). 需配合 longitude
yearintegeryes出生年 (阳历; calendarType=lunar 时填农历年)
NameTypeReqDescription
servicestringyes
双轨干支提示stringyes
大限列表arrayyes
小限objectyes
流年objectyes
流日objectyes
流时objectyes
流月objectyes
流运目标objectyes

No examples provided.

Common questions

What is the FateStar Ziwei MCP server?

FateStar Ziwei is an MCP server listed in the public MCP registry as io.github.LouisLin0723/fatestar-ziwei. Zi Wei Dou Shu for AI agents: free natal charts, six transit levels, and optional readings. This page covers its hosted endpoint (https://www.fatestar.top/api/mcp).

Is the FateStar Ziwei MCP server safe to use?

FateStar Ziwei scores 84 out of 100 on VerifyMCP. 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 FateStar Ziwei MCP server expose?

FateStar Ziwei exposes 3 tools: ziwei_chart, ziwei_transits, ziwei_reading. Their descriptions and schemas cost roughly 1,420 tokens of context every time the server is loaded.

Does the FateStar Ziwei MCP server require authentication?

No. We connected to FateStar Ziwei without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the FateStar Ziwei MCP server still maintained?

FateStar Ziwei is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.