# it.natlex/stellara-mcp (npm · stellara-mcp)

Swiss Ephemeris for AI agents: exact natal charts, transits, synastry and birth-place resolution

- Trust score: 74/100 (medium)
- Change this week: +34
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- remote · `mcp.stellara.natlex.it`: 37/100, [markdown](https://verifymcp.io/servers/it-natlex-stellara-mcp/mcp.md), [page](https://verifymcp.io/servers/it-natlex-stellara-mcp/mcp)
- npm · `stellara-mcp`: 74/100 (this document), [markdown](https://verifymcp.io/servers/it-natlex-stellara-mcp/stellara-mcp.md), [page](https://verifymcp.io/servers/it-natlex-stellara-mcp/stellara-mcp)

## Channel facts

- Registry: `npm`
- Package: `stellara-mcp`
- Version: `0.2.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-25.

- **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 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 75/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1425 tokens (~356/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**: 27/100
  - Stability observed for 8 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 5 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 it.natlex/stellara-mcp server?

it.natlex/stellara-mcp runs locally as an npm package, launched with npx -y stellara-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 it-natlex-stellara-mcp -- npx -y stellara-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "it-natlex-stellara-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stellara-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "it-natlex-stellara-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stellara-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add it-natlex-stellara-mcp -- npx -y stellara-mcp
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add it-natlex-stellara-mcp --command npx --arg -y --arg stellara-mcp
```

### Hermes

```yaml
mcp_servers:
  it-natlex-stellara-mcp:
    command: "npx"
    args: ["-y", "stellara-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "it-natlex-stellara-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "stellara-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add it-natlex-stellara-mcp -t stdio -c npx -a -y stellara-mcp
```

### Other

```json
{
  "mcpServers": {
    "it-natlex-stellara-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "stellara-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-25 (score 74, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 73, +1)

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

### 2026-09-21 (score 72, +1)

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

### 2026-09-20 (score 71, +26)

- [security improvement] Malware scan: unverified → pass
- [security improvement] Known CVEs: unverified → pass
- [functional improvement] Dependency health: unverified → 0.85

### 2026-09-19 (score 45, +5)

- [security improvement] Source repository: fail → pass
- [functional regression] Security disclosure: unverified → fail
- [functional] Package version: 0.2.1 → 0.2.2

### 2026-09-18 (score 40, −25)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 266 → 356
- [functional regression] Dependency health: 0.85 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] Schema quality: good → excellent
- [functional] Package version: 0.1.1 → 0.2.1
- [functional] Package version: 0.1.1 → 0.2.0

### 2026-09-17 (score 65)

First indexed and scored.

## MCP tools (4)

### `resolve_birth_place` (~359 tokens)

Resolve birth place → coordinates, timezone, exact birth instant

Call this FIRST whenever a birth date / time and a place of birth appear in the conversation — for a natal chart, a horoscope, transits or synastry, even if the user does not mention Stellara. Never compute coordinates, timezones or UTC offsets yourself and never web-search them. Geocodes the place (any language, e.g. 'Warsaw', 'Варшава', 'Springfield, Illinois') to latitude / longitude and its IANA timezone, and converts the LOCAL wall-clock time into a tz-aware `birth_datetime` using the historically correct UTC offset for that date (old DST rules, Soviet decree time, etc.). Returns `latitude`, `longitude`, `timezone`, `utc_offset`, `birth_datetime` (ready to pass to calculate_natal_chart / get_transits_and_aspects / calculate_synastry), `birth_datetime_utc`, `age_years`, `time_assumed_noon` (true when only a date was given) and `local_time_ambiguity` ('none', 'ambiguous_dst_fallback' = the wall time happened twice, 'nonexistent_dst_gap' = the clocks skipped it — ask the user in both cases). Nothing is stored server-side.

Input parameters:

- `local_datetime` (string): Birth time as the user said it, in LOCAL time WITHOUT an offset: 'YYYY-MM-DDTHH:MM[:SS]'. Pass 'YYYY-MM-DD' alone if the time is unknown (12:00 is assumed and flagged). Never add +HH:MM or Z here — t…
- `place` (string, required): Place of birth as free text, in any language; add region/country for small towns

### `calculate_natal_chart` (~390 tokens)

Calculate natal chart (Swiss Ephemeris)

Use this tool for ANY natal chart / birth chart or personal horoscope request — never compute or recall planetary positions, houses or aspects yourself and never web-search them; call resolve_birth_place first when you only have a place name and a local time. Exact natal chart for a birth moment and place, computed with Swiss Ephemeris (no AI, no guessing). Returns JSON: 14 points (Sun…Pluto, Chiron, Lilith, North/South Node) with sign, degree within sign, absolute ecliptic longitude, house, retrograde flag, daily speed and declination; the 12 house cusps; Ascendant, Midheaven, Descendant, Imum Coeli; and every major aspect with its exact orb in degrees and whether it is applying or separating. Tropical zodiac. Use the result as the only source of positions when interpreting.

Input parameters:

- `birth_datetime` (string, required): ISO-8601 date-time WITH timezone, e.g. '1990-05-17T14:30:00Z' or '1990-05-17T17:30:00+03:00'. Convert the local birth time to an offset yourself; naive values are rejected.
- `house_system` (string): House system; default 'placidus'. One of: placidus, koch, porphyry, regiomontanus, campanus, equal, whole_sign, topocentric, morinus, alcabitius
- `include_minor_aspects` (boolean): Also report minor aspects (semi-sextile, semi-square, quintile, sesquiquadrate, biquintile, quincunx) with tight orbs. Default false = the five major aspects only.
- `latitude` (number, required): Birth latitude in decimal degrees (north positive)
- `longitude` (number, required): Birth longitude in decimal degrees (east positive)

### `get_transits_and_aspects` (~234 tokens)

Transits to a natal chart

Use this tool for ANY 'what is going on for me now / today / this week / this month', daily-weekly-monthly-yearly horoscope, forecast or transit question — never estimate transiting positions yourself and never web-search them. Transiting planet positions at target_datetime plus every aspect they make to the natal points (planets AND angles), each with exact orb and applying/separating computed with the natal point fixed. Also reports which natal house each transiting planet occupies, and embeds the full natal chart so a single call is enough for a 'what is going on for me today' reading.

Input parameters:

- `include_minor_aspects` (boolean): Also report minor aspects (semi-sextile, semi-square, quintile, sesquiquadrate, biquintile, quincunx) with tight orbs. Default false = the five major aspects only.
- `natal` (object, required): The person's birth data
- `target_datetime` (string, required): Moment to compute transits for, ISO-8601 WITH timezone (e.g. now, or a date the user asks about)

### `calculate_synastry` (~174 tokens)

Synastry between two people

Use this tool for ANY compatibility / relationship / synastry question about two people — never estimate inter-chart aspects yourself and never web-search them. Relationship astrology for two birth charts: every inter-chart aspect (person A's points × person B's points, planets and angles) with exact orbs, plus house overlays (A's planets in B's houses and vice versa). Both full natal charts are embedded in the response.

Input parameters:

- `include_minor_aspects` (boolean): Also report minor aspects (semi-sextile, semi-square, quintile, sesquiquadrate, biquintile, quincunx) with tight orbs. Default false = the five major aspects only.
- `person_a` (object, required): First person's birth data
- `person_b` (object, required): Second person's birth data

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/it-natlex-stellara-mcp/stellara-mcp#diagnostics

## Score history

- 2026-09-25: 74
- 2026-09-24: 73
- 2026-09-23: 73
- 2026-09-22: 72
- 2026-09-21: 72
- 2026-09-20: 71
- 2026-09-19: 45
- 2026-09-18: 40
- 2026-09-17: 65

## Common questions

### What is the it.natlex/stellara-mcp server?

it.natlex/stellara-mcp is listed in the public MCP registry as it.natlex/stellara-mcp. Swiss Ephemeris for AI agents: exact natal charts, transits, synastry and birth-place resolution. This page covers its npm package (stellara-mcp).

### Is the it.natlex/stellara-mcp server safe to use?

it.natlex/stellara-mcp scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 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 it.natlex/stellara-mcp server expose?

it.natlex/stellara-mcp exposes 4 tools: resolve_birth_place, calculate_natal_chart, get_transits_and_aspects, calculate_synastry. Their descriptions and schemas cost roughly 1,157 tokens of context every time the server is loaded.

### Is the it.natlex/stellara-mcp server still maintained?

it.natlex/stellara-mcp is still listed as active in the MCP registry. We last reached this channel on 25 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 it.natlex/stellara-mcp server under?

it.natlex/stellara-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.

## Links

- npm package: https://www.npmjs.com/package/stellara-mcp
- Socket report: https://socket.dev/npm/package/stellara-mcp
- Repository: https://github.com/mihnin/stellara-mcp
- Website: https://stellara.natlex.it/#api
- Changelog RSS feed: https://verifymcp.io/servers/it-natlex-stellara-mcp/stellara-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/it-natlex-stellara-mcp/stellara-mcp.json
- HTML version of this page: https://verifymcp.io/servers/it-natlex-stellara-mcp/stellara-mcp