Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.ganguoguo444004-coder/cosine-astro-mcp

NPM · COSINE-ASTRO-MCP

Astrology: natal charts, transits, synastry, retrogrades, profections. Computed offline.

Available components

0 this week 62 Trust /100

Last scanned (1 hour ago)

Scores higher than 31% of npm servers

Trust breakdown (7 categories)

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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 4.6.5, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability62
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1340 tokens (~223/item across 6 items; 6 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 Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

Changelog

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.

  • 24 Oct 26 −6
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 18 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 17 Oct 26 53

    First indexed and scored.

Diagnostics

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/cosine-astro-mcp@0.1.0

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 →

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 94 packages
Packages resolved 94
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 6 exposed · ~1,237 tokens

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 →

Tool Tokens
annual_profection ~371

Hellenistic annual profection for an age or a date: the profected house (whole-sign, counted from the Ascendant; from the Sun's sign if the birth time is unknown), its sign, the lord of the year (traditional ruler, with the modern co-ruler) and where that lord sits in the natal chart, plus the dates the profection year runs.

NameTypeReqDescription
ageinteger–Age in completed years. Takes precedence over `on_date`.
citystring–Optional shortcut: a city from the built-in offline table (about 110 large cities, English or Chinese name, e.g. "Beijing", "上海", "London", "New York"). Explicit latitude/longitude/timezone override…
datestringyesBirth date (local calendar date), YYYY-MM-DD
house_systemstring–House system. Placidus (default) falls back to whole-sign inside the polar circles, where it has no solution.
latitudenumber–Birthplace latitude in degrees, north positive
longitudenumber–Birthplace longitude in degrees, east positive (New York is about -74.0)
on_datestring–Date to find the profection year for, YYYY-MM-DD (default: today in the birth time zone)
timestring–Local clock time of birth, 24-hour HH:MM. Omit if unknown: planets are then cast for local noon and there are no Ascendant, Midheaven or houses.
timezonestring–IANA time zone of the birthplace, e.g. "Asia/Shanghai", "America/New_York". Historical daylight saving time is applied automatically. Required unless `city` is given.

No output schema declared.

No examples provided.

mercury_retrograde ~141

Mercury retrograde periods overlapping a date range (default: the next 12 months): pre-shadow start, station retrograde, station direct and post-shadow end (to about a minute, in UTC and a chosen time zone), with the degrees and signs of the two stations.

NameTypeReqDescription
end_datestring–End of the range, inclusive, YYYY-MM-DD (default: one year after the start). At most 30 years.
start_datestring–Start of the range, YYYY-MM-DD (default: today)
timezonestring–IANA time zone for the range and the local times in the output (default UTC)

No output schema declared.

No examples provided.

moon_phase ~115

The Moon's phase at a moment (default: now): phase name, illuminated fraction, Sun–Moon angle, days since new moon, the Moon's and Sun's signs, and the next new, first-quarter, full and last-quarter moons.

NameTypeReqDescription
datestring–Date, YYYY-MM-DD. Omit for the current moment.
timestring–Local time, HH:MM (default 12:00 when a date is given)
timezonestring–IANA time zone (default UTC)

No output schema declared.

No examples provided.

natal_chart ~317

Cast a tropical natal (birth) chart: the ten planets with sign, degree, house and retrograde flag; Ascendant and Midheaven; twelve house cusps (Placidus by default); major aspects with orbs and applying/separating; and the dominant element and modality. Works without a birth time (no angles or houses then).

NameTypeReqDescription
citystring–Optional shortcut: a city from the built-in offline table (about 110 large cities, English or Chinese name, e.g. "Beijing", "上海", "London", "New York"). Explicit latitude/longitude/timezone override…
datestringyesBirth date (local calendar date), YYYY-MM-DD
house_systemstring–House system. Placidus (default) falls back to whole-sign inside the polar circles, where it has no solution.
latitudenumber–Birthplace latitude in degrees, north positive
longitudenumber–Birthplace longitude in degrees, east positive (New York is about -74.0)
timestring–Local clock time of birth, 24-hour HH:MM. Omit if unknown: planets are then cast for local noon and there are no Ascendant, Midheaven or houses.
timezonestring–IANA time zone of the birthplace, e.g. "Asia/Shanghai", "America/New_York". Historical daylight saving time is applied automatically. Required unless `city` is given.

No output schema declared.

No examples provided.

synastry ~100

Compare two natal charts: the major aspects between person A's planets (and Ascendant) and person B's, with orbs (conjunction/opposition 6°, square/trine 5°, sextile 3°), where each person's planets fall in the other's houses, and a simple descriptive tally (not a compatibility score).

NameTypeReqDescription
person_aobjectyesFirst person's birth data
person_bobjectyesSecond person's birth data

No output schema declared.

No examples provided.

transits ~193

Planet positions for a date and time (default: now), and, given a natal chart, the major aspects the transiting planets make to the natal planets, Ascendant and Midheaven within an orb (default 2°), with the natal house each transiting planet is passing through.

NameTypeReqDescription
datestring–Date of the transits, YYYY-MM-DD. Omit for the current moment.
max_orbnumber–Largest orb in degrees for transit-to-natal aspects (default 2)
natalobject–The natal chart to compare against. Omit to get only the planets' positions.
timestring–Local time of the transits, HH:MM (default 12:00 when a date is given)
timezonestring–IANA time zone for the transit date and output times (default: the natal chart's zone, else UTC)

No output schema declared.

No examples provided.

Install

How do I install the io.github.ganguoguo444004-coder/cosine-astro-mcp server?

io.github.ganguoguo444004-coder/cosine-astro-mcp runs locally as an npm package, launched with npx -y cosine-astro-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 · cosine-astro-mcp

# add to Claude Code
claude mcp add ganguoguo444004-coder-cosine-astro-mcp -- npx -y cosine-astro-mcp
Common questions

What is the io.github.ganguoguo444004-coder/cosine-astro-mcp server?

io.github.ganguoguo444004-coder/cosine-astro-mcp is listed in the public MCP registry as io.github.ganguoguo444004-coder/cosine-astro-mcp. Astrology: natal charts, transits, synastry, retrogrades, profections. Computed offline. This page covers its npm package (cosine-astro-mcp).

Is the io.github.ganguoguo444004-coder/cosine-astro-mcp server safe to use?

io.github.ganguoguo444004-coder/cosine-astro-mcp scores 62 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. 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.ganguoguo444004-coder/cosine-astro-mcp server expose?

io.github.ganguoguo444004-coder/cosine-astro-mcp exposes 6 tools: natal_chart, transits, synastry, mercury_retrograde, annual_profection, moon_phase. Their descriptions and schemas cost roughly 1,237 tokens of context every time the server is loaded.

Is the io.github.ganguoguo444004-coder/cosine-astro-mcp server still maintained?

io.github.ganguoguo444004-coder/cosine-astro-mcp 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.ganguoguo444004-coder/cosine-astro-mcp server under?

io.github.ganguoguo444004-coder/cosine-astro-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.