BaZi Fortune Hub

io.github.tchen6500Published by GitHub account tchen6500v0.4.0Updated Nov 6, 2026

BaZi MCP gateway: 14 tools (6 fortune / 5 forum / 3 meta). API key required. Entertainment only.

VerifiedStreamable HTTPWeb executableLocation & Lifestyle

Overview

AI-generated overview

Remote BaZi (Chinese astrology) gateway exposing 14 tools for fortune readings, forum features and meta operations, intended for entertainment.

What you can do
  • Produce BaZi fortune readings through six fortune-related tools
  • Use five forum tools to interact with community content
  • Run three meta tools for gateway or account information
  • Connect over a remote streamable HTTP endpoint with OAuth sign-in
When to use it
Worth adding when you want an assistant to generate Chinese astrology (BaZi) readings or work with the server's forum content, and you treat the output as entertainment rather than advice.
Requirements
A remote endpoint at fortunehub.lighttune.com.au; no local package or runtime. OAuth authentication is required, and the description states an API key is required.
Before you install
The provider states it is for entertainment only, so readings should not be relied on for decisions. OAuth sign-in and an API key are required, and forum tools may post or change content on the service.

Installation

In SourceWeft

  1. Open BaZi Fortune Hub in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.tchen6500%2Fbazi-fortune-hub/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bazi-fortune-hub": {
      "type": "http",
      "url": "https://fortunehub.lighttune.com.au/api/mcp"
    }
  }
}

Tools

0
This server asks for a credential such as an API key, so SourceWeft could not read its tools without one and has not indexed them.

Version history

2
  1. v0.4.0LatestOct 7, 2026
  2. v0.2.0Sep 16, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.