Name: Astrology Forecast MCP Server by RoxyAPI
Author: roxyapi

Astrology Forecast MCP Server by RoxyAPI

Astrology transit forecasts, timelines and significant-date feeds for AI agents.

Tool-list grade A Remote · Streamable HTTP API key 5 tools v1.0.1

No reviews yet by roxyapi The publisher’s own endpoint — this marketplace is not in the path

96/100

tool-list score

tools declared

remote

at its publisher

—

calls last 7d

What it does

Astrology transit forecasts, timelines and significant-date feeds for AI agents.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user --transport http astrology-forecast-mcp-server-by-roxyapi https://roxyapi.com/mcp/forecast --header 'X-API-Key: ${X_API_KEY}'

# 2 — ask your agent for something these tools do
#   post_forecast_timeline, post_forecast_transits, post_forecast_significant_dates and 2 more

It needs X_API_KEY (RoxyAPI key from roxyapi.com/account): this sends it in the X-API-Key header from your environment, so export it first — its endpoint answers 401 without it.

Astrology Forecast MCP Server by RoxyAPI costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

roxyapi17 servers

2 categories

All 17 servers

Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.

Installation

Where are you running it?

Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.

Claude Codedeclared by this listing

This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it. Claude Code reads X_API_KEY (RoxyAPI key from roxyapi.com/account) from your environment each time it connects and sends it in the X-API-Key header — its endpoint answers 401 without it — so the key stays out of its config: export it in your shell profile (macOS, Linux), or run setx X_API_KEY … and open a new terminal (Windows).

claude mcp add --scope user --transport http astrology-forecast-mcp-server-by-roxyapi https://roxyapi.com/mcp/forecast --header 'X-API-Key: ${X_API_KEY}'

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add — but its publisher asks for a key of their own on every call.

What it asks of you

It reaches a system of yours, so it needs your own credential rather than the publisher’s: X-API-Key header — RoxyAPI key from roxyapi.com/account. You set it in your own client’s config, on your machine — this marketplace never holds it.

What it writes

One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.

What you approve

5 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.

Tool surface

What the model actually sees. Descriptions are diffed on every release — see version history.

Only tools that write or reach the network

Build one time-ordered forecast for a single birth subject by merging upcoming events across three domains: western transit-to-natal aspects, sign ingresses, retrograde stations, eclipses, and new and full moons; biorhythm critical days; and vedic Vimshottari mahadasha, antardasha, and pratyantardasha boundaries. The window is clamped to 90 days and events are capped and scored by significance. Bu

Parameter	Type	Required	Notes
lang	string	no	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 En
birthData	object	yes	The single birth subject this forecast is built for. One object only, never an array.
startDate	string	no	First day of the forecast window in YYYY-MM-DD format. Defaults to today in UTC.
endDate	string	no	Last day of the forecast window in YYYY-MM-DD format. Defaults to startDate plus 30 days. The window is clamped to a maximum of 90 days from startDate.
domains	array	no	Which forecast domains to include. Defaults to all three. Pass a subset to scope the timeline to one or two engines.
minSignificance	number	no	Drop events scoring below this significance threshold from 0 to 100. Defaults to 0, keeping all events.
domainWeights	object	no	Per-domain significance multipliers applied before the significance floor and event cap. Bias which domains survive filtering and the cap. Omitted domains default to a weight of 1. Valid keys are west
compact	boolean	no	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.

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, an

Parameter	Type	Required	Notes
lang	string	no	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 En
birthData	object	yes	The single birth subject this transit forecast is built for. One object only, never an array.
startDate	string	no	First day of the transit window in YYYY-MM-DD format. Defaults to today in UTC.
endDate	string	no	Last day of the transit window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.
minSignificance	number	no	Drop transit events scoring below this significance threshold from 0 to 100. Defaults to 0.
compact	boolean	no	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.

Return only the high-significance dates from the merged cross-domain forecast for a single birth subject: the rare outer-planet exact transit aspects, slow-planet sign ingresses, retrograde stations, and Vimshottari mahadasha and antardasha changes that mark genuine turning points. Defaults to a significance floor of 70 so the response is a short list of the most meaningful upcoming dates. Built f

Parameter	Type	Required	Notes
lang	string	no	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 En
birthData	object	yes	The single birth subject this forecast is built for. One object only, never an array.
startDate	string	no	First day of the window in YYYY-MM-DD format. Defaults to today in UTC.
endDate	string	no	Last day of the window in YYYY-MM-DD format. Defaults to startDate plus 30 days. Clamped to a maximum of 90 days from startDate.
domains	array	no	Which forecast domains to consider before filtering by significance. Defaults to all three.
minSignificance	number	no	Significance floor from 0 to 100 for what counts as a significant date. Defaults to 70.
domainWeights	object	no	Per-domain significance multipliers applied before the significance floor and event cap. Bias which domains survive filtering and the cap. Omitted domains default to a weight of 1. Valid keys are west
compact	boolean	no	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.

Roll the cross-domain forecast for a single birth subject into four pre-summarized windows: the next 24 hours, 7 days, 30 days, and 90 days from the start date. Each window returns its event count, a per-domain count breakdown, a per-type count breakdown, and the top highest-significance events. Built for a glanceable what-is-coming strip so a caller can render the upcoming highlights without scan

Parameter	Type	Required	Notes
lang	string	no	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 En
birthData	object	yes	The single birth subject this digest is built for. One object only, never an array.
startDate	string	no	Start anchor for every window in YYYY-MM-DD format. The next 24h, 7d, 30d, and 90d windows are measured forward from this date at 00:00:00 UTC. Defaults to today in UTC.
domains	array	no	Which forecast domains to include before rolling up the windows. Defaults to all three.
minSignificance	number	no	Drop events scoring below this significance threshold from 0 to 100 before the rollup. Defaults to 0.
domainWeights	object	no	Per-domain significance multipliers applied before the significance floor and event cap. Bias which domains survive filtering and the cap. Omitted domains default to a weight of 1. Valid keys are west
top	integer	no	Number of highest-significance events to surface per window. Defaults to 3, capped at 20.
compact	boolean	no	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.

Cast the solar return chart for one subject and year: the chart erected for the exact moment the transiting Sun returns to its natal ecliptic longitude, the foundational technique for annual astrological forecasting. Returns the full tropical chart with planetary positions, house cusps, aspects, Ascendant, and Midheaven. Location-sensitive: pass the birthplace to anchor the chart to natal geograph

Parameter	Type	Required	Notes
lang	string	no	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 En
date	string	yes	Birth date in YYYY-MM-DD format. Anchors the natal Sun longitude the transiting Sun returns to each year.
time	string	yes	Birth time in 24-hour HH:MM:SS format. Pins the exact natal Sun position that defines the solar return moment.
year	integer	yes	Year to cast the solar return for. The chart is erected for the moment in this year when the transiting Sun returns to the natal Sun longitude, on or within a day of the birthday.
latitude	number	yes	Latitude of the solar return location in decimal degrees. The solar return is location-sensitive: use the birthplace to anchor the chart to natal geography, or the current city for a relocated solar r
longitude	number	yes	Longitude of the solar return location in decimal degrees. Sets the local sidereal time, so it drives the Ascendant, Midheaven, and house cusps of the return chart.
timezone		yes	IANA name (e.g. "America/New_York", "Europe/London", "UTC"), decimal hours (e.g. -5 for EST, 1 for CET), or a fixed UTC offset (e.g. "-05:00", "+01:00"). Prefer the IANA name: it is resolved to the of
houseSystem	string	no	House system for the return chart. placidus is the Western default. whole-sign, equal, and koch are also supported.
compact	boolean	no	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.

Free

$0 forever

Every tool — any call limit is its publisher’s, not ours
No card, and mcprush charges nothing for it
Runs at its publisher’s own address — this marketplace is not in the path
Nothing to cap, because mcprush bills nothing

Nothing here is billable: mcprush charges nothing to install Astrology Forecast MCP Server by RoxyAPI or to call it, at any volume.

ATool-list grade · score 96 / 100

Release 1.0.1 · scanned 21 Oct 2026

Graded from the tools this server lists, not from its source code.

Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.

Threat score100

Client score96

Findings0 threat · 0 capability

Capabilityminimal

Coveragemanifest

Verificationnot in this report

Surface digest81fdc538cc3e1efc3b0f015447fb800958ff98bce626ae1ac173cd7851c4f670

Score vectorthreat 100 → client 96

Term	Level	What it prices	Points
capability-exposure	minimal	capability blast radius (minimal) — client exposure if the model is manipulated	−0
coverage-honesty	manifest	inspection depth (manifest) — how much of the target the scan could see	−4

score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.

What the scan could actually read

A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.

The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.

Tool surfaceread

Implementation sourcenot available

Package metadatanot available

Live transportnot available

The implementation source was not read — this reflects the declared tool metadata only.

Capability — what it could do if the model were manipulated

Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.

Tool	Capability tags	Why the tag was assigned
post_forecast_timeline	no tags
post_forecast_transits	no tags
post_forecast_significant_dates	no tags
post_forecast_digest	no tags
post_forecast_solar_return	no tags

Toxic-flow graph

The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.

The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.

Supply chain and provenance

Integrityfirst-seen

Surface digest81fdc538cc3e1efc

Scanned2026-10-21

This is the first scan of this surface here, so there is nothing yet to compare it against.

Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.