Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Western Astrology MCP Server by RoxyAPI

REMOTE · ROXYAPI.COM

Western natal charts, horoscopes, transits and synastry for AI agents, verified vs NASA JPL.

Available components

0 this week 87 Trust /100

Last scanned (10 hours ago)

Scores higher than 94% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability73
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 19463 tokens (~499/item across 39 items; 39 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Tools include usage examples.Pass
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
  • 99% of tool parameters carry a description.Partial
  • Structured output schemas are declared (95% 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 39 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 39 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
Changelog

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.

  • 29 Oct 26 0
    • Tool “post_astrology_progressions” rewrote its description, which is the text the model reads security
    • “post_astrology_progressions” added an optional parameter “houseSystem” cosmetic
    • “post_astrology_lilith” reworded the description of “houseSystem” cosmetic
  • 28 Oct 26 0
    • “get_astrology_moon_phase_current” reworded the description of “timezone” cosmetic
    • “post_astrology_transits” reworded the description of “timezone” cosmetic

    2 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 21 Oct 26 0
    • Stability: fail → pass ▲ security
  • 20 Oct 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 95 to 98.

  • 10 Oct 26 0
    • Tool “get_astrology_moon_phase_upcoming” rewrote its description, which is the text the model reads security
  • 3 Oct 26 0
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
    • “post_astrology_transit_aspects” reworded the description of “transitTime” cosmetic
  • 1 Oct 26 86
    • “get_astrology_moon_phase_calendar_year_month” reworded the description of “year” cosmetic
    • “post_astrology_aspects_monthly” reworded the description of “year” cosmetic
    • “post_astrology_ecliptic_crossings” reworded the description of “year” cosmetic
    • “post_astrology_parallels_monthly” reworded the description of “year” cosmetic
    • “post_astrology_planets_monthly” reworded the description of “year” cosmetic
    • “post_astrology_transits_monthly” reworded the description of “year” cosmetic

    6 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 30 Sept 26 0
    • “post_astrology_planetary_returns” reworded the description of “approximateDate” cosmetic

    1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.

Diagnostics

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://roxyapi.com/mcp/astrology

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=roxyapi.com CN=WE1,O=Google Trust Services,C=US 23 Sept 2026 22 Dec 2026 ECDSA 256 ECDSA-SHA256 b253589252f3f4620e758a7554771c71
SANs: roxyapi.com, *.roxyapi.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of roxyapi.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
roxyapi.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' 'inline-speculation-rules' 'unsafe-eval' https://challenges.cloudflare.com https://cdn.jsdelivr.net https://static.cloudflareinsights.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https:; font-src 'self'; connect-src 'self' https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src 'self' https://challenges.cloudflare.com https://roxyapi.github.io; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(self), usb=(), bluetooth=(), accelerometer=(), gyroscope=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://roxyapi.com/mcp/astrology Verified 200
http (plaintext) http://roxyapi.com/mcp/astrology HTTPS enforced 301 https://roxyapi.com/mcp/astrology
MCP tools · 39 exposed · ~19,463 tokens

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 →

Tool Tokens
post_astrology_profections ~698

Calculate the annual profection and lord of the year for any birth chart and target date using the Hellenistic time lord technique. Each completed year of life advances the rising sign by one whole sign house, activating a new profected house, profected sign, and ruling planet that sets the tone of the year. Returns the age, profected house and sign, the lord of the year with its natal sign and house placement, and a plain language interpretation for traditional and Hellenistic astrology apps.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
houseSystemstring–House system used only to report where the lord of the year sits in the natal chart. The profected house and sign always use whole sign profection from the rising sign. Placidus (default), Whole Sign…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
longitudenumberyesBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
targetDatestringyesDate whose profection year you want, in YYYY-MM-DD format. The completed whole years from the birth date to this date select the profected house and sign. Must fall on or after the birth date.
timestringyesBirth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
timezone–yesTimezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
ageintegeryes–
birthDetailsobjectyes–
interpretationstringyes–
lordNatalPositionobjectyes–
lordOfYearstringyes–
profectedHouseintegeryes–
profectedSignstringyes–
summarystringyes–
targetDatestringyes–
{"date":"1990-07-15","latitude":40.7128,"longitude":-74.006,"targetDate":"2025-08-04","time":"14:30:00","timezone":"America/New_York"}
post_astrology_progressions ~746

Generate the secondary progressed chart for any date using the day-for-a-year key. Each day of ephemeris motion after birth stands in for one year of life. Returns every progressed body with its sign, degree, natal house, motion, and retrograde state, plus the progressed Ascendant and Midheaven via the Naibod arc. The progressed Sun and progressed Moon are the headline timing markers for inner growth and emotional chapters. Secondary progressions API, progressed chart calculator, progressed Sun and Moon, progressed Ascendant and Midheaven.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
houseSystemstring–House system of the natal chart that every progressed body is placed in. Pass the system the natal chart was drawn in so the house numbers match it. Placidus (default) is the most widely used in West…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
longitudenumberyesBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
targetDatestringyesDate to progress the chart to, in YYYY-MM-DD format. Usually today or a forecast date. The day-for-a-year key turns the elapsed years since birth into the same number of ephemeris days after the birt…
timestringyesBirth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
timezone–yesTimezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
ascendantobjectyes–
birthDetailsobjectyes–
elapsedYearsnumberyes–
midheavenobjectyes–
planetsarrayyes–
progressedDatestringyes–
summarystringyes–
targetDatestringyes–
{"date":"1990-07-15","latitude":40.7128,"longitude":-74.006,"targetDate":"2025-07-15","time":"14:30:00","timezone":"America/New_York"}
post_astrology_relocation_chart ~588

Calculate a relocation chart (relocated birth chart) for a new place on Earth. The birth moment stays the same, so every planet keeps its natal sign and degree, while the Ascendant, Midheaven, Vertex, and all twelve house cusps are recomputed for the new latitude and longitude. Returns the relocated houses and angles, the planets that change house, the angular planets activated at the new place, and the distance and compass direction from the birthplace. Built for relocation astrology readings, astrocartography style move planning, and travel charts. Verified against NASA JPL Horizons.

NameTypeReqDescription
birthLatitudenumberyesBirthplace latitude in decimal degrees (-90 to 90). Used for the original natal angles and houses that the relocated chart is compared against.
birthLongitudenumberyesBirthplace longitude in decimal degrees (-180 to 180). Positive East, negative West.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth date in YYYY-MM-DD format. The birth moment is unchanged by relocation, so this still defines the planetary positions of the chart.
houseSystemstring–House system for dividing the relocated chart into 12 houses. Placidus (default) is time-sensitive and most popular in Western astrology. Whole Sign assigns one sign per house. Equal divides into 30…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
relocationLatitudenumberyesNew location latitude in decimal degrees (-90 to 90). The relocated Ascendant and house cusps are most sensitive to north-south movement.
relocationLongitudenumberyesNew location longitude in decimal degrees (-180 to 180). The relocated Midheaven shifts roughly one degree per degree of longitude moved.
timestringyesBirth time in 24-hour HH:MM:SS format. Combined with the timezone it fixes the exact birth instant, which the relocated angles and houses are recomputed for.
timezone–yesBirth timezone: decimal hours from UTC (e.g. -5 for EST, 5.5 for IST) OR IANA name (e.g. "America/New_York"). Resolved to the offset in force at the birth date and time. This is the birthplace timezo…
NameTypeReqDescription
ascendantobjectyes–
birthDetailsobjectyes–
changesobjectyes–
houseSystemstringyes–
housesarrayyes–
interpretationobjectyes–
midheavenobjectyes–
planetsarrayyes–
relocationobjectyes–
vertexobjectyes–
{"birthLatitude":21.3069,"birthLongitude":-157.8583,"date":"1961-08-04","relocationLatitude":40.7167,"relocationLongitude":-74.006,"time":"19:24:00","timezone":-10}
post_astrology_solar_arc ~645

Calculate a solar arc directed chart for any birth moment and target date. The solar arc is the secondary-progressed Sun longitude minus the natal Sun longitude, about one degree for each year of life, and every natal point including the Ascendant and Midheaven is advanced forward by that same arc. Returns the solar arc, each directed point with its natal and directed longitude, zodiac sign, degree, and a plain language interpretation, for predictive astrology apps timing major life events. Built on accurate tropical chart positions, no astronomy expertise needed.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestringyesBirth date in YYYY-MM-DD format. Determines planetary positions for the specific calendar day.
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesBirth location latitude in decimal degrees (-90 to 90). Positive = North, negative = South.
longitudenumberyesBirth location longitude in decimal degrees (-180 to 180). Positive = East, negative = West.
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
targetDatestringyesDate to direct the chart to, in YYYY-MM-DD format. Every natal point is advanced by the solar arc accumulated from birth to this date, about one degree for each year of life.
timestringyesBirth time in 24-hour HH:MM:SS format. Determines the Ascendant (rising sign) and house cusps. Use 12:00:00 if unknown.
timezone–yesTimezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved to…
NameTypeReqDescription
birthDetailsobjectyes–
directedarrayyes–
solarArcnumberyes–
summarystringyes–
targetDatestringyes–
{"date":"1990-07-15","latitude":40.7128,"longitude":-74.006,"targetDate":"2025-07-15","time":"14:30:00","timezone":"America/New_York"}
post_astrology_solar_return ~486

Generate a solar return chart for any year, the foundational technique for annual astrological forecasting. The chart is cast for the exact moment the transiting Sun returns to its natal ecliptic longitude (your astrological birthday). Returns full tropical zodiac chart with planetary positions, house cusps, aspects, Ascendant, and Midheaven. Location-sensitive: relocating your solar return chart to a different city changes the houses and Ascendant. Solar return chart API, annual horoscope forecast, birthday chart calculator, yearly astrology prediction, relocated solar return.

NameTypeReqDescription
birthDatestringyesOriginal birth date in YYYY-MM-DD format. Used to determine natal Sun longitude for the solar return calculation.
birthTimestringyesOriginal birth time in 24-hour HH:MM:SS format. Determines exact natal Sun position for annual return timing.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
houseSystemstring–House system for the solar return chart. Placidus (default) is most common in Western astrology. Whole Sign, Equal, and Koch also supported.
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
latitudenumberyesLatitude of the solar return location in decimal degrees (-90 to 90). Use current residence or travel location at time of birthday. Solar return charts are location-sensitive.
longitudenumberyesLongitude of the solar return location in decimal degrees (-180 to 180). Affects house cusps and Ascendant of the return chart.
returnYearintegeryesYear for which to cast the solar return chart. The chart is erected for the exact moment the transiting Sun conjuncts the natal Sun longitude in this year.
timezone–yesDecimal hours from UTC OR IANA name (e.g. "America/New_York"). IANA resolved to the DST-correct offset for the birthDate. Output datetime is adjusted to this timezone.
NameTypeReqDescription
birthDatestringyes–
chartobjectyes–
interpretationobjectyes–
locationobjectyes–
natalSunPositionobjectyes–
solarReturnDatestringyes–
solarReturnYearnumberyes–
{"birthDate":"1990-07-15","birthTime":"14:30:00","latitude":40.7128,"longitude":-74.006,"returnYear":2026,"timezone":"America/New_York"}
post_astrology_synastry ~259

Calculate complete synastry (relationship compatibility) between two natal charts using Western tropical astrology. Analyzes inter-chart aspects between all planets to determine romantic, friendship, and karmic compatibility. Returns compatibility score (0-100), detailed inter-aspects with strength ratings, harmonious vs challenging aspect counts, and relationship dynamics analysis. Perfect for dating apps, matrimonial sites, relationship counseling tools, and astrology compatibility features. Based on professional astrological techniques.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
houseSystemstring–House system for both natal charts. Placidus (default), Whole Sign, Equal, or Koch.
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
person1objectyes–
person2objectyes–
NameTypeReqDescription
analysisobjectyes–
compatibilityScorenumberyes–
interAspectsarrayyes–
person1objectyes–
person2objectyes–
summaryobjectyes–
{"person1":{"date":"1990-07-15","latitude":40.7128,"longitude":-74.006,"time":"14:30:00","timezone":"America/New_York"},"person2":{"date":"1990-07-15","latitude":40.7128,"longitude":-74.006,"time":"14:30:00","timezone":"America/New_York"}}
post_astrology_transit_aspects ~591

Calculate all transit-to-natal aspects with detailed interpretations, strength ratings, and timing guidance. Compares current (or future) planetary positions against your natal chart to identify active transits. Returns aspect type, orb, applying/separating status, narrative interpretation, impact rating, and practical guidance for each transit. Like /astrology/transits with a natalChart, returns summary, timing, impact, guidance, and keywords for each aspect. Adds planet, aspect-type, and minStrength filtering plus summary.strongest and summary.byType rollups. Transit aspects API, transit-to-natal analysis, predictive astrology, personalized transit forecast.

NameTypeReqDescription
aspectTypesarray–Filter to specific aspect types (conjunction, opposition, trine, square, sextile, etc.). Omit to include all aspect types.
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
houseSystemstring–House system used to divide the natal chart into 12 houses. Every house number in the response is read against these natal cusps, for the natal bodies and the transiting bodies alike. Placidus (defau…
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
minStrengthnumber–Minimum aspect strength threshold (0-100). Higher values return only tighter, more potent aspects. Useful for filtering out wide-orb aspects.
natalChartobjectyesNatal chart birth details (date, time, location, timezone). Used to calculate natal planetary positions that transits are compared against.
planetsarray–Filter to specific transiting planets. Omit to include all planets. Useful for focusing on slow-moving outer planet transits (Saturn, Jupiter, Pluto).
transitDatestring–Transit date in YYYY-MM-DD format. Defaults to current date if omitted. Use future dates for predictive transit analysis.
transitTimestring–Transit time in HH:MM:SS format, read on the clock of the natal chart timezone at the transit date (an IANA zone takes the offset in force on that date, daylight saving included). Defaults to 12:00:0…
NameTypeReqDescription
ascendantobjectyes–
aspectsarrayyes–
houseSystemstringyes–
housesarrayyes–
natalPlanetsarrayyes–
summaryobjectyes–
transitDatestringyes–
transitPlanetsarrayyes–
{"natalChart":{"date":"1990-07-15","latitude":40.7128,"longitude":-74.006,"time":"14:30:00","timezone":"America/New_York"}}
post_astrology_transits ~545

Calculate current or future planetary transits (positions of all bodies now). Optionally compare transits to natal chart to find transit-to-natal aspects. Returns all 14 celestial bodies (the 10 classical planets, the lunar nodes, Chiron, and Black Moon Lilith) with signs, degrees, and speeds. When natal chart provided, includes transit aspects (transiting Sun conjunct natal Mars, etc.) with orbs and applying/separating status. Perfect for daily transit forecasts, aspect alerts, and personalized transit reports.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
datestring–Transit date in YYYY-MM-DD format (defaults to current date)
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
natalChartobject–Optional natal chart data to compare transits against
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timestring–Transit time in HH:MM:SS format (defaults to current time)
timezone––Transit timezone: decimal hours from UTC OR IANA name (e.g. "America/New_York"). IANA resolved to the DST-correct offset for the transit date. When `date` or `time` is omitted, the current moment is…
NameTypeReqDescription
summaryobject––
timezonenumberyes–
transitAspectsarray––
transitDatestringyes–
transitPlanetsarrayyes–
transitTimestringyes–
{}
post_astrology_transits_monthly ~610

Get every tropical sign change for a given month, for all 14 Western bodies: the Sun through Pluto, both lunar nodes, Chiron and Black Moon Lilith. Returns the starting sign of each body on the first of the month and then each ingress with its exact date and time in your timezone. Omit year and month to get the month in progress, so a published transit calendar stays current without a redeploy. Essential for transit calendars, monthly forecast copy, retrograde and ingress tracking, and newsletter automation. Monthly transit API, planetary ingress calendar, sign change dates, tropical transit table. Verified against NASA JPL Horizons, with the four cardinal ingresses cross-checked against published equinox and solstice times.

NameTypeReqDescription
compactboolean–Set true for the same data in a compact shape: arrays of same-shaped objects arrive columnar as {"__cols":[names],"__rows":[[values]]}. Lossless, typically 40 to 52 percent fewer tokens.
langstring–Response language (BCP 47). Supported: en, tr, de, es, hi, pt, fr, ru, zh-Hans, zh-Hant. Defaults to en. Coverage varies by domain, and a field with no translation in the requested language returns E…
monthinteger–Month number (1-12). Defaults to the current month (UTC).
nodeTypestring–Lunar node convention. "mean" is the smoothed average node, which always moves retrograde; "true" is the osculating node, which tracks the real perturbed node, oscillates up to about 1.5 degrees eith…
timezone––Timezone: an IANA name (e.g. "America/New_York", "Europe/London", or `cities[0].timezone` from /location/search) or decimal hours from UTC (e.g. -5 for EST, 5.5 for IST). An IANA name is resolved onc…
yearinteger–Year for the monthly transit table (1551 to 2649). Defaults to the current year (UTC).
NameTypeReqDescription
monthnumberyes–
startingPositionsarrayyes–
timezonenumberyes–
transitEventsarrayyes–
yearnumberyes–
{}
Install

How do I install the Western Astrology MCP Server by RoxyAPI server?

Western Astrology MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/mcp/astrology, 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 · roxyapi.com

# add to Claude Code
claude mcp add --transport http com-roxyapi-astrology 'https://roxyapi.com/mcp/astrology'
Common questions

What is the Western Astrology MCP Server by RoxyAPI server?

Western Astrology MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/astrology. Western natal charts, horoscopes, transits and synastry for AI agents, verified vs NASA JPL. This page covers its hosted endpoint (https://roxyapi.com/mcp/astrology).

Is the Western Astrology MCP Server by RoxyAPI server safe to use?

Western Astrology MCP Server by RoxyAPI scores 87 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 Western Astrology MCP Server by RoxyAPI server expose?

Western Astrology MCP Server by RoxyAPI exposes 39 tools: get_astrology_signs, get_astrology_signs_id, get_astrology_planet_meanings, get_astrology_planet_meanings_id, post_astrology_natal_chart, and 34 more. Their descriptions and schemas cost roughly 19,463 tokens of context every time the server is loaded.

Does the Western Astrology MCP Server by RoxyAPI server require authentication?

No. We connected to Western Astrology MCP Server by RoxyAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Western Astrology MCP Server by RoxyAPI server still maintained?

Western Astrology MCP Server by RoxyAPI 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.