Astrology Forecast MCP Server by RoxyAPI

REMOTE · ROXYAPI.COM · SCANNED AUG 3

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

Available components

+5 this week 65 65 Trust /100

Trust breakdown (6 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 →

Endpoint Security63

The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail

Transport & Reachability100

Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass

Schema Quality & AI Usability56

AI-judged instruction clarity (excellent).Pass
Context-footprint check failed: tool/resource definitions use about 2426 tokens (~485/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management27

Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

remote · roxyapi.com

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

claude mcp add --transport http com-roxyapi-forecast https://roxyapi.com/mcp/forecast

# ~/.codex/config.toml

[mcp_servers.com-roxyapi-forecast]
url = "https://roxyapi.com/mcp/forecast"

// opencode.json

{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-roxyapi-forecast": {
      "type": "remote",
      "url": "https://roxyapi.com/mcp/forecast",
      "enabled": true
    }
  }
}

# add to OpenClaw

openclaw mcp add com-roxyapi-forecast --url https://roxyapi.com/mcp/forecast --transport streamable-http

# ~/.hermes/config.yaml

mcp_servers:
  com-roxyapi-forecast:
    url: "https://roxyapi.com/mcp/forecast"

// mcp.json

{
  "mcpServers": {
    "com-roxyapi-forecast": {
      "type": "http",
      "url": "https://roxyapi.com/mcp/forecast"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

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.

2 Aug 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
1 Aug 26 0
- Endpoint reachability: unreachable → reachable ▲ functional
31 Jul 26 +2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
29 Jul 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: pass → unverified ▼ security
- Stability: 0.07 → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- First check of Schema quality: unverified functional
28 Jul 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
26 Jul 26 60

First indexed and scored.

Show 6 earlier entries Hide earlier entries

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 3 Aug 2026 · Probed https://roxyapi.com/mcp/forecast

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	26 Jul 2026	24 Oct 2026	ECDSA 256	ECDSA-SHA256	fb04ac30ca01abb60e3558bdfadfe2f4
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

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' https://cdn.jsdelivr.net; img-src 'self' data: https:; font-src 'self' https://fonts.scalar.com; connect-src 'self' https://api.scalar.com https://challenges.cloudflare.com https://cloudflareinsights.com; frame-src 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=()

Transports 2 probes

Transport	URL	Outcome	Status	Location
streamable-http	https://roxyapi.com/mcp/forecast	Verified	200
http (plaintext)	http://roxyapi.com/mcp/forecast	HTTPS enforced	301	https://roxyapi.com/mcp/forecast

MCP tools — 5 exposed · ~2,426 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.

Tool Tokens

post_forecast_digest Forecast digest - Pre-summarized next 24h, 7d, 30d, and 90d rollups ~477

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 scanning the full event list.

Input Output Examples

Name	Type	Req	Description
birthData	object	yes	The single birth subject this digest is built for. One object only, never an array.
compact	boolean	—	Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie…
domainWeights	object	—	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 wes…
domains	array	—	Which forecast domains to include before rolling up the windows. Defaults to all three.
lang	string	—	Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
minSignificance	number	—	Drop events scoring below this significance threshold from 0 to 100 before the rollup. Defaults to 0.
startDate	string	—	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.
top	integer	—	Number of highest-significance events to surface per window. Defaults to 3, capped at 20.

No output schema declared.

No examples provided.

post_forecast_significant_dates Significant dates - High-significance cross-domain forecast highlights ~462

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 for what-is-coming highlights, timing alerts, and at-a-glance forecast strips.

Input Output Examples

Name	Type	Req	Description
birthData	object	yes	The single birth subject this forecast is built for. One object only, never an array.
compact	boolean	—	Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie…
domainWeights	object	—	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 wes…
domains	array	—	Which forecast domains to consider before filtering by significance. Defaults to all three.
endDate	string	—	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.
lang	string	—	Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
minSignificance	number	—	Significance floor from 0 to 100 for what counts as a significant date. Defaults to 70.
startDate	string	—	First day of the window in YYYY-MM-DD format. Defaults to today in UTC.

No output schema declared.

No examples provided.

post_forecast_solar_return Solar return chart - Annual birthday forecast chart for a single subject ~630

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 geography, or the current city for a relocated solar return where the houses and Ascendant shift to where you are on your birthday. Built for year-ahead forecast tools, birthday charts, and annual horoscope features.

Input Output Examples

Name	Type	Req	Description
compact	boolean	—	Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie…
date	string	yes	Birth date in YYYY-MM-DD format. Anchors the natal Sun longitude the transiting Sun returns to each year.
houseSystem	string	—	House system for the return chart. placidus is the Western default. whole-sign, equal, and koch are also supported.
lang	string	—	Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
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…
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.
time	string	yes	Birth time in 24-hour HH:MM:SS format. Pins the exact natal Sun position that defines the solar return moment.
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 D…
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.

No output schema declared.

No examples provided.

post_forecast_timeline Cross-domain forecast timeline - Transits, ingresses, stations, dasha changes, critical days ~485

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. Built for what-is-coming dashboards, daily and weekly forecast feeds, and timing tools.

Input Output Examples

Name	Type	Req	Description
birthData	object	yes	The single birth subject this forecast is built for. One object only, never an array.
compact	boolean	—	Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie…
domainWeights	object	—	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 wes…
domains	array	—	Which forecast domains to include. Defaults to all three. Pass a subset to scope the timeline to one or two engines.
endDate	string	—	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.
lang	string	—	Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
minSignificance	number	—	Drop events scoring below this significance threshold from 0 to 100. Defaults to 0, keeping all events.
startDate	string	—	First day of the forecast window in YYYY-MM-DD format. Defaults to today in UTC.

No output schema declared.

No examples provided.

post_forecast_transits Western astrology forecast - aspects, ingresses, stations, eclipses, moon phases ~372

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.

Input Output Examples

Name	Type	Req	Description
birthData	object	yes	The single birth subject this transit forecast is built for. One object only, never an array.
compact	boolean	—	Set true to receive the exact same data in a token-optimized shape that is cheaper for you to read: whitespace is stripped and every array of same-shaped objects is encoded columnar as {"__cols":[fie…
endDate	string	—	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.
lang	string	—	Response language (ISO 639-1). Supported: en, tr, de, es, hi, pt, fr, ru. Defaults to en. Languages without translations yet return English.
minSignificance	number	—	Drop transit events scoring below this significance threshold from 0 to 100. Defaults to 0.
startDate	string	—	First day of the transit window in YYYY-MM-DD format. Defaults to today in UTC.

No output schema declared.

No examples provided.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

26 Jul 3 Aug

Day	Score
26 Jul	60
27 Jul	60
28 Jul	61
29 Jul	61
30 Jul	62
31 Jul	64
1 Aug	64
2 Aug	65
3 Aug	65