Check the operational status of your Amazon Neptune graph to verify connectivity and health for graph database queries.
Apache 2.0
167,546 tools. Last updated 2026-06-02 23:19
"Neptune" matching MCP tools:
- Find exact moments when transiting planets form specified aspects to your natal chart positions over a date range. Ideal for horoscope timelines, event forecasting, and optimal timing windows.MIT
- Calculate rise, set, and transit times for planets at your location to plan optimal observation sessions.Apache 2.0
- Get precise ecliptic longitude, latitude, distance, speed, and retrograde status for any planet or celestial body at a given date and time. Supports Sun, Moon, planets, asteroids, and lunar nodes. Optional topocentric calculations with observer coordinates.MIT
- Calculate a planet's position in the sky for any date, time, and location to plan observations or answer "where is [planet] tonight?" questions.Apache 2.0
- Check the motion status of planets Mercury through Neptune using real JPL ephemeris data. Get direct, retrograde, or stationary status with astrological interpretation for software development decisions.Creative Commons Zero v1.0 Universal
Matching MCP Servers
- Alicense-qualityBmaintenanceEnables AI agents to deploy applications to AWS with DevOps capabilities by automatically inferring infrastructure needs from code and generating inspectable Infrastructure as Code specifications.Last updated14Apache 2.0
- AlicenseBqualityCmaintenanceEnables querying Amazon Neptune databases and analytics graphs using openCypher or Gremlin. It provides tools for executing queries, retrieving graph schemas, and monitoring connection status.Last updated4Apache 2.0
- Retrieve upcoming retrograde and direct stations for planets in a date range. Get exact station times, longitudes, and zodiac signs to track planetary motion.MIT
- Find retrograde periods for any planet over the last 1-10 years and overlay them with deployment history to discover correlations.Creative Commons Zero v1.0 Universal
- Retrieve the graph schema to identify vertex and edge labels along with their connection patterns for query planning and data exploration.Apache 2.0
- Execute Gremlin queries to retrieve and analyze graph data from Amazon Neptune databases.Apache 2.0
- Execute openCypher queries to retrieve and analyze data from Amazon Neptune graph databases, enabling graph-based insights and relationships exploration.Apache 2.0
- Calculate a complete Western natal chart using the tropical zodiac and Swiss Ephemeris. Returns 10 planet positions with Placidus (or chosen) house placements, essential dignities, all active aspects, and element/modality/hemisphere balance statistics. SECTION: WHAT THIS TOOL COVERS Tropical natal chart: Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto. Each planet returns tropical longitude, sign, house (1–12), retrograde flag, dignity label (domicile/exaltation/detriment/fall/peregrine), dignity score (domicile +5, exaltation +4, triplicity +3, term +2, face +1, detriment -5, fall -4), is_exaltation_degree (within 1° of exact exaltation), dignity_disputed (true for outer planets where exaltation/fall is disputed among modern astrologers). Aspect orbs: conjunction/opposition 5°, square/trine 5°, sextile 3°, minor aspects 1.5°. Not Vedic sidereal (asterwise_get_natal_chart). SECTION: WORKFLOW BEFORE: None — this tool is standalone. AFTER: asterwise_get_western_transits_daily — layer current transits over this natal chart. AFTER: asterwise_get_western_synastry — compare this chart against a partner's chart. AFTER: asterwise_get_western_solar_return — annual return chart for the current year. SECTION: INPUT CONTRACT birth.date — YYYY-MM-DD. Example: '1985-11-12' birth.time — HH:MM (24-hour local time). Example: '06:45' birth.lat — Decimal degrees, north positive. Example: 19.076 (Mumbai) birth.lon — Decimal degrees, east positive. Example: 72.8777 (Mumbai) birth.timezone — IANA timezone string. Example: 'Asia/Kolkata', 'America/New_York', 'Europe/Rome', 'UTC'. Default: UTC. IMPORTANT: Timezone defaults to UTC — always supply the correct local timezone for accurate house cusps. An incorrect timezone shifts the Ascendant. birth.house_system — 'placidus' (default, most common), 'koch', 'equal', 'whole_sign'. Placidus is standard for most Western traditions. Whole sign is traditional/Hellenistic. NOTE: house_system is accepted here but silently ignored by transit, return, synastry, composite, and progression endpoints — those always use the birth location coordinates without house-system selection. ayanamsa — always tropical regardless of any value supplied; field is not present. SECTION: OUTPUT CONTRACT data.zodiac (string — 'tropical') data.house_system (string — the system used) data.ascendant — { longitude (float), sign (string), sign_index (int 0–11), degree_in_sign (float) } data.mc — same shape as ascendant data.planets[] — 10 objects (Sun through Pluto): name (string), longitude (float), sign (string), sign_index (int 0–11) degree_in_sign (float), house (int 1–12) is_retrograde (bool), dignity (string), dignity_score (int) is_exaltation_degree (bool), dignity_disputed (bool) data.houses[] — 12 objects: house (int 1–12), cusp_longitude (float), sign (string) sign_index (int 0–11), degree_in_sign (float) data.aspects[] — each: planet_a (string), planet_b (string), type (string) exact_angle (float), orb (float), is_applying (bool) data.elements — { fire (int), earth (int), air (int), water (int), dominant (string) } data.modalities — { cardinal (int), fixed (int), mutable (int), dominant (string) } data.hemisphere — { eastern (int), western (int), northern (int), southern (int) } data.ayanamsa_value (float — 0.0 for tropical) data.ayanamsa_used (string — 'tropical') data.birth_time_provided (bool) SECTION: RESPONSE FORMAT response_format=json serialises the complete response as indented JSON — use this for programmatic parsing, typed clients, and downstream tool chaining. response_format=markdown renders the same data as a human-readable natal report. Both modes return identical underlying data. SECTION: COMPUTE CLASS MEDIUM_COMPUTE (~300ms) SECTION: ERROR CONTRACT INVALID_PARAMS (local — caught before upstream call): — WesternBirthData Pydantic violations (date pattern, time pattern, lat/lon bounds) → MCP INVALID_PARAMS INVALID_PARAMS (upstream): — None expected for valid coordinates and dates post-1800. INTERNAL_ERROR: — Any upstream API failure or timeout → MCP INTERNAL_ERROR Edge cases: — Polar latitudes (above ~65°N or below ~65°S) may cause Placidus house calculation failure; use whole_sign or equal house system for polar births. — time='00:00' accepted; lagna-sensitive results are unreliable for unknown birth times. SECTION: DO NOT CONFUSE WITH asterwise_get_natal_chart — Vedic sidereal chart using Lahiri ayanamsa; different zodiac, different house system, different planet set (9 grahas vs 10 tropical planets). asterwise_get_western_aspects — takes raw longitudes as input; use when you already have positions and don't need full chart computation.Connector
- Next return chart for any planet after a given date. Finds the exact moment the specified planet returns to its natal tropical longitude and builds a complete Western natal chart for that moment at the birth location. SECTION: WHAT THIS TOOL COVERS Generalised return for any of the 10 classical tropical bodies — Mercury returns (yearly-ish), Venus (~1 year), Mars (~2 years), Jupiter (~12 years), Saturn (~29 years), through Pluto (~248 years). SECTION: WORKFLOW BEFORE: asterwise_get_western_natal. AFTER: None. SECTION: INPUT CONTRACT birth — WesternBirthData. planet — one of Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune, Pluto. after_date (optional YYYY-MM-DD) — defaults to today. SECTION: OUTPUT CONTRACT Same shape as solar return: planet name, natal_longitude, return_utc, return_jd, chart SECTION: RESPONSE FORMAT response_format=json serialises the complete response as indented JSON. response_format=markdown renders the same data as a human-readable report. Both modes return identical underlying data. SECTION: COMPUTE CLASS SLOW_COMPUTE for outer planets (Jupiter+ return can search years ahead) SECTION: ERROR CONTRACT INVALID_PARAMS (local): planet not in the valid 10-planet set → MCP INVALID_PARAMS locally. INTERNAL_ERROR: Any upstream API failure or timeout → MCP INTERNAL_ERROR Edge cases: Neptune return takes ~165 years — only useful for generational analysis, not individual lifetime prediction. Pluto return: ~248 years, never completes in one lifetime. SECTION: DO NOT CONFUSE WITH asterwise_get_western_solar_return — Sun-only shortcut. asterwise_get_western_lunar_return — Moon-only shortcut.Connector