# True Solar Time (npm · true-solar-time-mcp)

True solar time correction for BaZi charts: historical DST, longitude, equation of time.

- Trust score: 79/100 (medium)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- npm · `true-solar-time-mcp`: 79/100 (this document), [markdown](https://verifymcp.io/servers/shann5-true-solar-time/true-solar-time-mcp.md), [page](https://verifymcp.io/servers/shann5-true-solar-time/true-solar-time-mcp)

## Channel facts

- Registry: `npm`
- Package: `true-solar-time-mcp`
- Version: `1.0.1`
- 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-09-24.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 96 dependencies flagged as unhealthy.
- **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 31 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 (good).
  - Context-footprint check failed: tool/resource definitions use about 303 tokens (~151/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 81/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 44% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the True Solar Time MCP server?

True Solar Time runs locally as an npm package, launched with npx -y true-solar-time-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add shann5-true-solar-time -- npx -y true-solar-time-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "shann5-true-solar-time": {
      "command": "npx",
      "args": [
        "-y",
        "true-solar-time-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "shann5-true-solar-time": {
      "command": "npx",
      "args": [
        "-y",
        "true-solar-time-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add shann5-true-solar-time -- npx -y true-solar-time-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "shann5-true-solar-time": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "true-solar-time-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add shann5-true-solar-time --command npx --arg -y --arg true-solar-time-mcp
```

### Hermes

```yaml
mcp_servers:
  shann5-true-solar-time:
    command: "npx"
    args: ["-y", "true-solar-time-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "shann5-true-solar-time": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "true-solar-time-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add shann5-true-solar-time -t stdio -c npx -a -y true-solar-time-mcp
```

### Other

```json
{
  "mcpServers": {
    "shann5-true-solar-time": {
      "command": "npx",
      "args": [
        "-y",
        "true-solar-time-mcp"
      ]
    }
  }
}
```

## 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-09-23 (score 79, −3)

- [functional] Stability: pass → 0.80

### 2026-09-22 (score 82, +1)

- [security] Stability: 0.97 → pass

### 2026-09-20 (score 81, +1)

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

### 2026-09-18 (score 80, +1)

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

### 2026-09-16 (score 79, +1)

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

### 2026-09-14 (score 78, +1)

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

### 2026-09-12 (score 77, +1)

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

### 2026-09-09 (score 76, +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.

## MCP tools (2)

### `true_solar_time` (~231 tokens)

True solar time correction

Convert a recorded birth time (wall clock + IANA time zone + longitude) into true solar time — the time a BaZi / Four Pillars chart should actually be cast from. Returns the corrected instant, the total correction decomposed into DST + longitude + equation-of-time (the three always sum exactly), the resulting two-hour branch, distance to the nearest branch boundary, and whether the reported clock time even existed (spring-forward DST gaps, e.g. China 1986–91). Deterministic: same input, same output, every time.

Input parameters:

- `day` (integer, required)
- `hour` (integer, required): Recorded wall-clock hour, 24h
- `longitude` (number, required): Birthplace longitude in degrees, east positive (Ürümqi ≈ 87.6, Vancouver ≈ -123.1)
- `minute` (integer, required)
- `month` (integer, required)
- `timeZone` (string, required): IANA time zone of the birthplace, e.g. 'Asia/Shanghai', 'America/Vancouver'
- `year` (integer, required): Birth year (Gregorian)

### `hour_branch` (~72 tokens)

Hour branch of a clock time

Which two-hour branch (子丑寅卯…) a given time falls in, and how many minutes it sits from the nearest branch boundary. Use on an already-corrected time; for raw birth records use true_solar_time.

Input parameters:

- `hour` (integer, required)
- `minute` (integer, required)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/shann5-true-solar-time/true-solar-time-mcp#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 79
- 2026-09-22: 82
- 2026-09-21: 81
- 2026-09-20: 81
- 2026-09-19: 80
- 2026-09-18: 80
- 2026-09-17: 79
- 2026-09-16: 79
- 2026-09-15: 78
- 2026-09-14: 78
- 2026-09-13: 77
- 2026-09-12: 77
- 2026-09-11: 76
- 2026-09-10: 76
- 2026-09-09: 76
- 2026-09-08: 75
- 2026-09-07: 75
- 2026-09-06: 74
- 2026-09-05: 74
- 2026-09-04: 73
- 2026-09-03: 73
- 2026-09-02: 72
- 2026-09-01: 72
- 2026-08-31: 71
- 2026-08-30: 68
- 2026-08-29: 68
- 2026-08-28: 68
- 2026-08-27: 68
- 2026-08-26: 68

## Common questions

### What is the True Solar Time MCP server?

True Solar Time is an MCP server listed in the public MCP registry as io.github.Shann5/true-solar-time. True solar time correction for BaZi charts: historical DST, longitude, equation of time. This page covers its npm package (true-solar-time-mcp).

### Is the True Solar Time MCP server safe to use?

True Solar Time scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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 True Solar Time MCP server expose?

True Solar Time exposes 2 tools: true_solar_time, hour_branch. Their descriptions and schemas cost roughly 303 tokens of context every time the server is loaded.

### Is the True Solar Time MCP server still maintained?

True Solar Time is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the True Solar Time MCP server under?

True Solar Time declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/true-solar-time-mcp
- Socket report: https://socket.dev/npm/package/true-solar-time-mcp
- Repository: https://github.com/Shann5/true-solar-time-mcp
- Website: https://auspiceoracle.com/en/content/true-solar-time
- Changelog RSS feed: https://verifymcp.io/servers/shann5-true-solar-time/true-solar-time-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/shann5-true-solar-time/true-solar-time-mcp.json
- HTML version of this page: https://verifymcp.io/servers/shann5-true-solar-time/true-solar-time-mcp