# io.github.douglasgan/asktian (npm · @asktian/mcp-server)

Chinese metaphysics (bazi, qimen, 5-element) as decision-support tools for AI agents.

- Trust score: 68/100 (medium)
- Change this week: +23
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.asktian.com`: 68/100, [markdown](https://verifymcp.io/servers/douglasgan-asktian/mcp.md), [page](https://verifymcp.io/servers/douglasgan-asktian/mcp)
- npm · `@asktian/mcp-server`: 68/100 (this document), [markdown](https://verifymcp.io/servers/douglasgan-asktian/asktian-mcp-server.md), [page](https://verifymcp.io/servers/douglasgan-asktian/asktian-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@asktian/mcp-server`
- Version: `0.3.3`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 43 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 907 tokens (~151/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add douglasgan-asktian -- npx -y @asktian/mcp-server
```

### Codex

```bash
codex mcp add douglasgan-asktian -- npx -y @asktian/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "douglasgan-asktian": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@asktian/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add douglasgan-asktian --command npx --arg -y --arg @asktian/mcp-server
```

### Hermes

```yaml
mcp_servers:
  douglasgan-asktian:
    command: "npx"
    args: ["-y", "@asktian/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "douglasgan-asktian": {
      "command": "npx",
      "args": [
        "-y",
        "@asktian/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 68, +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.

### 2026-08-02 (score 67, +18)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Capabilities: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.23
- [functional improvement] License: unverified → pass
- [functional] Licence: MIT

### 2026-08-01 (score 49, +29)

- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] Security disclosure: unverified → fail
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Tool coverage: unverified → 100

### 2026-07-31 (score 20, +14)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 6, −72)

- [security regression] Known CVEs: partial → unverified
- [security regression] Malware scan: pass → unverified
- [security regression] Provenance: fail → unverified
- [security regression] Install scripts: pass → unverified
- [functional regression] Security disclosure: fail → unverified
- [functional regression] Maintenance: pass → unverified
- [functional regression] License: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional regression] Dependency health: partial → unverified
- [functional] Licence: MIT

### 2026-07-29 (score 78, +53)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional] Licence: MIT

### 2026-07-28 (score 25, −20)

- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Dependency health: unverified → partial
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 45)

First indexed and scored.

## MCP tools (6)

### `asktian_daily_reading` (~160 tokens)

Get today's personalized Chinese metaphysics (八字 bazi + 干支 daily energy) reading for a person. Returns their archetype (one of 8 trigrams 八卦), today's energy, favorable colors/direction/hours, headline advice, and any caution. Use this when the user asks how today will be for them, what colors to wear, where to face their desk, or for general daily guidance.

Input parameters:

- `birth_hour` (string): Optional 24h time HH:MM. If unknown, omit (defaults to noon).
- `birthdate` (string, required): ISO date YYYY-MM-DD (Gregorian calendar).
- `gender` (string): Optional. Some metaphysics traditions weigh gender; pass 'any' if unsure.

### `asktian_compatibility` (~152 tokens)

Compute fate compatibility between two people via Chinese metaphysics (八字 pairing, 5-element generation/clash). Returns qualitative label first (e.g. '互补型 Complementary'), then a numeric score (hidden if <60 to avoid making low-compat feel like rejection — this is intentional per the asktian design principles). Useful when user asks about compatibility, fit, or 'will this person and I work'.

Input parameters:

- `dimension` (string): Which dimension to weight. Default 'general'.
- `person_a_birthdate` (string, required): ISO YYYY-MM-DD birthdate of the first person.
- `person_b_birthdate` (string, required): ISO YYYY-MM-DD birthdate of the second person.

### `asktian_best_time_for_action` (~175 tokens)

Find the most auspicious time windows in the next N days for a specific action. Use this when the user asks 'when should I do X', 'should I move this meeting', 'is tomorrow a good day to launch', 'when should I have the hard conversation', etc. Returns top 3 best windows and any windows to avoid. This is the most useful tool for real-time decision support inside any AI assistant — it lets you give specific scheduling advice instead of vague reflections.

Input parameters:

- `action` (string): What kind of action. Pick the closest match; use 'generic' if unsure.
- `birthdate` (string, required): ISO YYYY-MM-DD birthdate of the person taking the action.
- `range_days` (number): How many days ahead to search. Default 7. Max 30.

### `asktian_today_energy` (~100 tokens)

Get today's GENERAL energy (no person needed) — the 干支 (stem + branch) and the dominant 5-element character of the day. Useful when the user asks 'what kind of day is it', 'what's the energy today', or when an AI agent wants to add cosmic context to a generic suggestion without needing the user's birthdate.

Input parameters:

- `date` (string): Optional ISO YYYY-MM-DD. Defaults to today (UTC).

### `asktian_name_analysis` (~96 tokens)

Quick energetic profile of a name (姓名学 name-analysis). Useful when the user asks about someone's name, a baby name, a company name, or 'what kind of person is X' when no birthdate is available. Returns a one-line vibe + dominant element guess.

Input parameters:

- `language` (string): Language hint. Default 'auto'.
- `name` (string, required): The name to analyze. Can be in any script.

### `asktian_market_read` (~224 tokens)

Get a Chinese-metaphysics signal on a binary prediction-market question (Polymarket/Kalshi style yes/no outcomes). Use when a user — or a trading agent — wants an UNCORRELATED, for-fun read on a market: 'will X happen by date Y'. Returns a lean (yes/no/neutral), a confidence, the 五行 reasoning from the resolution date's energy, and a mandatory disclaimer. This is ENTERTAINMENT and a falsifiable ritual — NOT financial advice. Always present it as a novelty signal, never as a recommendation to place a bet.

Input parameters:

- `question` (string, required): The binary market question, e.g. 'Will BTC be above $100k by 2026-12-31?'
- `resolve_date` (string): Optional ISO YYYY-MM-DD when the market resolves. Defaults to today.
- `subject_birthdate` (string): Optional ISO YYYY-MM-DD. If the market is about a specific person (e.g. 'will X win'), their birthdate adds their bazi element to the read.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/douglasgan-asktian/asktian-mcp-server#diagnostics

## Score history

- 2026-08-03: 68
- 2026-08-02: 67
- 2026-08-01: 49
- 2026-07-31: 20
- 2026-07-30: 6
- 2026-07-29: 78
- 2026-07-28: 25
- 2026-07-27: 45

## Links

- npm package: https://www.npmjs.com/package/@asktian/mcp-server
- Socket report: https://socket.dev/npm/package/@asktian/mcp-server
- Repository: https://github.com/douglasgan/asktian-mcp
- Website: https://asktian.com/agents
- Changelog RSS feed: https://verifymcp.io/servers/douglasgan-asktian/asktian-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/douglasgan-asktian/asktian-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/douglasgan-asktian/asktian-mcp-server