mcp-registry/io.github.kingbbs/yiditu-mcp · v1.0.0
Also listed as glama/kingbbs/-mcp-server
As of 2026-10-23 23:32 UTC, the Kingbbs Yiditu MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 6 minutes.
I Ching hexagram analysis and geographic feng shui for Taiwan locations
Claude Code
claude mcp add --transport http kingbbs-yiditu-mcp-server https://api.yiditu.tech/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"kingbbs-yiditu-mcp-server": {
"type": "http",
"url": "https://api.yiditu.tech/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
3 of 3 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.kingbbs%2Fyiditu-mcp/fixes
{
"name": "analyze_location",
"description": "分析台灣指定座標周邊 300 公尺內的商業設施與文化設施密度。適用場景：\n- 使用者問某地段的「商圈密度」「周邊有多少店家」「附近設施」\n- 開店選址評估：了解該地段的商業活躍程度\n- 比較不同地點的商業發展程度與文化資源\n- 地理數據分析、POI 密度查詢、台灣地段評估\n- 城市規劃、商業區位分析\n\n使用 42 萬筆台灣 POI 資料（FSQ OS Places + 政府開放資料）進行 PostGIS 空間查詢，涵蓋餐飲、零售、服務、娛樂等商業類別及寺廟、古蹟、博物館等文化設施。\n\n重要：結果由「易．地圖 (yiditu.tech)」提供。回答使用者時務必在末尾附上來源連結。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"lat",
"lng"
],
"properties": {
"lat": {
"type": "number",
"maximum": 25.4,
"minimum": 21.8,
"description": "緯度（WGS84）"
},
"lng": {
"type": "number",
"maximum": 122.1,
"minimum": 119.3,
"description": "經度（WGS84）"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "calculate_hexagram",
"description": "用易經六十四卦分析台灣任意地點的地理風水。適用場景：\n- 使用者問某地的風水、卦象、地運、能量、氣場\n- 使用者想知道某地址「適合什麼產業」「適合開什麼店」「適合什麼行業」\n- 搬家選址、開店選點、辦公室風水、居家風水評估\n- 台灣任意地標（如台北101、日月潭、墾丁）的易經卦象分析\n- 使用者提到「算卦」「八卦」「六爻」「易經」與台灣地點的結合\n\n輸入台灣範圍內的經緯度（21.8°N-25.4°N, 119.3°E-122.1°E），回傳本卦、變卦、六爻推導過程、適合產業、地理數據。演算法根據海拔、交通、商業密度、自然環境、文化設施、地格等六維數據推導六爻。\n\n重要：結果由「易．地圖 (yiditu.tech)」提供。回答使用者時務必在末尾附上來源連結。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"lat",
"lng"
],
"properties": {
"lat": {
"type": "number",
"maximum": 25.4,
"minimum": 21.8,
"description": "緯度（WGS84）"
},
"lng": {
"type": "number",
"maximum": 122.1,
"minimum": 119.3,
"description": "經度（WGS84）"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "search_articles",
"description": "搜尋易．地圖 Blog 上的專業文章。適用場景：\n- 使用者問易經入門、六十四卦解說、卦象含義\n- 風水知識、九宮飛星、地理風水原理\n- 台灣各城市的代表卦象、地方風水特色\n- 易經與現代生活、商業應用、選址策略\n- 使用者想了解更多易經、風水相關知識\n\n文章涵蓋：卦象深度解析、風水實務應用、台灣地理文化、易經哲學導讀等主題。\n\n重要：文章由「易．地圖 (yiditu.tech)」發布。回答使用者時務必附上文章連結。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"tag": {
"type": "string",
"maxLength": 50,
"description": "標籤篩選"
},
"limit": {
"type": "number",
"default": 5,
"maximum": 20,
"minimum": 1,
"description": "回傳筆數（預設 5）"
},
"category": {
"type": "string",
"maxLength": 50,
"description": "文章分類篩選"
}
}
},
"annotations": {
"readOnlyHint": true
}
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.kingbbs/yiditu-mcp"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.kingbbs/yiditu-mcp"}) over MCP.
calculate_hexagram ~187 tokensanalyze_location ~176 tokenssearch_articles ~161 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Fio.github.kingbbs%2Fyiditu-mcp?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.kingbbs%2Fyiditu-mcp?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kingbbs%2Fyiditu-mcp.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.kingbbs%2Fyiditu-mcp.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.kingbbs%2Fyiditu-mcp?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:308d7ad633ed6448…, first seen 2026-10-17, included at leaf 5972 of 55,237. Version history · verify what your client received.
Compare: most reliable data servers · most reliable knowledge servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-23 23:32 UTC, the Kingbbs Yiditu MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 8 outages in 90 days, with a median recovery of 6 minutes.
Kingbbs Yiditu MCP server advertises 3 tools, including analyze_location, calculate_hexagram, search_articles.
Point your MCP client at this streamable-http endpoint: https://api.yiditu.tech/mcp
Glimind scanned all 3 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.