ziwei-mcp
Registry code: 7c1252d7fd0d8ea8
Zi Wei Dou Shu for AI agents: free natal charts, six transit levels, and optional readings.
from a public catalogue that lists it, not from the operator
- endpoint
- https://www.fatestar.top/api/mcp
- protocol
- streamable-http ·2025-06-18
- authentication
- none observed
- public key
- none — nobody has proven they own this listing · is it yours? claim it
- karma
- 0 · newcomer
- Is ziwei-mcp live?
- Yes — it answered the hub's last check (checked 20m ago). It answered 90% of checks over the last 30 days.
- Is ziwei-mcp free to use?
- Yes — the hub reached it with no key and no payment.
- What tools does ziwei-mcp have?
- 3 tools: ziwei_transits, ziwei_reading, ziwei_chart.
- Is ziwei-mcp safe to connect?
- The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
90 days 93.6%· all time 93.6%
last good check
of 3 tools
- degraded → live
- live → degraded· HTTP 503
- down → live
- degraded → down· HTTP 402: vercel DEPLOYMENT_DISABLED
- live → degraded· HTTP 402: vercel DEPLOYMENT_DISABLED
- topic
- lifestyle & home
- used for
- generate a zi wei dou shu natal chart
- calculate astrological transit periods
- get an astrology reading for a question
- takes → gives
- data, text → data, text
- tools
- 3 reads
Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.
through this hub
successful
what callers paid
Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run
Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.
ziwei_transits reads unknown 11h ago
在本命盘基础上计算 6 层运限: 大限 (10 年运, 含全部 13 段列表) / 小限 (1 年) / 流年 / 流月 / 流日 / 流时。每层返回该层命宫地支 + 四化 (化禄/化权/化科/化忌) + 双轨干支 (真实干支 vs 宫位编号)。不传 target* 则默认: 当前农历年月日 + 出生时辰。⚠️ 双轨干支铁律: 对外讲「X 日签约 / X 月运势」必用「真实干支」, 严禁用「宫位编号」当日子说。
{ "type": "object", "required": [ "year", "month", "day", "hour", "gender" ], "properties": { "day": { "type": "integer", "maximum": 31, "minimum": 1, "description": "出生日 (1-31)" }, "hour": { "type": "integer", "maximum": 23, "minimum": 0, "description": "出生小时 0-23 (24 小时制, 非时辰地支)" }, "year": { "type": "integer", "maximum": 2100, "minimum": 1900, "description": "出生年 (阳历; calendarType=lunar 时填农历年)" }, "month": { "type": "integer", "maximum": 12, "minimum": 1, "description": "出生月 (1-12)" }, "gender": { "enum": [ "male", "female" ], "type": "string", "description": "性别" }, "minute": { "type": "integer", "maximum": 59, "minimum": 0, "description": "出生分钟 (默认 0; 配合 longitude 做真太阳时精修)" }, "longitude": { "type": "number", "description": "出生地经度 (东经正/西经负). 传了即启用真太阳时修正" }, "targetDay": { "type": "integer", "maximum": 30, "minimum": 1, "description": "流日目标农历日 (默认当前农历日)" }, "targetHour": { "type": "integer", "maximum": 23, "minimum": 0, "description": "流时目标小时 0-23 (默认出生时辰)" }, "targetYear": { "type": "integer", "maximum": 2100, "minimum": 1900, "description": "流年目标年 (默认当前农历年)" }, "isLeapMonth": { "type": "boolean", "description": "是否闰月 (仅 calendarType=lunar 有效)" }, "targetMonth": { "type": "integer", "maximum": 12, "minimum": 1, "description": "流月目标农历月 (默认当前农历月)" }, "calendarType": { "enum": [ "solar", "lunar" ], "type": "string", "default": "solar", "description": "历法: solar=公历(默认) / lunar=农历" }, "timezoneOffset": { "type": "number", "description": "时区偏移 (UTC+8=8, UTC-5=-5). 需配合 longitude" } }, "additionalProperties": false }arguments 96 linesziwei_reading reads unknown never probed
调 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 拿命盘数据 + 你自己解读。
{ "type": "object", "required": [ "year", "month", "day", "hour", "gender", "question" ], "properties": { "day": { "type": "integer", "maximum": 31, "minimum": 1, "description": "出生日 (1-31)" }, "hour": { "type": "integer", "maximum": 23, "minimum": 0, "description": "出生小时 0-23 (24 小时制, 非时辰地支)" }, "year": { "type": "integer", "maximum": 2100, "minimum": 1900, "description": "出生年 (阳历; calendarType=lunar 时填农历年)" }, "month": { "type": "integer", "maximum": 12, "minimum": 1, "description": "出生月 (1-12)" }, "apiKey": { "type": "string", "description": "FSFSKey 开发者 Key (也可由 MCP server 环境变量 FATESTAR_API_KEY 提供; 旧 fs_live_ 仍兼容)" }, "gender": { "enum": [ "male", "female" ], "type": "string", "description": "性别" }, "minute": { "type": "integer", "maximum": 59, "minimum": 0, "description": "出生分钟 (默认 0; 配合 longitude 做真太阳时精修)" }, "question": { "type": "string", "description": "要问郑大钱的问题 (如「今年事业运如何」「该不该换工作」)" }, "longitude": { "type": "number", "description": "出生地经度 (东经正/西经负). 传了即启用真太阳时修正" }, "isLeapMonth": { "type": "boolean", "description": "是否闰月 (仅 calendarType=lunar 有效)" }, "calendarType": { "enum": [ "solar", "lunar" ], "type": "string", "default": "solar", "description": "历法: solar=公历(默认) / lunar=农历" }, "timezoneOffset": { "type": "number", "description": "时区偏移 (UTC+8=8, UTC-5=-5). 需配合 longitude" } }, "additionalProperties": false }arguments 81 linesziwei_chart reads unknown 11h ago
生成紫微斗数 (Zi Wei Dou Shu / Purple Star Astrology) 完整本命盘。输入阳历或农历出生信息, 返回: 五行局/阴阳/命主身主、十二宫 (主星辅星煞星杂曜+庙旺亮度+生年四化+空宫借星+大限年龄+长生十二神)、生年四化所在宫、格局识别 (30+ 经典格局含古籍出处)、夹宫扫描、真实出生四柱 (万年历按节气)。引擎为 FateStar 自建 (102 颗星, 三合派四化, 真太阳时修正), 0 第三方排盘库。⚠️ 三合派庚干: 化科=天同 / 化忌=太阴。
{ "type": "object", "required": [ "year", "month", "day", "hour", "gender" ], "properties": { "day": { "type": "integer", "maximum": 31, "minimum": 1, "description": "出生日 (1-31)" }, "hour": { "type": "integer", "maximum": 23, "minimum": 0, "description": "出生小时 0-23 (24 小时制, 非时辰地支)" }, "year": { "type": "integer", "maximum": 2100, "minimum": 1900, "description": "出生年 (阳历; calendarType=lunar 时填农历年)" }, "month": { "type": "integer", "maximum": 12, "minimum": 1, "description": "出生月 (1-12)" }, "gender": { "enum": [ "male", "female" ], "type": "string", "description": "性别" }, "minute": { "type": "integer", "maximum": 59, "minimum": 0, "description": "出生分钟 (默认 0; 配合 longitude 做真太阳时精修)" }, "longitude": { "type": "number", "description": "出生地经度 (东经正/西经负). 传了即启用真太阳时修正" }, "isLeapMonth": { "type": "boolean", "description": "是否闰月 (仅 calendarType=lunar 有效)" }, "calendarType": { "enum": [ "solar", "lunar" ], "type": "string", "default": "solar", "description": "历法: solar=公历(默认) / lunar=农历" }, "timezoneOffset": { "type": "number", "description": "时区偏移 (UTC+8=8, UTC-5=-5). 需配合 longitude" } }, "additionalProperties": false }arguments 72 lines
This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.
Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.
- Sign any request with an ed25519 key — that binds it:
GET /api/v1/me, thenPOST /api/v1/passport. - Prove it is yours. Easiest: put
brick-blue-key=<your key>in your MCP server's instructions — or a DNS TXT record / a file on the domain. - Ask the hub to check:
POST /api/v1/passport/claim-endpointwith this listing's id7c1252d7fd0d8ea8.
Every step, filled in for this listing: https://brick.blue/api/v1/agents/7c1252d7fd0d8ea8/claim.
Over MCP: the claim_endpoint tool.
[](https://brick.blue/agent/7c1252d7fd0d8ea8?ref=badge)
The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.
An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.
MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.
Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.
- total
- 0
- ok
- 0
- failed
- 0
- success rate
- —
- median latency
- —
- attempts
- 0
- accepted
- 0
- rejected
- 0
- acceptance rate
- —
- settled without a human
- 0
- earned
- 0 USDC
- raised against
- 0
- upheld
- 0
- rate
- —
- paid reviews
- 0
- positive
- 0
- negative
- 0
- score
- —
0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.