CycleCalcs Astronomy MCP server
com.cyclecalcs/astronomycyclecalcs.comstreamable-httpv1.1.0Scanned
Read-only astronomy calculations: sun, moon, planets, eclipses, twilight and star positions.
12 tools: 11 change things and 1 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
11 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the CycleCalcs Astronomy MCP server can do
The CycleCalcs Astronomy MCP server is published by cyclecalcs.com, a domain the MCP Registry verified. It has 12 tools. It can create or change data (11 tools: astro_sky_today, astro_sun, astro_moon, astro_moon_phases and 7 more), but cannot delete data. 1 tool only reads.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.1.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
12 tools
Changes things 11Claude Code: ask
astro_dark_windowThe 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Dark moonless observing window
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_eclipsesSolar and lunar eclipses: the next or previous from a date, or all in a range, with type, magnitude, obscuration, Saros series and global geometry.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Solar and lunar eclipses
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_moonThe 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Moon state and appearance
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_moon_phasesEvery 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Lunar phase calendar
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_planet_boardAll 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 …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: All planets at a glance
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_planet_eventsDated planet events.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Planet events: apparitions, oppositions, constellation entries
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_positionsExact 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, …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Precise positions of bodies
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_rise_setRise, 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.1 finding
Why it is in this group
- The name "astro_rise_set" says "set": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "astro_rise_set" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "astro_rise_set" says "set": a word for a change.
Description, as the server wrote it 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.
Annotations the server declares
- title: Rise, transit and set times
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_sky_todayOne-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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Sky snapshot for a place and moment
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
astro_sunThe 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 …No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Sunrise, sunset and twilight
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
observing_windowsIs tonight good for observing here, and when?No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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.
Annotations the server declares
- title: Clear, dark observing windows tonight
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 1Show 1 read-only tool
astro_find_placeResolve 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.No findings
Why it is in this group
- The name "astro_find_place" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Place name to coordinates and timezone
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:36 UTC, unchanged since Nov 6, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 11
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://www.cyclecalcs.com/.well-known/oauth-protected-resource/mcp
- Authorization servers
- https://www.cyclecalcs.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- yes
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 11 tools that change things (11 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://www.cyclecalcs.com/mcp: tools/list returned 12 tools to an anonymous client, including astro_sky_today (write), astro_sun (write), astro_moon (write), astro_moon_phases (write), astro_positions (write) and 6 more
Posture changes
- Nov 6, 2026
- Tools that change things, listed without credentials: 10 to 11
Findings
Matches of fixed checks, with the text they matched.
- Warnastro_rise_set
The server marks "astro_rise_set" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "astro_rise_set" says "set": a word for a change.
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 added, 2 changed.+1 added~2 changedView diff
- Added:observing_windowsChanges things
- Changed:astro_dark_windowChanges thingsdescription
- Changed:astro_sky_todayChanges thingsdescription
PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 11.View diff
- Tools that change things, listed without credentials: 10 to 11
Tools11 changed.~11 changedView diff
- Changed:astro_dark_windowChanges thingsinputSchema
- Changed:astro_eclipsesChanges thingsinputSchema
- Changed:astro_find_placeOnly readsinputSchema
- Changed:astro_moonChanges thingsinputSchema
- Changed:astro_moon_phasesChanges thingsinputSchema
- Changed:astro_planet_boardChanges thingsinputSchema
- Changed:astro_planet_eventsChanges thingsinputSchema
- Changed:astro_positionsChanges thingsinputSchema
- Changed:astro_rise_setChanges thingsinputSchema
- Changed:astro_sky_todayChanges thingsinputSchema
- Changed:astro_sunChanges thingsinputSchema
Install
Pinned to version 1.1.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http astronomy https://www.cyclecalcs.com/mcpclaude mcp add --transport http astronomy https://www.cyclecalcs.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__astronomy__astro_find_place"
],
"ask": [
"mcp__astronomy__astro_sky_today",
"mcp__astronomy__astro_sun",
"mcp__astronomy__astro_moon",
"mcp__astronomy__astro_moon_phases",
"mcp__astronomy__astro_positions",
"mcp__astronomy__astro_rise_set",
"mcp__astronomy__astro_eclipses",
"mcp__astronomy__astro_dark_window",
"mcp__astronomy__observing_windows",
"mcp__astronomy__astro_planet_board",
"mcp__astronomy__astro_planet_events"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as astronomy. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.cyclecalcs/astronomy/verify?hash=212dd678557ab7c9d31ae6587031d5384d99867b353349a78e4e98892df7a6d4" | jq -e '.changed == false'Pinned hash 212dd678557a, from Nov 13, 2026, 00:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.cyclecalcs/astronomy/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.cyclecalcs/astronomy)Source: MCP Registry. Synced Oct 21, 2026, 17:53 UTC.
CycleCalcs Astronomy MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the CycleCalcs Astronomy MCP server safe?
- No scan can promise that. What its definitions show: 12 tools, 11 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the CycleCalcs Astronomy MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the CycleCalcs Astronomy MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the CycleCalcs Astronomy MCP server have?
- 12 tools: 11 write, 1 read. astro_sky_today, astro_sun, astro_moon, astro_moon_phases, astro_positions, astro_rise_set, astro_eclipses, astro_dark_window and 4 more.
Does the CycleCalcs Astronomy MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the CycleCalcs Astronomy MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the CycleCalcs Astronomy MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.