com.natalcompass/connector
REMOTE · NATALCOMPASS.COM · SCANNED SEP 26
Birth charts, transits, moon phases and more from precise astronomical calculations. Natal Compass.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability62
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
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.
remote · natalcompass.com
claude mcp add --transport http com-natalcompass-connector 'https://natalcompass.com/mcp'
{
"mcpServers": {
"com-natalcompass-connector": {
"url": "https://natalcompass.com/mcp"
}
}
} {
"servers": {
"com-natalcompass-connector": {
"type": "http",
"url": "https://natalcompass.com/mcp"
}
}
} [mcp_servers.com-natalcompass-connector] url = "https://natalcompass.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-natalcompass-connector": {
"type": "remote",
"url": "https://natalcompass.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-natalcompass-connector --url 'https://natalcompass.com/mcp' --transport streamable-http
mcp_servers:
com-natalcompass-connector:
url: "https://natalcompass.com/mcp" {
"McpServers": {
"com-natalcompass-connector": {
"Transport": "http",
"Url": "https://natalcompass.com/mcp"
}
}
} assistant mcp add com-natalcompass-connector -t streamable-http -u 'https://natalcompass.com/mcp'
{
"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.
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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 19 Sept 26 71
First indexed and scored.
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 26 Sept 2026 · Probed https://natalcompass.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=natalcompass.com | CN=YE2,O=Let's Encrypt,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA384 | 5e6cc8359d64ce21b62b51a5de0eb435ad0 |
| SANs: natalcompass.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of natalcompass.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| natalcompass.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| content-security-policy | default-src 'self';base-uri 'self';object-src 'none';frame-ancestors 'self';form-action 'self';script-src 'self' https://plausible.io https://challenges.cloudflare.com https://accounts.google.com;script-src-attr 'none';style-src 'self' https: 'unsafe-inline';img-src 'self' data: blob: https:;font-src 'self' https: data:;frame-src 'self' https://challenges.cloudflare.com https://accounts.google.com;connect-src 'self' https://plausible.io https://*.ingest.de.sentry.io https://challenges.cloudflare.com https://accounts.google.com;upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | geolocation=(), camera=(), microphone=(), payment=(), usb=(), notifications=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://natalcompass.com/mcp | Verified | 200 | |
| http (plaintext) | http://natalcompass.com/mcp | HTTPS enforced | 301 | https://natalcompass.com/mcp |
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 →
get_moon_phase Moon phase ~259
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculation | object | yes | – |
| input | object | yes | – |
| moon | object | yes | – |
| notes | array | yes | – |
| phase | object | yes | – |
| source | object | yes | – |
| sun | object | yes | – |
| void_of_course | object | yes | – |
No examples provided.
get_natal_chart Birth chart ~512
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).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 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 | yes | Birth place latitude in decimal degrees, north positive. Required. When given a place name, look up its coordinates first. |
| longitude | number | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| angles | object | – | – |
| aspects | array | yes | – |
| calculation | object | yes | – |
| houses | array | – | – |
| input | object | yes | – |
| notes | array | yes | – |
| planets | object | yes | – |
| source | object | yes | – |
No examples provided.
get_retrogrades Retrograde periods of a year ~228
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).
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | – | The calendar year, from 1900 to 2100. Optional: the current year when omitted. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculation | object | yes | – |
| input | object | yes | – |
| notes | array | yes | – |
| retrogrades | object | yes | – |
| source | object | yes | – |
No examples provided.
get_solar_return Solar return chart ~574
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).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | 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 | yes | Birth place latitude in decimal degrees, north positive. Required. When given a place name, look up its coordinates first. |
| longitude | number | yes | 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 | yes | The year of the return, from 1900 to 2100. |
| Name | Type | Req | Description |
|---|---|---|---|
| angles | object | – | – |
| aspects | array | yes | – |
| calculation | object | yes | – |
| houses | array | – | – |
| input | object | yes | – |
| notes | array | yes | – |
| planets | object | yes | – |
| return | object | yes | – |
| source | object | yes | – |
No examples provided.
get_synastry Synastry between two charts ~324
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).
| Name | Type | Req | Description |
|---|---|---|---|
| include_minor_aspects | boolean | – | Also list the minor aspects (semisextile, semisquare, sesquiquadrate, quincunx). Off by default. |
| person_a | object | yes | 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 | yes | The second person's birth details, in the same shape. |
| Name | Type | Req | Description |
|---|---|---|---|
| aspects | array | yes | – |
| calculation | object | yes | – |
| input | object | yes | – |
| notes | array | yes | – |
| source | object | yes | – |
No examples provided.
get_transits Planets on a date ~263
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculation | object | yes | – |
| input | object | yes | – |
| notes | array | yes | – |
| positions | object | yes | – |
| source | object | yes | – |
No examples provided.
get_transits_to_chart Transits to a birth chart ~517
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).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Birth date as YYYY-MM-DD, from 1900 to 2100. |
| house_system | string | – | House system. Placidus unless the person asks for another. |
| latitude | number | yes | Birth place latitude in decimal degrees, north positive. Required. When given a place name, look up its coordinates first. |
| longitude | number | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| aspects | array | yes | – |
| calculation | object | yes | – |
| input | object | yes | – |
| notes | array | yes | – |
| source | object | yes | – |
| transits | object | yes | – |
No examples provided.
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.