Xuanxue Bazi Matching
Wire deterministic Chinese metaphysics APIs (BaZi, QiMen, and related systems) into an agent app with optional x402 USDC pay-per-call on Base.
Overview
Xuanxue BaZi Matching MCP is a Build-phase MCP server that connects agents to six deterministic Chinese divination APIs with optional x402 USDC billing on Base.
What is this MCP server?
- Six deterministic API families: BaZi, QiMen, ZiWei, MeiHua, LiuYao, LiuRen
- x402 on Base: omit token for 402 Payment Required with instructions, or set XUANXUE_PAYMENT_TOKEN for USDC pay-per-call
- Default API base https://api.decodeyourming.com (override with XUANXUE_API_BASE)
- npm package xuanxue-bazi-matching with stdio MCP transport
- Version 0.2.0 registry entry for agent-side invocation
- 6 named divination API systems in the server description
- Server version 0.2.0
- Default API host https://api.decodeyourming.com
What problem does it solve?
You want BaZi-style calculations inside an agent workflow but do not want to maintain HTTP clients and payment challenge handling yourself.
Who is it for?
Solo builders shipping agent or API products that need licensed BaZi/QiMen-style endpoints and are fine with x402 on Base.
Skip if: General SaaS teams with no metaphysics feature requirement or those avoiding pay-per-call crypto billing.
What do I get? / Deliverables
After registration, your agent can call structured divination APIs through MCP with documented defaults and optional token-based payment.
- Agent-callable tools backed by six divination API systems
- Configurable remote API base URL
- Payment-required or token-authenticated call flow per x402 design
Recommended MCP Servers
Journey fit
Paid third-party API MCP servers belong on Build → integrations where solo builders connect external services into agents or products. This server is a thin MCP bridge to hosted divination endpoints with billing hooks—not infra or docs—so integrations is the right shelf.
How it compares
Specialized paid API MCP bridge, not a general LLM tool or local inference server.
Common Questions / FAQ
Who is Xuanxue BaZi Matching MCP for?
Developers building apps or agents that need deterministic Chinese divination APIs exposed via Model Context Protocol.
When should I use Xuanxue BaZi Matching MCP?
Use it during integration when your feature set requires BaZi, QiMen, ZiWei, MeiHua, LiuYao, or LiuRen calls from Claude Code or similar clients.
How do I add Xuanxue BaZi Matching MCP to my agent?
Add the npm stdio server xuanxue-bazi-matching to your MCP config, set XUANXUE_PAYMENT_TOKEN if you want paid calls, and optionally override XUANXUE_API_BASE.