CycleCalcs Astronomy
REMOTE · WWW.CYCLECALCS.COM
Read-only astronomy calculations: sun, moon, planets, eclipses, twilight and star positions.
Available components
Last scanned (9 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Maps and Location
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 Security83
- 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability55
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 8587 tokens (~715/item across 12 items; 12 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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.
- 5 Nov 26 +65
- Authorization: unverified → partial ▲ security
- HTTPS: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Stability: unverified → pass ▲ security
- HSTS header: fail → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: not serving MCP → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- “observing_windows” reworded the description of “cloudmax” cosmetic
- 4 Nov 26 −65
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- HTTPS: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- HSTS header: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 2 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “astro_dark_window” rewrote its description, which is the text the model reads security
- Tool “astro_sky_today” rewrote its description, which is the text the model reads security
- Server version: 1.1.0 → 1.2.0 functional
- New tool “observing_windows” functional
- 24 Oct 26 0
- “astro_dark_window” reworded the description of “date” cosmetic
- “astro_dark_window” reworded the description of “place” cosmetic
- “astro_eclipses” reworded the description of “date” cosmetic
- “astro_eclipses” reworded the description of “end” cosmetic
- “astro_eclipses” reworded the description of “place” cosmetic
- “astro_eclipses” reworded the description of “start” cosmetic
- “astro_find_place” reworded the description of “query” cosmetic
- “astro_moon” reworded the description of “date” cosmetic
- “astro_moon” reworded the description of “end” cosmetic
- “astro_moon” reworded the description of “place” cosmetic
- “astro_moon” reworded the description of “start” cosmetic
- “astro_moon_phases” reworded the description of “date” cosmetic
- “astro_moon_phases” reworded the description of “end” cosmetic
- “astro_moon_phases” reworded the description of “place” cosmetic
- “astro_moon_phases” reworded the description of “start” cosmetic
- “astro_planet_board” reworded the description of “date” cosmetic
- “astro_planet_board” reworded the description of “place” cosmetic
- “astro_planet_events” reworded the description of “date” cosmetic
- “astro_planet_events” reworded the description of “end” cosmetic
- “astro_planet_events” reworded the description of “place” cosmetic
- “astro_planet_events” reworded the description of “start” cosmetic
- “astro_positions” reworded the description of “date” cosmetic
- “astro_positions” reworded the description of “end” cosmetic
- “astro_positions” reworded the description of “place” cosmetic
- “astro_positions” reworded the description of “start” cosmetic
- “astro_rise_set” reworded the description of “date” cosmetic
- “astro_rise_set” reworded the description of “end” cosmetic
- “astro_rise_set” reworded the description of “place” cosmetic
- “astro_rise_set” reworded the description of “start” cosmetic
- “astro_sky_today” reworded the description of “date” cosmetic
- “astro_sky_today” reworded the description of “place” cosmetic
- “astro_sun” reworded the description of “date” cosmetic
- “astro_sun” reworded the description of “end” cosmetic
- “astro_sun” reworded the description of “place” cosmetic
- “astro_sun” reworded the description of “start” cosmetic
35 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.
- 9 Oct 26 0
- Server version: 1.0.0 → 1.1.0 functional
- 1 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- 28 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
- 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
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://www.cyclecalcs.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.cyclecalcs.com | CN=YE1,O=Let's Encrypt,C=US | 12 Oct 2026 | 10 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 679d7586efe0d391d8bbf49b3afda702012 |
| SANs: cyclecalcs.com, www.cyclecalcs.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 secure
Validation of www.cyclecalcs.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cyclecalcs.com. | present | 27182 | 8 | Verified |
| www.cyclecalcs.com. | Verified address RRset verified with the apex keys |
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=63072000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.cyclecalcs.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.cyclecalcs.com/mcp | HTTPS enforced | 301 | https://www.cyclecalcs.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 →
astro_dark_window Dark moonless observing window ~459
The genuinely dark, moonless observing window for a night: astronomical night intersected with the Moon being down, ranked across up to 62 nights with a trend. The right tool for "when should I stargaze / photograph the Milky Way / observe deep-sky objects". Location required. For plain twilight times use astro_sun; for whether tonight's clouds allow it, use observing_windows.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | Night to start from. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: followe… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| moon_illumination_max | number | – | Treat the Moon as tolerable below this illuminated fraction (0..1) even when up. |
| nights | integer | – | How many nights to evaluate and rank. Default 1. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | The best genuinely dark observing windows across a range of nights. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_eclipses Solar and lunar eclipses ~1,026
Solar and lunar eclipses: the next or previous from a date, or all in a range, with type, magnitude, obscuration, Saros series and global geometry. A solar eclipse also carries a computed hybrid flag and, when central, the duration, path width and Sun altitude at greatest eclipse. With a location it adds local circumstances, contact times, and an explicit visible-from-here answer; set visible_only to true to keep only eclipses visible there. include adds the precomputed central path or the circumstances at greatest local eclipse. NOTE: count applies per type, so count=3 with type "both" can return six events.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many eclipses PER TYPE to return. |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | Anchor date to search from. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd:… |
| direction | string | – | Search direction from the anchor date. Default "next". |
| end | string | – | Last day of an explicit window. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or… |
| include | array | – | Optional extras, added to the default blocks rather than replacing them. "path": the precomputed central path of a solar eclipse as inline GeoJSON (central line, northern and southern limits, and per… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| start | string | – | First day of an explicit window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening an… |
| type | string | – | Which kind of eclipse to report. Default "both". |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| visible_only | boolean | – | true keeps only eclipses visible from the supplied location (requires a location). |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Solar and lunar eclipses in a date range, optionally filtered to one location. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_find_place Place name to coordinates and timezone ~261
Resolve a place name to coordinates, region, country, IANA timezone and a stable place_id, or reverse-look-up the nearest places to a lat/lon. Results are GeoNames data (CC BY 4.0); the response carries the required credit in its attribution field, which must be preserved when results are shown. Note the other tools accept a place argument directly, so this is only needed to disambiguate a name, filter by country, or reverse-geocode.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | – | Two-letter ISO country code filter, e.g. "US". |
| id | string | – | A place_id from an earlier result, to fetch that exact place. |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| limit | integer | – | Maximum matches to return. Default 5. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| query | string | – | The place NAME to search for, one to three words, e.g. "Springfield" or "Springfield,US". Never a question or a sentence: send "Lisbon", not "moon phase tonight in Lisbon". |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Coordinates for a place name, or the nearest named places to coordinates. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_moon Moon state and appearance ~755
The Moon at an instant or as a daily series: phase name and angle, illuminated fraction, distance, apparent size, libration, bright limb, and the next quarter phases. A location adds rise/set and altitude. For a calendar of new and full moons use astro_moon_phases; for the Moon's exact coordinates use astro_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | Number of daily rows from start (alternative to end). |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: followed by a Julian Day on… |
| end | string | – | Last day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd:… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| start | string | – | First day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd:… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | The Moon's state and appearance, or a sampled series in range mode. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_moon_phases Lunar phase calendar ~807
Every new moon, quarter and full moon in a window (or the next few from a date): each with its exact instant, distance, apparent size, supermoon classification under both competing definitions, traditional full-moon name, and any eclipse falling on it. Use for "when is the next full moon" and phase calendars. For the Moon's state right now use astro_moon.
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | – | How many phase events to return from the anchor date. |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | Anchor date; the next phases follow it. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its ni… |
| end | string | – | Last day of a window. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: follow… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| phases | array | – | Optional filter of phase kinds. Omit for all four. Example: ["full_moon"] for full moons only. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| start | string | – | First day of a window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its nigh… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | New, first quarter, full and last quarter moons in a date range. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_planet_board All planets at a glance ~448
All eight planets in one call for a date and optional location: constellation, magnitude, apparent size, elongation from the Sun, morning or evening sky, retrograde state with the next station, rise/set, and a worth-looking-tonight assessment. The right tool for "which planets are visible tonight". For exact coordinates of specific bodies use astro_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array | – | Optional subset of planets: mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto. |
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: followed by a Julian Day on… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| sort | string | – | Optional result ordering. Default is by distance from the Sun. |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Which planets are worth looking at right now, and where. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_planet_events Planet events: apparitions, oppositions, constellation entries ~1,057
Dated planet events. For Mercury and Venus, the apparition cycle: inferior and superior conjunctions, greatest eastern and western elongations, peak brightness (a Venus-only event: Mercury's brightness peaks behind the Sun where it cannot be seen), and the rare transits across the Sun; with no dates it also reports where each is in its cycle right now: morning star or evening star, the conjunctions bounding the current apparition, and the live elongation, phase, magnitude and apparent size. For Mars, Jupiter, Saturn, Uranus and Neptune: conjunction with the Sun, western quadrature, opposition and eastern quadrature, the instants the planet's apparent geocentric ecliptic longitude minus the Sun's reaches 0, 270, 180 and 90 deg, each with the planet's constellation, distance, magnitude and elongation. For any of the seven, constellation_entry, returned only when listed in kinds: each crossing of an IAU constellation boundary, with the two constellations and the direction of motion. The right tool for "when does Venus become the morning star", "when is Mars at opposition", or "when does Uranus cross from Taurus into Gemini". For tonight's visibility of all eight planets use astro_planet_board. Mercury and Venus conjunction instants use the classical heliocentric convention, named on each event.
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array | – | Which planets to report. Default mercury and venus. |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | Anchor instant; with no start/end the response covers the next full synodic cycle from here. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date m… |
| end | string | – | Last day of an explicit window, exclusive. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its… |
| kinds | array | – | Optional filter of event kinds. Omit for each planet's own family: the seven apparition kinds for mercury and venus, the four Sun-relative kinds for mars to neptune. peak_magnitude only ever fires fo… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| start | string | – | First day of an explicit window (use with end). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening an… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Planet events in a date range: the Mercury and Venus apparition events (conjunctions, greatest elongations, Venus's peak brightness, transits across the Sun), the Sun-relative events of Mars to Neptu… |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_positions Precise positions of bodies ~911
Exact positions for up to 20 bodies at an instant or over a time grid: right ascension and declination in both J2000 and of-date frames, ecliptic longitude and latitude, distance, and, with a location, altitude and azimuth with refraction stated per field. With a location the position is topocentric, but tropical_sign and constellation stay geocentric, and meta.conventions.label_origin says so. Use for "where exactly is X". Do not pass earth. For rise and set TIMES use astro_rise_set; for a visibility overview of all planets use astro_planet_board.
| Name | Type | Req | Description |
|---|---|---|---|
| bodies | array | yes | Bodies to report. Each entry: One of sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, or a fixed J2000 target as "radec:RA,DEC" with RA in hours (0-24) and DEC in degrees (-9… |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: followed by a Julian Day on… |
| end | string | – | Grid end. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: followed by a Juli… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| start | string | – | Grid start (use with end and step). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night.… |
| step | string | – | Grid stride, e.g. "1h", "10min", "1d". |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Where each requested body is, at an instant or sampled across a range. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_rise_set Rise, transit and set times ~854
Rise, upper transit, set and lower transit for one body at one location, with an explicit status at extreme latitudes (circumpolar, never rises) instead of missing values. Accepts fixed radec targets. For the Sun specifically, astro_sun returns richer twilight structure; for positions between events use astro_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| body | string | yes | One of sun, moon, mercury, venus, mars, jupiter, saturn, uranus, neptune, pluto, or a fixed J2000 target as "radec:RA,DEC" with RA in hours (0-24) and DEC in degrees (-90..90), e.g. "radec:5.6,-5.4"… |
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: followed by a Julian Day on… |
| end | string | – | Last day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd:… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| search_horizon_days | integer | – | How many days ahead to search when an event does not occur on the requested day (high latitudes). |
| start | string | – | First day of a daily series. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd:… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Rise, transit and set for one body, for a day or across a range. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_sky_today Sky snapshot for a place and moment ~427
One-call snapshot of the whole sky for a place and moment: moon phase and illumination, which planets are up and worth looking at, the next eclipse, and (with a location) sun times. Reach for this first when the question is broad, like "what is in the sky tonight". For solar-day detail use astro_sun; for choosing an observing night use astro_dark_window, and for whether tonight's clouds allow it use observing_windows; for one planet's exact position use astro_positions.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: followed by a Julian Day on… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | A whole-sky snapshot for one place and moment. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
astro_sun Sunrise, sunset and twilight ~801
The complete solar day for one location: sunrise, sunset, solar noon, day length, civil, nautical and astronomical twilight boundaries, and explicit polar day/night status at high latitudes. Location required. For a series, send start and end (step is whole days, e.g. "1d" or "7d"). For "is it dark enough to observe" prefer astro_dark_window; for a broad snapshot prefer astro_sky_today.
| Name | Type | Req | Description |
|---|---|---|---|
| cursor | string | – | Opaque pagination cursor from a previous result's next_cursor. Send it with the same start/end arguments as the first page. |
| date | string | – | Single day to report, ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: follow… |
| end | string | – | Last day of a range. ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its evening and its night. Or jd: followe… |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| start | string | – | First day of a range (use with end instead of date). ISO 8601 UTC date or datetime, e.g. "2026-08-06" or "2026-08-06T21:00:00Z". With a location, a bare date means that date there: its day, its eveni… |
| step | string | – | Range stride in whole days, e.g. "1d", "7d", "30d". Default "1d". |
| tz | string | – | IANA timezone like "Europe/Lisbon" to render event times in local time. Optional; a resolved place supplies its own timezone. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | The complete solar day for one location, or one row per day in range mode. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | Either unrestricted, or attribution_required when third-party place data was used. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
observing_windows Clear, dark observing windows tonight ~509
Is tonight good for observing here, and when? The clear, dark windows of tonight, and of the next nights the hourly cloud forecast covers, for one place: astronomical night with the Moon down (or up, with moon "any"), under the MET Norway cloud forecast. The windows are the ones the CycleCalcs Observing Planner widget draws, and the rule below decides which count; the answer is the /api/observing-windows feed's. Returns summary (tonight in one sentence on the place's clock), go_tonight (true when tonight has a window that passes the rule), next (the first window ahead that passes, with start, end, minutes and starts_in_minutes), tonight and later. Give lat, lon and tz, or a place name; lat and lon are rounded to two decimals (about 1 km), the precision of the forecast. The right tool for "is it clear enough to stargaze tonight" or "when should I set up the telescope". For the moonless dark alone, without weather, or for nights past the forecast, use astro_dark_window.
| Name | Type | Req | Description |
|---|---|---|---|
| cloudmax | integer | – | The clear limit: an hour is clear when the forecast gives under this percent of total cloud (and under 25 percent fog, with no rain forecast). Default 30. |
| lat | number | – | Latitude in decimal degrees, north positive. Send lat and lon together. |
| lon | number | – | Longitude in decimal degrees, east positive (Lisbon is about -9.14). Send lat and lon together. |
| min_minutes | integer | – | The shortest window worth going out for, in minutes. Default 60. |
| moon | string | – | "down" (the default) counts only windows with the Moon below the horizon; "any" lets it be up. |
| place | string | – | The place NAME only, one to three words, instead of lat/lon: "City" or "City,CC" with an ISO country code, e.g. "Lisbon,PT". Never a question or a sentence. Resolved server-side; the response then ca… |
| tz | string | – | The place's IANA timezone, such as "America/Chicago". Required with lat and lon: tonight and every time in the answer are on the place's clock. A resolved place supplies its own. |
| Name | Type | Req | Description |
|---|---|---|---|
| attribution | string | – | The credit line to display verbatim when rights is attribution_required. |
| data | object | yes | Tonight's clear, dark windows at one place under the cloud forecast, and the first one ahead that passes the rule. The same plan /api/observing-windows serves. |
| next_cursor | string | – | Present only when more rows exist. Send it back with the SAME start/end arguments as the first call to get the next page. |
| not_computed | array | – | Data this API deliberately does not serve, and why. Present only when the question touched such a field. An absence named here is information: treat it as "withheld", never as "none exists". |
| rights | string | – | attribution_required when the cloud forecast or a resolved place name was used, else unrestricted. When attribution_required, the attribution line must be shown. |
| warnings | array | – | Machine-readable notices about this answer. Present only when non-empty. Never changes whether the call succeeded. |
No examples provided.
How do I install the CycleCalcs Astronomy MCP server?
CycleCalcs Astronomy is a hosted endpoint at https://www.cyclecalcs.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 · www.cyclecalcs.com
claude mcp add --transport http com-cyclecalcs-astronomy 'https://www.cyclecalcs.com/mcp'
What is the CycleCalcs Astronomy MCP server?
CycleCalcs Astronomy is an MCP server listed in the public MCP registry as com.cyclecalcs/astronomy. Read-only astronomy calculations: sun, moon, planets, eclipses, twilight and star positions. This page covers its hosted endpoint (https://www.cyclecalcs.com/mcp).
Is the CycleCalcs Astronomy MCP server safe to use?
CycleCalcs Astronomy scores 85 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 CycleCalcs Astronomy MCP server expose?
CycleCalcs Astronomy exposes 12 tools: astro_sky_today, astro_sun, astro_moon, astro_moon_phases, astro_positions, and 7 more. Their descriptions and schemas cost roughly 8,315 tokens of context every time the server is loaded.
Does the CycleCalcs Astronomy MCP server require authentication?
No. We connected to CycleCalcs Astronomy without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CycleCalcs Astronomy MCP server still maintained?
CycleCalcs Astronomy 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.