# io.github.breezefeng/deepnatal (npm · deepnatal)

Natal charts cross-verified three ways. Refuses to answer rather than guess.

- Trust score: 90/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- npm · `deepnatal`: 90/100 (this document), [markdown](https://verifymcp.io/servers/breezefeng-deepnatal/deepnatal.md), [page](https://verifymcp.io/servers/breezefeng-deepnatal/deepnatal)

## Channel facts

- Registry: `npm`
- Package: `deepnatal`
- Version: `0.1.2`
- 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-21.

- **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.
  - 34 of 101 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to breezefeng/deepnatal).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 22 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 913 tokens (~228/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 io.github.breezefeng/deepnatal MCP server?

io.github.breezefeng/deepnatal runs locally as an npm package, launched with npx -y deepnatal. 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 breezefeng-deepnatal -- npx -y deepnatal
```

### Cursor

```json
{
  "mcpServers": {
    "breezefeng-deepnatal": {
      "command": "npx",
      "args": [
        "-y",
        "deepnatal"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "breezefeng-deepnatal": {
      "command": "npx",
      "args": [
        "-y",
        "deepnatal"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add breezefeng-deepnatal -- npx -y deepnatal
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add breezefeng-deepnatal --command npx --arg -y --arg deepnatal
```

### Hermes

```yaml
mcp_servers:
  breezefeng-deepnatal:
    command: "npx"
    args: ["-y", "deepnatal"]
```

### Netclaw

```json
{
  "McpServers": {
    "breezefeng-deepnatal": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "deepnatal"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add breezefeng-deepnatal -t stdio -c npx -a -y deepnatal
```

### Other

```json
{
  "mcpServers": {
    "breezefeng-deepnatal": {
      "command": "npx",
      "args": [
        "-y",
        "deepnatal"
      ]
    }
  }
}
```

## 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-20 (score 90, +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-18 (score 89, +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-15 (score 88, +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.

### 2026-09-13 (score 87, +1)

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

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

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

### 2026-09-07 (score 84, +1)

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

### 2026-09-06 (score 83, +3)

- [functional improvement] Stability: unverified → 0.27

## MCP tools (4)

### `calculate_natal_chart` (~222 tokens)

Calculate a natal chart

Compute a full natal/birth chart: ten planets with sign, degree, house and retrograde status, plus ascendant, midheaven and twelve house cusps. Every result is cross-checked by two independent astronomy implementations and the call FAILS rather than returning a chart when they disagree. Use this whenever a user asks for a birth chart, rising sign, or planetary placements — do not attempt the arithmetic yourself. Requires an exact birth time; if the time is unknown use calculate_chart_without_birth_time instead.

Input parameters:

- `date` (string, required): Local birth date at the birthplace, YYYY-MM-DD.
- `latitude` (number, required): Birthplace latitude, decimal degrees.
- `longitude` (number, required): Birthplace longitude, decimal degrees.
- `time` (string, required): Local clock time at the birthplace, HH:mm 24-hour, as written on the birth record.
- `timezone` (string, required): IANA timezone of the BIRTHPLACE, e.g. Asia/Taipei. Never the user's current zone — people are routinely asked about a birth in another country.

### `calculate_chart_without_birth_time` (~192 tokens)

Calculate a chart without a birth time

For users who do not know their birth time. Returns only what is genuinely knowable without it, and explicitly lists what is not: ascendant, midheaven and all house positions are omitted with reasons rather than estimated. Also reports whether the Moon changed sign during that day — it does on nearly half of all dates, which means the moon sign itself is undetermined without a time. Never substitute noon and present the result as fact; that is exactly what this tool exists to prevent.

Input parameters:

- `date` (string, required): Local birth date at the birthplace, YYYY-MM-DD.
- `latitude` (number, required): Birthplace latitude, decimal degrees.
- `longitude` (number, required): Birthplace longitude, decimal degrees.
- `timezone` (string, required): IANA timezone of the BIRTHPLACE, e.g. Asia/Taipei. Never the user's current zone — people are routinely asked about a birth in another country.

### `verify_ascendant` (~286 tokens)

Independently verify an ascendant

Recompute the ascendant along a third path that imports no astrology library at all — pure spherical geometry, the intersection of the ecliptic with the eastern horizon — and report how far it lands from the primary engine. Optionally pass a value produced ELSEWHERE (another website, an app, a printed chart) as `claim` and this will tell you whether it holds up and, when it does not, name the likely cause. Use this when a user says two sites disagree about their rising sign, doubts a result, or asks which one is correct. Accepts claims like "Virgo", "處女座", "12 Leo", "Leo 12°34'" or a bare ecliptic longitude.

Input parameters:

- `claim` (string): Optional ascendant produced by some other tool, to be checked against this engine.
- `date` (string, required): Local birth date at the birthplace, YYYY-MM-DD.
- `latitude` (number, required): Birthplace latitude, decimal degrees.
- `longitude` (number, required): Birthplace longitude, decimal degrees.
- `time` (string, required): Local clock time at the birthplace, HH:mm 24-hour, as written on the birth record.
- `timezone` (string, required): IANA timezone of the BIRTHPLACE, e.g. Asia/Taipei. Never the user's current zone — people are routinely asked about a birth in another country.

### `inspect_historical_timezone` (~213 tokens)

Inspect historical timezone and DST

Resolve a local birth date and time to UTC using historical timezone rules, and report whether daylight saving time was actually in effect on that date. This is the single most common source of wrong charts: many tools apply the PRESENT-DAY offset to a past date. Taiwan observed DST 1945-1961 and 1974-1979, mainland China 1986-1991, Japan 1948-1951 — a birth inside those windows is an hour off in tools that ignore them, which moves the ascendant about 15 degrees. Use this to explain WHY two charts differ.

Input parameters:

- `date` (string, required): Local birth date at the birthplace, YYYY-MM-DD.
- `time` (string, required): Local clock time at the birthplace, HH:mm 24-hour, as written on the birth record.
- `timezone` (string, required): IANA timezone of the BIRTHPLACE, e.g. Asia/Taipei. Never the user's current zone — people are routinely asked about a birth in another country.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/breezefeng-deepnatal/deepnatal#diagnostics

## Score history

- 2026-09-21: 90
- 2026-09-20: 90
- 2026-09-19: 89
- 2026-09-18: 89
- 2026-09-17: 88
- 2026-09-16: 88
- 2026-09-15: 88
- 2026-09-14: 87
- 2026-09-13: 87
- 2026-09-12: 86
- 2026-09-11: 86
- 2026-09-10: 85
- 2026-09-09: 85
- 2026-09-08: 84
- 2026-09-07: 84
- 2026-09-06: 83
- 2026-09-05: 80
- 2026-09-04: 80
- 2026-09-03: 80
- 2026-09-02: 80
- 2026-09-01: 80
- 2026-08-31: 80
- 2026-08-30: 80
- 2026-08-29: 65

## Common questions

### What is the io.github.breezefeng/deepnatal MCP server?

io.github.breezefeng/deepnatal is an MCP server listed in the public MCP registry as io.github.breezefeng/deepnatal. Natal charts cross-verified three ways. Refuses to answer rather than guess. This page covers its npm package (deepnatal).

### Is the io.github.breezefeng/deepnatal MCP server safe to use?

io.github.breezefeng/deepnatal scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 io.github.breezefeng/deepnatal MCP server expose?

io.github.breezefeng/deepnatal exposes 4 tools: calculate_natal_chart, calculate_chart_without_birth_time, verify_ascendant, inspect_historical_timezone. Their descriptions and schemas cost roughly 913 tokens of context every time the server is loaded.

### Is the io.github.breezefeng/deepnatal MCP server still maintained?

io.github.breezefeng/deepnatal is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.breezefeng/deepnatal MCP server under?

io.github.breezefeng/deepnatal 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/deepnatal
- Socket report: https://socket.dev/npm/package/deepnatal
- Repository: https://github.com/breezefeng/deepnatal
- Website: https://deepnatal.com/
- Changelog RSS feed: https://verifymcp.io/servers/breezefeng-deepnatal/deepnatal.xml
- Changelog JSON feed: https://verifymcp.io/servers/breezefeng-deepnatal/deepnatal.json
- HTML version of this page: https://verifymcp.io/servers/breezefeng-deepnatal/deepnatal