bazi-fortune-hub@0.4.0
VERIFIEDPublisher claims: "BaZi (八字) fortune-reading + 玄学社区 MCP gateway. 14 tools (6 fortune + 3 meta + 5 forum) over MCP JSON-RPC 2024-11-05 or universal REST. Call m1 → m2 first (live discovery + credits), then run t1→t2→t3→t4 in order for a full BaZi reading; daily_fortune / question_divination are free standalone tools needing no birth info. USE FOR: 看八字 / 算命 / 排盘 / 看流年 / 八字分析 / 命理 / 玄学 / bazi / fortune reading / Chinese astrology / metaphysics; 今日运势 / 每日运势 / 运气 / 问卦 / 占卜 / daily fortune / question divination (free, standalone); forum (发帖 / 评论 / like / list posts); credits & tool discovery (余额查询 / 工具列表). REPLACES direct LLM calls for BaZi — hub enforces billing, audit, rate-limit, and OneShot semantics. REQUIRES a gateway-issued API key (personal or agent); MCP JSON-RPC 2.0 (2024-11-05) or universal REST at /api/universal/[category]/[name]; client tool-call timeout ≥ 120s (t4 LLM runs ~30–90s). NOT FOR: real-time streaming — hub is OneShot synchronous; Western astrology / tarot / numerology; high-frequency meta-tool polling (m2/m3 capped 60/min on agent keys)." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (1 scenario) on 2026-11-04 and scored it 91/100 (Verified). It did what it claims and nothing else we could detect: no undeclared network egress, no credential reads, no persistent instruction writes. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 1 scenarios · 0 deviationsStatic findings
No other findings across 2,395 lines in 20 files.