Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

QimenMind Qimen Dunjia Chart

REMOTE · WWW.QIMENMIND.COM

Cast Qimen Dunjia (奇门遁甲) charts: four pillars, Ju, nine palaces, stars, doors and deities.

+3 this week 82 Trust /100

Last scanned (22 hours ago)

Scores higher than 85% of remote servers

Reachable. Last reached 4 Nov 2026.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 326 tokens (~163/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 33% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

  • 31 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

  • 28 Oct 26 +1
    • Tool “qimen_chart” rewrote its description, which is the text the model reads security
    • Tool “qimen_chart_now” rewrote its description, which is the text the model reads security
    • Schema quality: pass → fail ▼ functional
    • Schema quality: good → excellent functional
    • “qimen_chart” reworded the description of “hour” cosmetic
    • “qimen_chart_now” reworded the description of “timezone” cosmetic
  • 27 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

  • 25 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 22 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Probed https://www.qimenmind.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.qimenmind.com CN=YR1,O=Let's Encrypt,C=US 13 Sept 2026 12 Dec 2026 RSA 2048 SHA256-RSA 62a5372dc3a466ddf2dd955ce0d92fbc2b9
SANs: www.qimenmind.com
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of www.qimenmind.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
qimenmind.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'none'; base-uri 'self'; object-src 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.qimenmind.com/api/mcp Verified 200
http (plaintext) http://www.qimenmind.com/api/mcp HTTPS enforced 308 https://www.qimenmind.com/api/mcp
MCP tools · 2 exposed · ~283 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
qimen_chart ~178

Cast a Qimen Dunjia (奇门遁甲) hour chart (Chaibu bureau method, rotating plate) for a date and time in Beijing time (Asia/Shanghai, UTC+8), the same reference QimenMind uses for question charts. Convert other local times to UTC+8 first; no location or true-solar-time correction is applied. Returns the four pillars, Yin/Yang Dun and Ju number, Zhi Fu / Zhi Shi, and the nine palaces with heaven/earth stems, star, door, deity, 81-pattern name, void and horse markers.

NameTypeReqDescription
dayintegeryes–
hourintegeryesHour (24h) in Beijing time (UTC+8).
minuteinteger––
monthintegeryes–
yearintegeryes–

No output schema declared.

No examples provided.

qimen_chart_now ~105

Cast the Qimen Dunjia chart for the current moment. By default it uses the current Beijing time (Asia/Shanghai), matching QimenMind question charts; passing another IANA timezone casts with that zone's wall-clock time instead, which can give a different chart. Use this when the user asks about a matter right now.

NameTypeReqDescription
timezonestring–IANA timezone whose wall-clock time is used. The default Asia/Shanghai matches QimenMind question charts.

No output schema declared.

No examples provided.

Install

How do I install the QimenMind Qimen Dunjia Chart MCP server?

QimenMind Qimen Dunjia Chart is a hosted endpoint at https://www.qimenmind.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · www.qimenmind.com

# add to Claude Code
claude mcp add --transport http xlw-pro-qimenmind 'https://www.qimenmind.com/api/mcp'
Common questions

What is the QimenMind Qimen Dunjia Chart MCP server?

QimenMind Qimen Dunjia Chart is an MCP server listed in the public MCP registry as io.github.xlw-pro/qimenmind. Cast Qimen Dunjia (奇门遁甲) charts: four pillars, Ju, nine palaces, stars, doors and deities. This page covers its hosted endpoint (https://www.qimenmind.com/api/mcp).

Is the QimenMind Qimen Dunjia Chart MCP server safe to use?

QimenMind Qimen Dunjia Chart scores 82 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the QimenMind Qimen Dunjia Chart MCP server expose?

QimenMind Qimen Dunjia Chart exposes 2 tools: qimen_chart, qimen_chart_now. Their descriptions and schemas cost roughly 283 tokens of context every time the server is loaded.

Does the QimenMind Qimen Dunjia Chart MCP server require authentication?

No. We connected to QimenMind Qimen Dunjia Chart without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the QimenMind Qimen Dunjia Chart MCP server still maintained?

QimenMind Qimen Dunjia Chart is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.