True Solar Time
NPM · TRUE-SOLAR-TIME-MCP · SCANNED SEP 24
True solar time correction for BaZi charts: historical DST, longitude, equation of time.
Available components
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage81
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 44% 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 2 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
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.
npm · true-solar-time-mcp
claude mcp add shann5-true-solar-time -- npx -y true-solar-time-mcp
{
"mcpServers": {
"shann5-true-solar-time": {
"command": "npx",
"args": [
"-y",
"true-solar-time-mcp"
]
}
}
} {
"servers": {
"shann5-true-solar-time": {
"command": "npx",
"args": [
"-y",
"true-solar-time-mcp"
]
}
}
} codex mcp add shann5-true-solar-time -- npx -y true-solar-time-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"shann5-true-solar-time": {
"type": "local",
"command": [
"npx",
"-y",
"true-solar-time-mcp"
],
"enabled": true
}
}
} openclaw mcp add shann5-true-solar-time --command npx --arg -y --arg true-solar-time-mcp
mcp_servers:
shann5-true-solar-time:
command: "npx"
args: ["-y", "true-solar-time-mcp"] {
"McpServers": {
"shann5-true-solar-time": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"true-solar-time-mcp"
]
}
}
} assistant mcp add shann5-true-solar-time -t stdio -c npx -a -y true-solar-time-mcp
{
"mcpServers": {
"shann5-true-solar-time": {
"command": "npx",
"args": [
"-y",
"true-solar-time-mcp"
]
}
}
} 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.
- 23 Sept 26 −3
- Stability: pass → 0.80 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 9 Sept 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.
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 24 Sept 2026 · Analysed npm/true-solar-time-mcp@1.0.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
hour_branch Hour branch of a clock time ~72
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.
| Name | Type | Req | Description |
|---|---|---|---|
| hour | integer | yes | – |
| minute | integer | yes | – |
No output schema declared.
No examples provided.
true_solar_time True solar time correction ~231
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.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | yes | – |
| hour | integer | yes | Recorded wall-clock hour, 24h |
| longitude | number | yes | Birthplace longitude in degrees, east positive (Ürümqi ≈ 87.6, Vancouver ≈ -123.1) |
| minute | integer | yes | – |
| month | integer | yes | – |
| timeZone | string | yes | IANA time zone of the birthplace, e.g. 'Asia/Shanghai', 'America/Vancouver' |
| year | integer | yes | Birth year (Gregorian) |
No output schema declared.
No examples provided.
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.