Fengshui Calculator MCP

An official MCP server providing stateless access to eight feng shui computation tools including BaZi, flying stars, Kua number, and almanac data. It allows AI agents to retrieve verifiable Chinese calendar facts with cryptographic provenance, supporting clients like Claude and Cursor without requiring authentication or session management.

Visit Fengshui Calculator

Endpoint and access

No sign-in to connect and list tools. Individual tools may still need a vendor account, credentials, or permissions; check the documented prerequisites.

Vendor evidenceStreamable HTTPNo sign-inEndpoint checked 2026-11-01Operated by Fengshui Calculator

MCP endpoint (Streamable HTTP)

https://fengshuicalculator.com/v1/mcp

Vendor documentation

What you can do with it

Calculate lunar dates and zodiac signs
Generate flying star charts for feng shui analysis
Compute Kua numbers for directional guidance
Verify chart reproducibility via SHA-256 digests

Source and maintenance

Vendor evidenceRegistry 0.1.0

mcp-registry: com.fengshuicalculator/fengshui-calculator@0.1.0

Protocol and capabilities

Server: fengshuicalculator 0.1.0
MCP protocol: 2025-06-18
Tools: 11 advertised
Resources: Not advertised
Resource templates: Not advertised
Prompts: Not advertised

Server-advertised capabilities

{
  "tools": {
    "listChanged": false
  }
}

Server-provided instructions

Untrusted server output shown for inspection. It is not Koskamo guidance and is excluded from knowledge search.

Traditional Chinese calendar and feng shui computation (BaZi pillars, solar terms, Ming Gua, flying stars). All results carry provenance (engine version + ruleset + SHA-256 input digest) and are for cultural/educational use — not predictions. Docs: https://fengshuicalculator.com/docs/mcp/

Tools

11 advertised

calendar

Advertised by the server during the last successful anonymous check.

Chinese calendar for a date: lunar date (with leap month), zodiac, day officer 建除, yellow/black path, six-day cycle — computed on Beijing time

calendar input schema

{
  "type": "object",
  "required": [],
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD, 1901–2199; defaults to today (Beijing)"
    }
  }
}

ganzhi

Advertised by the server during the last successful anonymous check.

Four pillars (BaZi) for a date+hour, returned under BOTH year conventions (Lichun vs Lunar New Year) × BOTH day boundaries (midnight vs 23:00) — differences are shown, not hidden

ganzhi input schema

{
  "type": "object",
  "required": [],
  "properties": {
    "date": {
      "type": "string",
      "description": "YYYY-MM-DD"
    },
    "hour": {
      "type": "integer",
      "description": "0–23; defaults to noon"
    }
  }
}

solar_terms

Advertised by the server during the last successful anonymous check.

All 24 solar terms of a year with exact Beijing instants. Model: VSOP87D apparent solar longitude + nutation + aberration + ΔT; root tolerance 1e-7 day (~8.6 ms); verified against an independent JPL DE441-based reconstruction. ΔT and midnight-margin uncertainty flags included.

solar_terms input schema

{
  "type": "object",
  "required": [],
  "properties": {
    "year": {
      "type": "integer",
      "description": "1901–2199"
    }
  }
}

sun_position

Advertised by the server during the last successful anonymous check.

Sun azimuth/elevation for a location and instant (solar compass numeric base): azimuth 0=north clockwise, geometric vs apparent (Sæmundsson refraction) elevation, declination, hour angle, explicit polar day/night state — measurement link only, no direction is inferred from photos

sun_position input schema

{
  "type": "object",
  "required": [
    "lat",
    "lon"
  ],
  "properties": {
    "at": {
      "type": "string",
      "description": "Unix seconds or ISO 8601; defaults to now. Pass explicitly for a reproducible input_digest"
    },
    "lat": {
      "type": "number",
      "description": "latitude in degrees, [-90, 90]"
    },
    "lon": {
      "type": "number",
      "description": "longitude in degrees, [-180, 180], east-positive"
    }
  }
}

kua_number

Advertised by the server during the last successful anonymous check.

Ming Gua (Kua number) from birth date + gender, with the Lichun year boundary computed astronomically, five-yellow substitution conventions, and eight favourable/unfavourable directions

kua_number input schema

{
  "type": "object",
  "required": [
    "gender"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "birth date YYYY-MM-DD"
    },
    "hour": {
      "type": "integer"
    },
    "gender": {
      "enum": [
        "male",
        "female"
      ],
      "type": "string"
    },
    "minute": {
      "type": "integer"
    },
    "convention": {
      "enum": [
        "standard",
        "gen"
      ],
      "type": "string",
      "description": "five-yellow substitution: standard = male Kun/female Gen; gen = both Gen"
    }
  }
}

flying_star_chart

Advertised by the server during the last successful anonymous check.

Xuan Kong flying star natal chart: nine palaces with mountain/facing/period stars plus classical pattern labels (e.g. 旺山旺向). Period from a construction date, or explicit yun

flying_star_chart input schema

{
  "type": "object",
  "required": [
    "sitting"
  ],
  "properties": {
    "yun": {
      "type": "integer",
      "description": "period 1–9; omit to use the period of the reference date"
    },
    "date": {
      "type": "string",
      "description": "when yun is omitted: the construction date whose period is used"
    },
    "kind": {
      "enum": [
        "xiagua",
        "tigua"
      ],
      "type": "string"
    },
    "sitting": {
      "type": "string",
      "description": "sitting mountain: index 0–23 or Chinese name 子癸丑艮寅甲卯乙辰巽巳丙午丁未坤申庚酉辛戌乾亥壬"
    }
  }
}

yun_period

Advertised by the server during the last successful anonymous check.

San Yuan period (三元九运, 1–9) for a date; periods switch at Lichun, anchored 1984 = start of Period 7

yun_period input schema

{
  "type": "object",
  "required": [],
  "properties": {
    "date": {
      "type": "string"
    }
  }
}

rulesets

Advertised by the server during the last successful anonymous check.

List the rule sets the kernel actually implements, with parameters and honest review_state — nothing not implemented is advertised

rulesets input schema

{
  "type": "object",
  "required": [],
  "properties": {}
}

form_analysis

Advertised by the server during the last successful anonymous check.

Indoor form-sha from a floor-plan wireframe: 穿堂煞 (door-window alignment), 缺角 (nine-palace missing corners), 厕占中宫 (toilet at centre) — plus optional fusion with the Eight Mansions house stars and Ming Gua. Grade B verdicts, no aggregate score

form_analysis input schema

{
  "type": "object",
  "required": [
    "plan"
  ],
  "properties": {
    "plan": {
      "type": "object",
      "description": "floor-plan wireframe: { exterior: [[x,y]...], rooms: [{kind, polygon}], openings: [{kind, a, b, is_entry}], walls: [[a,b]...] } in meters (y axis = north by drafting convention)"
    },
    "gender": {
      "enum": [
        "male",
        "female"
      ],
      "type": "string"
    },
    "birth_year": {
      "type": "integer",
      "description": "birth year for Ming Gua (enables personal palace stars + 宅命配)"
    },
    "rotation_deg": {
      "type": "number",
      "description": "plan y-axis deviation from true north, clockwise — must come from compass measurement"
    },
    "sitting_index": {
      "type": "integer",
      "description": "sitting mountain index 0–23 (0 = 子), enables Eight Mansions fusion"
    },
    "minggua_convention": {
      "enum": [
        "standard",
        "gen"
      ],
      "type": "string"
    }
  }
}

terrain_white_tiger

Advertised by the server during the last successful anonymous check.

White tiger elevation check (白虎抬头) from a DEM-derived 360-bin skyline: compares the right (white tiger) vs left (azure dragon) sector elevation within ±45° of the sitting direction

terrain_white_tiger input schema

{
  "type": "object",
  "required": [
    "skyline_360",
    "sitting_azimuth_deg"
  ],
  "properties": {
    "skyline_360": {
      "type": "array",
      "items": {
        "type": "number"
      },
      "description": "360 elevation angles (degrees), one per azimuth degree"
    },
    "sitting_azimuth_deg": {
      "type": "number",
      "description": "sitting direction azimuth (0 = north, clockwise)"
    }
  }
}

replay

Advertised by the server during the last successful anonymous check.

Verifiability as an API call: recompute a stored request and compare its SHA-256 input digest (JCS-canonicalised) against an expected value — byte-identical reproduction or honest mismatch

replay input schema

{
  "type": "object",
  "required": [
    "request"
  ],
  "properties": {
    "request": {
      "type": "object",
      "description": "the original kernel request JSON"
    },
    "engine_version": {
      "type": "string",
      "description": "snapshot engine version; mismatch → 409-style error"
    },
    "expected_input_digest": {
      "type": "string",
      "description": "64-hex SHA-256 from the report being verified"
    }
  }
}

Prompts

Not advertised

No prompt definitions available.

Resources

Not advertised

No resource definitions available.

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks: 1 of 1 (100%)
Average latency: 967 ms
95th percentile latency: 967 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

Nov 1, 2026, 7:33 AM UTC · probe · passed · 967 ms · metadata changed · 11 tool(s)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http fengshui-calculator-mcp https://fengshuicalculator.com/v1/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add fengshui-calculator-mcp --url https://fengshuicalculator.com/v1/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable fengshui-calculator-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "fengshui-calculator-mcp": {
      "url": "https://fengshuicalculator.com/v1/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).

Cline configuration

{
  "mcpServers": {
    "fengshui-calculator-mcp": {
      "type": "streamableHttp",
      "url": "https://fengshuicalculator.com/v1/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start fengshui-calculator-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "fengshui-calculator-mcp": {
      "type": "http",
      "url": "https://fengshuicalculator.com/v1/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http fengshui-calculator-mcp https://fengshuicalculator.com/v1/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "fengshui-calculator-mcp": {
      "url": "https://fengshuicalculator.com/v1/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "fengshui-calculator-mcp": {
      "serverUrl": "https://fengshuicalculator.com/v1/mcp"
    }
  }
}

Let your agent find its tools

Find servers like Fengshui Calculator MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows

Do you run Fengshui Calculator MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing