MCP Server for AI Agents 模型上下文協議

Q: What is the MCP endpoint URL?

https://fengshuicalculator.com/v1/mcp — a stateless streamable-HTTP MCP server speaking JSON-RPC 2.0. No key, no session, no install.

One URL gives Claude, Cursor and any MCP client eight feng shui computation tools — the same kernel, the same provenance, no key and no session: https://fengshuicalculator.com/v1/mcp

Protocol: MCP streamable HTTP, stateless subset (JSON-RPC 2.0 per POST) · Version: 2025-06-18

Client setup

Claude Desktop / Claude.ai

Settings → Connectors → Add custom connector → URL: https://fengshuicalculator.com/v1/mcp. The connector initializes and lists tools automatically.

Cursor

Settings → MCP → Add new global MCP server — either the URL form, or the JSON form:

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

Any other MCP client

Streamable HTTP endpoint, POST JSON-RPC 2.0. Supported methods: initialize, notifications/initialized, ping, tools/list, tools/call. Responses are plain JSON (no SSE stream) — the stateless subset; sessions are neither created nor required.

$ curl -X POST https://fengshuicalculator.com/v1/mcp \
    -H 'Content-Type: application/json' \
    -d '{"jsonrpc":"2.0","id":1,"method":"tools/call",
         "params":{"name":"kua_number",
                   "arguments":{"date":"2024-02-03","gender":"male"}}}'

The tool catalogue

calendar(date) — lunar date with leap month, zodiac, day officer, yellow/black path.
ganzhi(date, hour) — four pillars under both year conventions × both day boundaries; differences shown, never hidden.
solar_terms(year) — 24 exact instants, DE441-based, with ΔT and midnight margins.
kua_number(date, hour, minute, gender, convention) — Ming Gua with the astronomical Lichun boundary and eight favourable/unfavourable directions.
flying_star_chart(sitting, yun?, date?, kind?) — nine-palace chart with pattern labels; yun derived from date when omitted.
yun_period(date) — San Yuan period for a date (Lichun boundary, anchor 1984).
rulesets() — what the kernel actually implements, with honest review_state.
replay(request, expected_input_digest?, engine_version?) — the verification tool: an agent can recompute any stored chart and prove the digest matches, byte for byte.

Every tool result embeds provenance (engine version, ruleset id, SHA-256 input digest) and the cultural/educational disclaimer — so downstream answers can cite exactly which engine version and rules computed them. Agents doing fortune-telling claims is exactly what the disclaimer exists for; computation yes, predictions no.

Protocol notes (the honest bits)

Stateless by design. No sessions, no SSE, no subscriptions. If your client requires streamable SSE or session headers, this server will not satisfy it — plain JSON responses only.
No auth required. Same fair-use gate as the REST API (about 60 requests burst per client IP per instance, 429 with Retry-After beyond it). Pro subscribers may send their license key as Authorization: Bearer … for a 600-burst bucket. No tool arguments are logged or stored.
Tool errors come back as isError: true with the endpoint's error JSON as content, not as JSON-RPC protocol errors — compute failures stay inside the tool result where agents can read them.
What it's for: agents that need correct Chinese-calendar facts with checkable provenance — not agents promising destiny. The digest format makes every number citable.

FAQ

What is the MCP endpoint URL?

https://fengshuicalculator.com/v1/mcp — a stateless streamable-HTTP MCP server speaking JSON-RPC 2.0. No key, no session, no install.

How do I add it to Claude Desktop or Cursor?

Add an MCP server entry of type URL (streamable HTTP) pointing at the endpoint. In Claude Desktop: Settings → Connectors → Add custom connector. In Cursor: MCP settings → Add server → type URL.

Which tools does the server expose?

Eight: calendar, ganzhi (four pillars under both conventions), solar_terms, kua_number, flying_star_chart, yun_period, rulesets, and replay — the digest-verification tool that lets an agent prove a chart reproduces byte-for-byte.

Does it keep sessions or state?

No. Each POST is independent JSON-RPC — the stateless subset of streamable HTTP. Nothing about your queries is stored; there is no account and no logging of tool arguments.

Docs home · REST reference · Fingerprint format · Verify a chart in the browser · Methodology