_ registry / mcp streamable-http · checked 1h ago

qimenseek-mcp

https://qimenseek.aicreditsapi.com

Registry code: bb165d13a5da2685

api record

Free Qimen Dunjia and BaZi charts via MCP - deterministic engine, nine palaces and four pillars.

from a public catalogue that lists it, not from the operator

endpoint
https://qimenseek.aicreditsapi.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is qimenseek-mcp live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is qimenseek-mcp free to use?
Not measured yet.
What tools does qimenseek-mcp have?
2 tools: qimen_pan, bazi_chart.
Is qimenseek-mcp safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
661ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • qimen_pan unknown never probed

    Cast a Qimen Dunjia (奇门遁甲) chart for a given date/time. Deterministic engine (Zhi Run method, verified against classical case ledger). Returns the 9-palace chart, deities/stars/gates, void palaces, detected formations (geju) and a rule-based reading. FREE — no quota consumed. 中文/English via lang.

    mcp-tool

    {
      "type": "object",
      "required": [
        "date",
        "time"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "Solar date, YYYY-MM-DD"
        },
        "lang": {
          "enum": [
            "zh",
            "en"
          ],
          "type": "string",
          "description": "Output language. Default zh."
        },
        "time": {
          "type": "string",
          "description": "24h time, HH:MM"
        },
        "scene": {
          "enum": [
            "general",
            "career",
            "wealth",
            "love",
            "health",
            "travel",
            "lost"
          ],
          "type": "string",
          "description": "Question scene. Default general."
        }
      }
    }
    arguments 38 lines
  • bazi_chart unknown never probed

    Cast a BaZi (Four Pillars) natal chart. Deterministic engine (solar-term month pillar, Five-Rats hour rule, true-solar-time ready). Returns pillars with hidden stems and Ten Gods, day master strength evidence chain, geju pattern with grade, favorable/unfavorable elements, current luck cycle. FREE — no quota consumed. 中文/English via lang.

    mcp-tool

    {
      "type": "object",
      "required": [
        "birthDate",
        "birthTime"
      ],
      "properties": {
        "lang": {
          "enum": [
            "zh",
            "en"
          ],
          "type": "string",
          "description": "Output language. Default zh."
        },
        "gender": {
          "enum": [
            "male",
            "female"
          ],
          "type": "string",
          "description": "Determines luck-cycle direction. Default male."
        },
        "birthDate": {
          "type": "string",
          "description": "Birth date, YYYY-MM-DD (solar calendar)"
        },
        "birthTime": {
          "type": "string",
          "description": "Birth time, HH:MM (24h). Late Zi (23:00-23:59) uses next-day school."
        }
      }
    }
    arguments 33 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id bb165d13a5da2685.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/bb165d13a5da2685/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/bb165d13a5da2685/badge.svg)](https://brick.blue/agent/bb165d13a5da2685?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.