# com.natalcompass/connector (remote · natalcompass.com)

Birth charts, transits, moon phases and more from precise astronomical calculations. Natal Compass.

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

## Components

- remote · `natalcompass.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/com-natalcompass-connector/natalcompass.md), [page](https://verifymcp.io/servers/com-natalcompass-connector/natalcompass)

## Channel facts

- Endpoint: `https://natalcompass.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.3.6`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-26.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 2990 tokens (~427/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the com.natalcompass/connector MCP server?

com.natalcompass/connector is a hosted endpoint at https://natalcompass.com/mcp, so there is nothing to install locally. 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 --transport http com-natalcompass-connector 'https://natalcompass.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-natalcompass-connector": {
      "url": "https://natalcompass.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-natalcompass-connector": {
      "type": "http",
      "url": "https://natalcompass.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-natalcompass-connector]
url = "https://natalcompass.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-natalcompass-connector": {
      "type": "remote",
      "url": "https://natalcompass.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-natalcompass-connector --url 'https://natalcompass.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-natalcompass-connector:
    url: "https://natalcompass.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-natalcompass-connector": {
      "Transport": "http",
      "Url": "https://natalcompass.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-natalcompass-connector -t streamable-http -u 'https://natalcompass.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-natalcompass-connector": {
      "type": "http",
      "url": "https://natalcompass.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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, 0)

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

### 2026-09-24 (score 74, +1)

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

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

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

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

- [functional improvement] Stability: unverified → 0.03

### 2026-09-19 (score 71)

First indexed and scored.

## MCP tools (7)

### `get_natal_chart` (~512 tokens)

Birth chart

Computes a birth chart from a date, an optional time and a place: the sign and degree of the Sun, Moon, planets, lunar nodes, Lilith, Chiron and the Part of Fortune, the ascendant and midheaven, the twelve house cusps and the major aspects between planets. Use it when a person asks about their chart, their placements, their rising sign, their houses or their aspects. The birth place must be given as latitude and longitude in decimal degrees; when a person names a place, look up its coordinates first. Without a birth time the chart has no houses, ascendant or Part of Fortune, and the Moon sign may be uncertain. Do not use it for the sky on a date unrelated to a birth (use get_transits), for how a date relates to a birth chart (use get_transits_to_chart), for the Moon phase (use get_moon_phase), for two charts compared (use get_synastry), or for a solar return (use get_solar_return). Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).

Input parameters:

- `date` (string, required): Birth date as YYYY-MM-DD, from 1900 to 2100.
- `house_system` (string): House system. Placidus unless the person asks for another.
- `include_minor_aspects` (boolean): Also list the minor aspects (semisextile, semisquare, sesquiquadrate, quincunx). Off by default.
- `latitude` (number, required): Birth place latitude in decimal degrees, north positive. Required. When given a place name, look up its coordinates first.
- `longitude` (number, required): Birth place longitude in decimal degrees, east positive. Required. When given a place name, look up its coordinates first.
- `node_type` (string): Lunar node calculation: the mean node or the true node.
- `time` (string): Local birth time as HH:MM on a 24-hour clock. Omit it when the time is unknown; positions are then computed for noon local time, and the chart has no houses, ascendant or Part of Fortune.
- `timezone` (string): IANA time zone of the birth place, for example Europe/Belgrade. Optional: when omitted it is resolved from the coordinates.

Output parameters:

- `angles` (object)
- `aspects` (array)
- `calculation` (object)
- `houses` (array)
- `input` (object)
- `notes` (array)
- `planets` (object)
- `source` (object)

### `get_transits` (~263 tokens)

Planets on a date

Gives where the Sun, Moon and planets are on a date: the sign and degree of each, computed geocentrically for 00:00 UTC on that date, or for the current instant when no date is given. Use it, rather than web search, when a person asks where a planet is now, what the sky looks like on a date, or which sign the Moon is in today. Positions only: it does not say whether a planet is retrograde, and it is tied to no birth chart. For how a date relates to a birth chart, use get_transits_to_chart; for the Moon phase, use get_moon_phase; for a birth chart, use get_natal_chart; for when a planet is retrograde across a year, use get_retrogrades. Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).

Input parameters:

- `date` (string): The date, YYYY-MM-DD, from 1900 to 2100. Positions are computed for 00:00 UTC on that date. Omit it for the current instant.

Output parameters:

- `calculation` (object)
- `input` (object)
- `notes` (array)
- `positions` (object)
- `source` (object)

### `get_transits_to_chart` (~517 tokens)

Transits to a birth chart

Relates the sky on a date to a specific birth chart: which transiting planets form major aspects to which natal points, with orbs, plus the transiting positions themselves. Aspects are to the natal planets and points (the lunar nodes, Lilith, Chiron and the Part of Fortune); aspects to the ascendant and midheaven are not included. Use it when a person asks how the planets on a given day, or today, relate to their chart, what a transiting planet is doing to one of their natal placements, or which transits are close to exact for them. It needs the birth details that get_natal_chart takes, with the birth place as latitude and longitude in decimal degrees; when a person names a place, look up its coordinates first. The sky date is optional and defaults to the current instant. For the sky alone, tied to no chart, use get_transits; for the chart itself, use get_natal_chart; for the Moon phase, use get_moon_phase. Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).

Input parameters:

- `date` (string, required): Birth date as YYYY-MM-DD, from 1900 to 2100.
- `house_system` (string): House system. Placidus unless the person asks for another.
- `latitude` (number, required): Birth place latitude in decimal degrees, north positive. Required. When given a place name, look up its coordinates first.
- `longitude` (number, required): Birth place longitude in decimal degrees, east positive. Required. When given a place name, look up its coordinates first.
- `node_type` (string): Lunar node calculation: the mean node or the true node.
- `time` (string): Local birth time as HH:MM on a 24-hour clock. Omit it when the time is unknown; positions are then computed for noon local time, and the chart has no houses, ascendant or Part of Fortune.
- `timezone` (string): IANA time zone of the birth place, for example Europe/Belgrade. Optional: when omitted it is resolved from the coordinates.
- `transit_date` (string): The date to compute the sky for, YYYY-MM-DD, from 1900 to 2100, at 00:00 UTC. Omit it for the current instant.

Output parameters:

- `aspects` (array)
- `calculation` (object)
- `input` (object)
- `notes` (array)
- `source` (object)
- `transits` (object)

### `get_moon_phase` (~259 tokens)

Moon phase

Gives the Moon on a date: the phase name, how much of the Moon is lit, its elongation from the Sun, the sign and degree of the Moon and of the Sun, and whether the Moon is void of course, with the time of its next major aspect and of its next sign change. Values are for 00:00 UTC on the date, or for the current instant when no date is given. Use it, rather than web search, when a person asks whether the Moon is void of course right now, about the Moon phase, a full or new Moon, the sign the Moon is in, or a void-of-course Moon. For the other planets on a date, use get_transits; for a birth chart, use get_natal_chart. Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).

Input parameters:

- `date` (string): The date, YYYY-MM-DD, from 1900 to 2100. Values are computed for 00:00 UTC on that date. Omit it for the current instant.

Output parameters:

- `calculation` (object)
- `input` (object)
- `moon` (object)
- `notes` (array)
- `phase` (object)
- `source` (object)
- `sun` (object)
- `void_of_course` (object)

### `get_retrogrades` (~228 tokens)

Retrograde periods of a year

Lists the retrograde periods of Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune and Pluto in a calendar year: the day each planet stations retrograde and the day it stations direct, to the day, in UTC. Use it when a person asks whether a planet is retrograde on a date, when a Mercury retrograde starts or ends, or which planets are retrograde in a year. The year is optional and defaults to the current year. A period that crosses the year boundary is shown in full. For where the planets are on a single date, use get_transits; for what a transiting planet is doing to a birth chart, use get_transits_to_chart. Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).

Input parameters:

- `year` (integer): The calendar year, from 1900 to 2100. Optional: the current year when omitted.

Output parameters:

- `calculation` (object)
- `input` (object)
- `notes` (array)
- `retrogrades` (object)
- `source` (object)

### `get_synastry` (~324 tokens)

Synastry between two charts

Compares two birth charts: the major aspects between one person's Sun, Moon, planets and North Node and the other's, each with its orb. Use it when a person asks how two charts relate, which aspects run between two people's charts, or what one person's planet does to another's. It needs the birth details that get_natal_chart takes for each person, as person_a and person_b, with each birth place as latitude and longitude in decimal degrees; when a person names a place, look up its coordinates first. There is no score: the result is the aspects themselves. Houses and angles are not compared. Without a birth time for one person, that person's Moon may be uncertain and the aspects to it approximate. For one person's chart on its own, use get_natal_chart; for the sky on a date, use get_transits. Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).

Input parameters:

- `include_minor_aspects` (boolean): Also list the minor aspects (semisextile, semisquare, sesquiquadrate, quincunx). Off by default.
- `person_a` (object, required): The first person's birth details, as get_natal_chart takes them: date, optional time, latitude and longitude in decimal degrees, optional timezone.
- `person_b` (object, required): The second person's birth details, in the same shape.

Output parameters:

- `aspects` (array)
- `calculation` (object)
- `input` (object)
- `notes` (array)
- `source` (object)

### `get_solar_return` (~574 tokens)

Solar return chart

Computes a solar return chart: the moment in a given year when the Sun returns to its natal position, and the chart cast for that moment at a place, with the planets, the ascendant and midheaven, the twelve house cusps and the major aspects. Use it when a person asks about their solar return or their birthday chart for a year. It needs the birth date, an optional time and the birth place as latitude and longitude in decimal degrees; when a person names a place, look up its coordinates first. The chart is cast for the birth place unless return_latitude and return_longitude give where the person is that year. Houses use the Placidus system and the lunar nodes are the mean nodes. Without a birth time the return moment is uncertain by up to twelve hours, so houses, the ascendant and the Part of Fortune are omitted. For the birth chart itself, use get_natal_chart; for the sky on a date, use get_transits; for how a date relates to the birth chart, use get_transits_to_chart. Positions come from precise astronomical calculations. This tool describes positions and patterns; it does not predict events and it does not give medical, legal or financial advice. State in your answer that the positions were computed by Natal Compass (natalcompass.com).

Input parameters:

- `date` (string, required): Birth date as YYYY-MM-DD, from 1900 to 2100.
- `include_minor_aspects` (boolean): Also list the minor aspects (semisextile, semisquare, sesquiquadrate, quincunx). Off by default.
- `latitude` (number, required): Birth place latitude in decimal degrees, north positive. Required. When given a place name, look up its coordinates first.
- `longitude` (number, required): Birth place longitude in decimal degrees, east positive. Required. When given a place name, look up its coordinates first.
- `return_latitude` (number): Latitude in decimal degrees of where the person is for the return, north positive. Optional: the birth place when omitted. Give both return coordinates or neither.
- `return_longitude` (number): Longitude in decimal degrees of where the person is for the return, east positive. Optional: the birth place when omitted.
- `time` (string): Local birth time as HH:MM on a 24-hour clock. Omit it when the time is unknown; positions are then computed for noon local time, and the chart has no houses, ascendant or Part of Fortune.
- `timezone` (string): IANA time zone of the birth place, for example Europe/Belgrade. Optional: when omitted it is resolved from the coordinates.
- `year` (integer, required): The year of the return, from 1900 to 2100.

Output parameters:

- `angles` (object)
- `aspects` (array)
- `calculation` (object)
- `houses` (array)
- `input` (object)
- `notes` (array)
- `planets` (object)
- `return` (object)
- `source` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-natalcompass-connector/natalcompass#diagnostics

## Score history

- 2026-09-26: 74
- 2026-09-25: 74
- 2026-09-24: 74
- 2026-09-23: 73
- 2026-09-22: 73
- 2026-09-21: 72
- 2026-09-20: 72
- 2026-09-19: 71

## Common questions

### What is the com.natalcompass/connector MCP server?

com.natalcompass/connector is an MCP server listed in the public MCP registry as com.natalcompass/connector. Birth charts, transits, moon phases and more from precise astronomical calculations. Natal Compass. This page covers its hosted endpoint (https://natalcompass.com/mcp).

### Is the com.natalcompass/connector MCP server safe to use?

com.natalcompass/connector scores 74 out of 100 on VerifyMCP. 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 com.natalcompass/connector MCP server expose?

com.natalcompass/connector exposes 7 tools: get_natal_chart, get_transits, get_transits_to_chart, get_moon_phase, get_retrogrades, and 2 more. Their descriptions and schemas cost roughly 2,677 tokens of context every time the server is loaded.

### Does the com.natalcompass/connector MCP server require authentication?

No. We connected to com.natalcompass/connector without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.natalcompass/connector MCP server still maintained?

com.natalcompass/connector is still listed as active in the MCP registry. We last reached this channel on 26 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://natalcompass.com/mcp
- Website: https://natalcompass.com/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-natalcompass-connector/natalcompass.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-natalcompass-connector/natalcompass.json
- HTML version of this page: https://verifymcp.io/servers/com-natalcompass-connector/natalcompass