Naelos.ai
REMOTE · MCP.NAELOS.AI
Astrology charts, transits and eclipses from NASA JPL data, 13,200 BC to AD 17,191. Free, no key.
Available components
Last scanned (1 hour ago)
Scores higher than 58% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Health and Science
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1419 tokens (~141/item across 10 items; 10 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 78% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “returns” rewrote its description, which is the text the model reads security
- 2 Nov 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.
- 31 Oct 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.
- 29 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 68
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 5 Nov 2026 · Probed https://mcp.naelos.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.naelos.ai | CN=YE2,O=Let's Encrypt,C=US | 28 Oct 2026 | 26 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5abd92539229746e2e9b48ff76a901180c1 |
| SANs: mcp.naelos.ai | ||||||
| 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 mcp.naelos.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 1814, 3799 | 8, 8 | Verified |
| naelos.ai. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.naelos.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.naelos.ai/mcp | HTTPS enforced | 301 | https://mcp.naelos.ai/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 →
eclipses Eclipses ~64
Solar and lunar eclipses between two dates (up to 20 years per call), with type, the exact moment of greatest eclipse and the eclipse degree. Works across the full 15,000-year span.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| to | string | yes | – |
No output schema declared.
No examples provided.
naelos_library Naelos's national and empire charts ~75
Which national charts (198) and empire charts (19) Naelos holds, each researched and sourced, with the founding event it is cast for. The charts themselves, with their times, places and readings, are in Naelos's Mundane suite.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Filter by name, e.g. France |
No output schema declared.
No examples provided.
natal_chart Birth chart ~203
A complete natal (birth) chart: every planet's sign, degree and house, the Ascendant and Midheaven, retrogrades, and the aspects between planets with exact orbs. Calculated from NASA JPL data by Naelos Ephemeris.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Birth date, YYYY-MM-DD |
| house_system | string | – | House system (default placidus) |
| latitude | number | yes | Birthplace latitude in decimal degrees (north positive) |
| longitude | number | yes | Birthplace longitude in decimal degrees (east positive) |
| place | string | – | Birthplace name, echoed back so the user can check the coordinates |
| time | string | – | Local clock time, HH:MM (24-hour). If unknown, omit: noon is used, and houses and angles are then unreliable. |
| timezone | string | yes | IANA time zone of the birthplace, e.g. America/New_York. Historical daylight saving is applied from it. |
No output schema declared.
No examples provided.
planet_position One planet at any date ~90
One body's tropical position on a date, anywhere from 13,200 BC to AD 17,191, with its speed and whether it is retrograde. For historical and ancient dates; dates before 1582 are proleptic Gregorian.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | – |
| date | string | yes | – |
| time_utc | string | – | HH:MM UTC (default 12:00) |
No output schema declared.
No examples provided.
progressions Progressions and solar arc, now ~182
The progressed chart as of today: secondary progressions (a day after birth for each year of life) or solar arc directions (every point moved by the Sun's progressed arc).
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Birth date, YYYY-MM-DD |
| latitude | number | yes | Birthplace latitude in decimal degrees (north positive) |
| longitude | number | yes | Birthplace longitude in decimal degrees (east positive) |
| method | string | – | Default secondary |
| place | string | – | Birthplace name, echoed back so the user can check the coordinates |
| time | string | – | Local clock time, HH:MM (24-hour). If unknown, omit: noon is used, and houses and angles are then unreliable. |
| timezone | string | yes | IANA time zone of the birthplace, e.g. America/New_York. Historical daylight saving is applied from it. |
No output schema declared.
No examples provided.
returns Solar or lunar return ~235
The solar return for a year (the moment the Sun returns to its birth position, the chart for that year) or the most recent lunar return (the last time the Moon reached its birth position), cast for the birthplace or another location.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Birth date, YYYY-MM-DD |
| kind | string | yes | – |
| latitude | number | yes | Birthplace latitude in decimal degrees (north positive) |
| longitude | number | yes | Birthplace longitude in decimal degrees (east positive) |
| place | string | – | Birthplace name, echoed back so the user can check the coordinates |
| return_latitude | number | – | Where the person is for the return, if not the birthplace |
| return_longitude | number | – | – |
| time | string | – | Local clock time, HH:MM (24-hour). If unknown, omit: noon is used, and houses and angles are then unreliable. |
| timezone | string | yes | IANA time zone of the birthplace, e.g. America/New_York. Historical daylight saving is applied from it. |
| year | integer | – | Solar return year (default this year) |
No output schema declared.
No examples provided.
sky_now The sky at a moment ~97
Where every planet is at a moment (now by default): sign, degree, retrograde, and the aspects between them. Give a place to add houses and angles. Works for any date from 13,200 BC to AD 17,191.
| Name | Type | Req | Description |
|---|---|---|---|
| datetime_utc | string | – | The moment in UTC, YYYY-MM-DDTHH:MM (default now) |
| latitude | number | – | – |
| longitude | number | – | – |
No output schema declared.
No examples provided.
synastry Synastry between two people ~55
The aspects between two people's birth charts (each one's planets to the other's), with exact orbs and strength.
| Name | Type | Req | Description |
|---|---|---|---|
| person_a | object | yes | First person's birth data |
| person_b | object | yes | Second person's birth data |
No output schema declared.
No examples provided.
timing_events Ingresses, lunations and stations ~71
Between two dates: planets changing sign, new and full Moons (and quarters), and retrograde and direct stations, each with its exact moment in UTC. At most two years per call.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | – |
| kinds | array | – | Default all three |
| to | string | yes | – |
No output schema declared.
No examples provided.
transits Transits to a birth chart ~239
Every exact transit of the planets (Sun to Pluto; the Moon is left out as it aspects everything monthly) to a birth chart's planets, Ascendant and Midheaven over a span, with the exact date of each and whether the planet is retrograde. Major aspects: conjunction, sextile, square, trine, opposition.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Birth date, YYYY-MM-DD |
| days | integer | – | Length of the span in days (default 30, at most 366) |
| from | string | – | Start date (default today) |
| latitude | number | yes | Birthplace latitude in decimal degrees (north positive) |
| longitude | number | yes | Birthplace longitude in decimal degrees (east positive) |
| place | string | – | Birthplace name, echoed back so the user can check the coordinates |
| time | string | – | Local clock time, HH:MM (24-hour). If unknown, omit: noon is used, and houses and angles are then unreliable. |
| timezone | string | yes | IANA time zone of the birthplace, e.g. America/New_York. Historical daylight saving is applied from it. |
No output schema declared.
No examples provided.
How do I install the Naelos.ai MCP server?
Naelos.ai is a hosted endpoint at https://mcp.naelos.ai/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 · mcp.naelos.ai
claude mcp add --transport http ai-naelos-naelos 'https://mcp.naelos.ai/mcp'
What is the Naelos.ai MCP server?
Naelos.ai is an MCP server listed in the public MCP registry as ai.naelos/naelos. Astrology charts, transits and eclipses from NASA JPL data, 13,200 BC to AD 17,191. Free, no key. This page covers its hosted endpoint (https://mcp.naelos.ai/mcp).
Is the Naelos.ai MCP server safe to use?
Naelos.ai scores 72 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 Naelos.ai MCP server expose?
Naelos.ai exposes 10 tools: natal_chart, sky_now, planet_position, transits, synastry, and 5 more. Their descriptions and schemas cost roughly 1,311 tokens of context every time the server is loaded.
Does the Naelos.ai MCP server require authentication?
No. We connected to Naelos.ai without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Naelos.ai MCP server still maintained?
Naelos.ai 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.