io.github.breezefeng/deepnatal
NPM · DEEPNATAL
Natal charts cross-verified three ways. Refuses to answer rather than guess.
Available components
Last scanned (15 hours ago)
Scores higher than 92% of npm servers
Category Health and Science
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 Security80
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 33 of 98 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to breezefeng/deepnatal). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 67 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 (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 2 Nov 26 0
- Stability: 0.97 → pass security
- 1 Nov 26 0
- Stability: pass → 0.97 functional
- 29 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 27 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- 26 Oct 26 0
- Stability: 0.97 → pass security
- 25 Oct 26 0
- Stability: pass → 0.97 functional
- 24 Oct 26 −6
- CVE-2023-54404 affects this package: high ▼ security
- Known CVEs: pass → fail ▼ security
- 19 Oct 26 +1
- Stability: 0.97 → pass security
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 5 Nov 2026 · Analysed npm/deepnatal@0.1.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | breezefeng/deepnatal |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/breezefeng/deepnatal/.github/workflows/publish.yml@refs/tags/v0.1.2 |
| Rekor log index | 2637970085 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:25fce1908d1d8f472ba03916885749e064d83a0693307e3e110967b8893d829036e4f2b87e80c101041cc8cd3f42f8cb2c5c6b84ba5ac3bae621c7f55 |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 1 finding
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 98 packages
| Packages resolved | 98 |
|---|---|
| Stale | 33 |
| 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 →
calculate_chart_without_birth_time Calculate a chart without a birth time ~192
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Local birth date at the birthplace, YYYY-MM-DD. |
| latitude | number | yes | Birthplace latitude, decimal degrees. |
| longitude | number | yes | Birthplace longitude, decimal degrees. |
| timezone | string | yes | 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. |
No output schema declared.
No examples provided.
calculate_natal_chart Calculate a natal chart ~222
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Local birth date at the birthplace, YYYY-MM-DD. |
| latitude | number | yes | Birthplace latitude, decimal degrees. |
| longitude | number | yes | Birthplace longitude, decimal degrees. |
| time | string | yes | Local clock time at the birthplace, HH:mm 24-hour, as written on the birth record. |
| timezone | string | yes | 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. |
No output schema declared.
No examples provided.
inspect_historical_timezone Inspect historical timezone and DST ~213
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.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Local birth date at the birthplace, YYYY-MM-DD. |
| time | string | yes | Local clock time at the birthplace, HH:mm 24-hour, as written on the birth record. |
| timezone | string | yes | 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. |
No output schema declared.
No examples provided.
verify_ascendant Independently verify an ascendant ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| claim | string | – | Optional ascendant produced by some other tool, to be checked against this engine. |
| date | string | yes | Local birth date at the birthplace, YYYY-MM-DD. |
| latitude | number | yes | Birthplace latitude, decimal degrees. |
| longitude | number | yes | Birthplace longitude, decimal degrees. |
| time | string | yes | Local clock time at the birthplace, HH:mm 24-hour, as written on the birth record. |
| timezone | string | yes | 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. |
No output schema declared.
No examples provided.
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.
npm · deepnatal
claude mcp add breezefeng-deepnatal -- npx -y deepnatal
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 88 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 5 November 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 5 November 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.
What did VerifyMCP test on the io.github.breezefeng/deepnatal MCP server?
VerifyMCP ran 16 checks on io.github.breezefeng/deepnatal, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.