Skip to main content
Glama
806,931 tools. Updated 2026-11-19 14:44

"Eclipse Mosquitto" matching MCP tools:

  • Returns every solar and lunar eclipse of a calendar year with local visibility for one city: eclipse type (total, partial, annular or penumbral), date, the sparsha (first contact), madhya (maximum) and moksha (release) times, the magnitude, and a locally_visible flag. That flag is the one that matters for practice -- sutak observance applies only where the eclipse is actually visible. Use this for 'which eclipses fall in this year' and 'is it visible here' questions, and for sutak timing. For festivals and vrat dates use get_year_events; for the rest of a day's almanac use get_panchang. Read-only deterministic computation (Swiss Ephemeris, Lahiri ayanamsa), served from a shared cache -- a cold or expired entry recomputes and can take ~30s; no writes, no auth, at least 30 requests/min/IP per server instance, plus a shared engine budget of at least 60/min/IP across all engine-backed tools. Constraints: the year must be within two years either side of the current year, and visibility is evaluated for the nearest of 50 supported cities.
    ConnectorNo auth
  • Solar and lunar eclipses in a date range, past or future, up to 10 years. Each gives the type, time of greatest eclipse, start and end (UTC) and the eclipse degree in the tropical zodiac. With birth data, each eclipse also lists the natal planets and angles within 3° of the eclipse degree by conjunction or opposition. WORKFLOW: BEFORE: None — standalone; add birth for personal contacts. AFTER: asterwise_get_western_transits_monthly — transits around an eclipse date. INPUT CONTRACT: from_date, to_date (string YYYY-MM-DD, UTC, inclusive) — at most 10 years apart. birth (optional WesternBirthData) — adds natal_contacts; house_system sets the Ascendant/MC computation. DO NOT CONFUSE WITH: asterwise_get_western_moon_phase — ordinary new and full moons, not eclipses. asterwise_get_western_moon_calendar — monthly phase table. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-western-eclipses/
    ConnectorOAuth
  • Solar and lunar eclipses in a date range, past or future, up to 10 years. Each gives the type, time of greatest eclipse, start and end (UTC) and the eclipse degree in the tropical zodiac. With birth data, each eclipse also lists the natal planets and angles within 3° of the eclipse degree by conjunction or opposition. WORKFLOW: BEFORE: None — standalone; add birth for personal contacts. AFTER: asterwise_get_western_transits_monthly — transits around an eclipse date. INPUT CONTRACT: from_date, to_date (string YYYY-MM-DD, UTC, inclusive) — at most 10 years apart. birth (optional WesternBirthData) — adds natal_contacts; house_system sets the Ascendant/MC computation. DO NOT CONFUSE WITH: asterwise_get_western_moon_phase — ordinary new and full moons, not eclipses. asterwise_get_western_moon_calendar — monthly phase table. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-western-eclipses/
    ConnectorOAuth
  • Return precomputed astronomical events between start_date and end_date — any range within years -5000..+5000 (eclipses -1999..3000), instant. Events are global (location-independent) and served from binary-searched lookup tables — no live ephemeris computation. Example questions: "planetary events this month", "solar eclipses in the 12th century", "when was Shani retrograde in 1500 BCE?", "adhik maas years this decade". Ritu/ayana changes are Sayan sankrantis: Surya entering Meena=Vasanta, Vrishabha=Grishma, Karka=Varsha (=Dakshinayan start, = solstice), Kanya=Sharada, Vrishchika=Hemanta, Makara=Shishira (=Uttarayan start, = solstice) — query event_types=["sankranti"] with ayanamsa="Sayan". Args: start_date: Start date inclusive, YYYY-MM-DD (e.g. "2026-01-01"); negative years allowed (e.g. "-3101-01-01") end_date: End date inclusive, YYYY-MM-DD (e.g. "2026-12-31") ayanamsa: "Lahiri" (Vedic sidereal, default) or "Sayan" (tropical/Western) grah: Optional planet filter. One of: Surya, Chandra, Mangala, Budha, Guru, Shukra, Shani, Rahu, Ketu event_types: Optional list of event type filters. Valid values: "transit" – Mangala..Ketu change rashi (NOT Surya/Chandra) "sankranti" – Surya changes rashi (~monthly) "moon_transit" – Chandra changes rashi (~monthly) "full_moon" – Purnima (Moon at 180° elongation) "new_moon" – Amavasya (Moon at 0° elongation) "retrograde_start" – planet turns retrograde "retrograde_end" – planet resumes direct motion "equinox" – Vernal or Autumnal equinox (Sayan Surya) "solstice" – Summer or Winter solstice (Sayan Surya) "asta_start" – planet enters combust zone (Grah Asta) "asta_end" – planet exits combust zone (Uday) "solar_eclipse" – solar eclipse (catalog, years -1999..3000) "lunar_eclipse" – lunar eclipse (catalog, years -1999..3000) "kaal_sarp" – Kaal Sarp window (interval) "adhik_maas" – intercalary Hindu month (interval) "kshay_maas" – lost Hindu month (interval) "kumbh_mela" – Kumbh Mela window (interval) The max range is set by the densest requested type: 3 years by default, up to 1000 years for sparse-only queries (kumbh, maas). Interval events also carry end_time, duration_days, and type-specific details. Returns: Dict with keys: start_date, end_date, ayanamsa, count, events (list). Each event has: time (UTC ISO), event_type, grah, from, to, and (for intervals) end_time, duration_days, plus a details dict.
    ConnectorNo auth
  • Return the nearest occurrence of one event type before or after a date — walks outward from any date in years -5000..+5000, instant. Ideal for questions like "when is the next Kumbh Mela?", "when does Guru go retrograde next?", "when is Makara Sankranti?" or "when was the last total solar eclipse before 1500 CE?" without scanning a whole range. Args: event_type: One of the values listed in get_astro_events (e.g. "kumbh_mela", "solar_eclipse", "adhik_maas", "sankranti"). from_date: Reference date, YYYY-MM-DD (BC years like "-0500-01-01" allowed). direction: "next" (first after from_date) or "prev" (last before). ayanamsa: "Lahiri" (default) or "Sayan". grah: Optional grah filter for grah-specific event types. location: Optional Kumbh Mela location (Haridwar/Prayagraj/Ujjain/Nashik). Returns: Dict with event_type, direction, from_date, ayanamsa, valid_range, and `event` (null if the reference date is outside the data range).
    ConnectorNo auth
  • Search forward from a start time for the next occurrences of one sky-event class, selected by the `event` enum: solar_eclipse, lunar_eclipse, equinox, solstice, moon_quarter, opposition, conjunction, max_elongation, perigee_apogee, or meteor_shower. Both eclipse classes and meteor_shower take an optional observer (latitude and longitude together). solar_eclipse without one returns global eclipses — kind, peak time, obscuration, and for a total or annular eclipse the latitude/longitude where it is greatest; with one it returns only eclipses visible from that point, with local contact times, `local_visible`, and the Sun's altitude at each contact. lunar_eclipse returns geocentric contact times, the same instants everywhere on Earth; an observer adds `local_visible` and the Moon's altitude at each contact. meteor_shower returns the maxima of nine major annual showers from a table bundled from the IMO Meteor Shower Calendar — ZHR, J2000 radiant, activity dates, and the Moon's geocentric illuminated fraction at each; an observer adds the radiant's and the Sun's altitude at the maximum, which can fall in daylight. The maxima are the calendar's nominal ones, with no outburst predictions. `shower` narrows the search to one shower by IMO code or name. A shower counts when its maximum is at or after start, so one past its maximum but still active needs an earlier start. Every other class is geocentric and ignores a location. The body-relative events (opposition, conjunction, max_elongation, perigee_apogee) require a `body`: opposition applies to the superior planets (mars through pluto), conjunction to any planet, max_elongation to mercury and venus, and perigee_apogee to the moon (perigee/apogee), earth, or a planet (perihelion/aphelion). conjunction with `body` alone is that planet's conjunction with the Sun. Add `body2` for a conjunction of two bodies — the Moon or a planet with another: the instant they share one ecliptic longitude seen from Earth's center, with their `separation_degrees` at that instant. That separation is not always their closest approach, since two planets can pass closer days or weeks away, and listings that time conjunctions by right ascension differ by hours, or by days for slow pairs. Returns the next `count` occurrences (default 1), up to 20 per call: a larger `count`, up to 200, returns the first 20 and a notice naming the exact `start` and `count` that continue the series. Searches stop at the end of 2100, the close of the supported span; when that leaves fewer than `count`, a notice says so. Start defaults to now; pass an IANA `timezone` for observer-local timestamps, eclipse contacts included.
    ConnectorNo auth

Matching MCP Servers

Matching MCP Connectors

  • 2027 eclipse costs: independent, not affiliated with IMXP (The Eclipse Missions, EclipseSeekers)

  • Next solar eclipse, eclipse times by place, Moon phases and seasons from the US Naval Observatory.

  • 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.
    ConnectorNo auth
  • Points along the path of the 2 August 2027 eclipse for which our oracle computed totality once — towns, capes, peaks, monuments — with the cloud range of two reanalyses at each. Points, not destinations: nothing was priced there and no entry or access was read. Points outside the path carry no totality. No coordinates are taken: the list is fixed, and a place absent from it has not been computed.
    ConnectorNo auth
  • 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.
    ConnectorNo auth
  • Local circumstances of a solar eclipse at a given latitude/longitude on a given date, whether the Sun is totally, annularly or partially eclipsed there, the magnitude and obscuration (percentage of the Sun covered), the duration, and the UT time, Sun altitude and azimuth of each contact (eclipse begins, totality begins/ends, maximum eclipse, eclipse ends, or sunrise/sunset if the eclipse is in progress then). Answers "what time does the August 12 2026 eclipse start in Madrid", "how much of the Sun will be covered in Denver", "will the eclipse be total where I am". Needs coordinates: resolve a place name to lat/lon first. Find the eclipse date with usno_solar_eclipses.
    ConnectorNo auth
  • Solar and lunar eclipses seen from a place: local type, contact times (C1-C4, P1-P4, U1-U4), magnitude, obscuration, duration of totality and the Sun's or Moon's altitude. E.g. {start: '2026-08-01', end: '2026-08-31', latitude: 39.47, longitude: -0.38}. For eclipse chasers, planetariums, schools and travel apps: solar eclipses from the place's own viewpoint (local type: total, annular, partial or none; contacts C1, C2, maximum, C3, C4 with the Sun's altitude and azimuth; magnitude, obscuration, duration, duration of totality or annularity) and lunar eclipses (penumbral and umbral contacts P1, U1, U2, maximum, U3, U4, P4 with the Moon's altitude, umbral and penumbral magnitude, durations), each marked visible when the body is above the horizon. Matches NASA's predictions to a few seconds (2024-04-08 at Dallas, 2025-03-14 lunar eclipse). Deterministic (JPL DE440, no LLM); every result carries meta.result_sha256. Price $0.10 per call via REST POST https://astro-agent.dev/v1/astronomy/eclipse-local (x402 or MPP); always paid, never a free call.
    ConnectorNo auth
  • Hindu festivals, vrats, sankrantis, eclipses and periods for a year at a location. Each lunar festival is fixed by its lunar month (amanta, with Adhik months found from new moons and sankrantis), its tithi, and the part of the day the tithi must hold (sunrise, forenoon, Madhyahna, Aparahna, Pradosh, Nishita, moonrise), with the classical tie-breaks when a tithi spans two days, Bhadra rules for Holika Dahan and Raksha Bandhan, and the Smarta Ekadashi rule. Checked against published panchang dates (New Delhi). WORKFLOW: BEFORE: asterwise_geocode — when you only have a place name. AFTER: asterwise_get_panchanga — the day's limbs and timings for a festival date. INPUT CONTRACT: year (1900-2100), lat, lon, timezone (IANA, default Asia/Kolkata). categories: optional list of festival, vrat, sankranti, eclipse, period; the default is ["festival"] (about 50 named festivals). Add "vrat" for every Ekadashi, Pradosh, Sankashti, Purnima and Amavasya, "period" for Adhik Maas, Pitru Paksha and Chaturmas, "eclipse" for eclipses. DO NOT CONFUSE WITH: asterwise_get_panchanga_calendar — daily limbs for a month, not festivals. asterwise_get_muhurta — auspicious windows for an activity, not festival dates. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-festival-calendar/
    ConnectorOAuth
  • Sky events in a UTC date range: rise/set/meridian transits (need lat+lon+body), lunar phases (new/quarters/full), solar and lunar eclipses, stations (body turns retrograde/direct; needs body), zodiac degree crossings (needs body + target_lon). Solar eclipses report global circumstances (type, magnitude, gamma) plus the greatest-eclipse location and path width; add lat+lon to also get local circumstances (type seen, magnitude, obscuration, contact times C1-C4). Lunar eclipses report type and magnitude; add lat+lon to learn whether the Moon is above the horizon there. Times to the second vs Swiss Ephemeris (stations to ~1 min: ill-conditioned by nature). Range <= 370 days.
    ConnectorNo auth
  • Hindu festivals, vrats, sankrantis, eclipses and periods for a year at a location. Each lunar festival is fixed by its lunar month (amanta, with Adhik months found from new moons and sankrantis), its tithi, and the part of the day the tithi must hold (sunrise, forenoon, Madhyahna, Aparahna, Pradosh, Nishita, moonrise), with the classical tie-breaks when a tithi spans two days, Bhadra rules for Holika Dahan and Raksha Bandhan, and the Smarta Ekadashi rule. Checked against published panchang dates (New Delhi). WORKFLOW: BEFORE: asterwise_geocode — when you only have a place name. AFTER: asterwise_get_panchanga — the day's limbs and timings for a festival date. INPUT CONTRACT: year (1900-2100), lat, lon, timezone (IANA, default Asia/Kolkata). categories: optional list of festival, vrat, sankranti, eclipse, period; the default is ["festival"] (about 50 named festivals). Add "vrat" for every Ekadashi, Pradosh, Sankashti, Purnima and Amavasya, "period" for Adhik Maas, Pitru Paksha and Chaturmas, "eclipse" for eclipses. DO NOT CONFUSE WITH: asterwise_get_panchanga_calendar — daily limbs for a month, not festivals. asterwise_get_muhurta — auspicious windows for an activity, not festival dates. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-festival-calendar/
    ConnectorOAuth
  • Finds the solar and lunar eclipses nearest a date: greatest eclipse to the second in UTC, type, obscuration, the eclipsed body's sign, days from the date, and for a solar eclipse where greatest eclipse meets the Earth. Given a place, each listing also carries what that observer gets: local kind, first contact, maximum, last contact and altitude at each. The 6,585.3-day saros groups eclipses into families whose members fall about a year or a continent apart, and a global eclipse is seen from only part of the Earth. Global and local circumstances are kept apart, including the Moon setting partway through or rising with the eclipse underway. Results include an attribution line and a permalink.
    ConnectorNo auth
  • When is the next solar eclipse, the list of solar eclipses in a year from the US Naval Observatory, each with its date and type (total, annular, partial, hybrid). With no arguments it returns the NEXT solar eclipse after today plus the rest of the current and following year, so "when is the next solar eclipse", "solar eclipses in 2027", "is there a total eclipse this year" are all one call. For where an eclipse is visible and what time it starts at a given place, follow with usno_eclipse_circumstances. Lunar eclipses are not published by this API.
    ConnectorNo auth
  • Combine .gitignore templates (based on github/gitignore) for languages, frameworks, tools, editors and operating systems into one deduplicated file, optionally test paths against it. Template ids: node, python, django, jupyter, java, maven, gradle, kotlin, android, go, rust, ruby, rails, php, laravel, dotnet, c, cpp, swift, flutter, elixir, scala, r, nextjs, terraform, unity, docker, secrets, vscode, jetbrains, visualstudio, eclipse, vim, emacs, sublime, macos, windows, linux. Returns: JSON { content (.gitignore text), unknownTemplates[], duplicatesRemoved, tests[{ path, ignored, rule{pattern,line,negate}, via }] }. Example input: {"templates":["node","macos","vscode"],"testPaths":[".env","node_modules/x.js",".vscode/settings.json"]}
    ConnectorNo auth
  • For a team of ONE: ask the house vetter to check your own proposed planet claim, so a solo agent can score. On a hidden star it folds the public light curve at your period and t0 and checks the dip's signal-to-noise, odd against even dips (eclipsing binary) and a dip halfway between (secondary eclipse). It never reads the answer key, so a rejection tells you nothing you could not compute yourself, and no attempt is used. Approved claims score as usual; the house vetter earns no vetter points and the leaderboard marks your team. Open-sky finds pass straight to NASA's known-signal check and human review.
    ConnectorNo auth
  • Calculates the solar and lunar eclipses of a year against a birth chart: each eclipse's date and type, the sidereal sign and nakshatra it falls in, the house it falls in counted from the rising sign and from the birth Moon, and the traditional reading of that count from the Moon sign. For a place it also says whether the eclipse is visible there, the local times of each contact and the Sutak window. Use it when someone asks about upcoming eclipses (grahan), whether one is visible where they live, its Sutak times, or where an eclipse falls in their chart.
    ConnectorNo auth
  • Calculates the solar and lunar eclipses of a year against a birth chart: each eclipse's date and type, the sidereal sign and nakshatra it falls in, the house it falls in counted from the rising sign and from the birth Moon, and the traditional reading of that count from the Moon sign. For a place it also says whether the eclipse is visible there, the local times of each contact and the Sutak window. Use it when someone asks about upcoming eclipses (grahan), whether one is visible where they live, its Sutak times, or where an eclipse falls in their chart.
    ConnectorNo auth
  • Forecast the western astrology events for a single birth chart over a window up to 90 days: every transit-to-natal major aspect refined to its exact instant, every transiting planet sign ingress, every retrograde or direct station, every solar and lunar eclipse, and every New and Full Moon. Returns a time-ordered, significance-scored timeline. Built for astrology forecast feeds, transit alerts, and timing tools.
    ConnectorNo auth