Astrology Forecast MCP Server by RoxyAPI
REMOTE · ROXYAPI.COM · SCANNED SEP 20
Astrology transit forecasts, timelines and significant-date feeds for AI agents.
Available components
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
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2243 tokens (~448/item across 5 items; 5 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
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Astrology Forecast MCP Server by RoxyAPI server?
Astrology Forecast MCP Server by RoxyAPI is a hosted endpoint at https://roxyapi.com/mcp/forecast, 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
claude mcp add --transport http com-roxyapi-forecast 'https://roxyapi.com/mcp/forecast'
{
"mcpServers": {
"com-roxyapi-forecast": {
"url": "https://roxyapi.com/mcp/forecast"
}
}
} {
"servers": {
"com-roxyapi-forecast": {
"type": "http",
"url": "https://roxyapi.com/mcp/forecast"
}
}
} [mcp_servers.com-roxyapi-forecast] url = "https://roxyapi.com/mcp/forecast"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-roxyapi-forecast": {
"type": "remote",
"url": "https://roxyapi.com/mcp/forecast",
"enabled": true
}
}
} openclaw mcp add com-roxyapi-forecast --url 'https://roxyapi.com/mcp/forecast' --transport streamable-http
mcp_servers:
com-roxyapi-forecast:
url: "https://roxyapi.com/mcp/forecast" {
"McpServers": {
"com-roxyapi-forecast": {
"Transport": "http",
"Url": "https://roxyapi.com/mcp/forecast"
}
}
} assistant mcp add com-roxyapi-forecast -t streamable-http -u 'https://roxyapi.com/mcp/forecast'
{
"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.
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.
- 17 Sept 26 0
- “post_forecast_solar_return” reworded the description of “timezone” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 29 Aug 26 +1
- Stability: 0.97 → pass security
- 28 Aug 26 −1
- Stability: pass → 0.97 functional
- 26 Aug 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
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Aug 26 0
- Authorization: unverified → partial ▲ security
- Schema quality: 485 → 423 ▲ functional
- Schema quality: fail → pass ▲ functional
- “post_forecast_digest” reworded the description of “compact” cosmetic
- “post_forecast_significant_dates” reworded the description of “compact” cosmetic
- “post_forecast_solar_return” reworded the description of “compact” cosmetic
- “post_forecast_timeline” reworded the description of “compact” cosmetic
- “post_forecast_transits” reworded the description of “compact” cosmetic
- 11 Aug 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
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 20 Sept 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 |
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' 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=() |
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/forecast | Verified | 200 | |
| http (plaintext) | http://roxyapi.com/mcp/forecast | HTTPS enforced | 301 | https://roxyapi.com/mcp/forecast |
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 →
post_forecast_digest Forecast digest - Pre-summarized next 24h, 7d, 30d, and 90d rollups ~433
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.
| 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 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. |
| 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 (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… |
| 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.
{"birthData":{"date":"1990-07-15","time":"13:30:00","timezone":"America/New_York"}}post_forecast_significant_dates Significant dates - High-significance cross-domain forecast highlights ~418
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.
| 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 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. |
| 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 (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… |
| 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.
{"birthData":{"date":"1990-07-15","time":"13:30:00","timezone":"America/New_York"}}post_forecast_solar_return Solar return chart - Annual birthday forecast chart for a single subject ~623
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.
| Name | Type | Req | Description |
|---|---|---|---|
| compact | boolean | – | 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. |
| 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 (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… |
| 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 o… |
| 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.
{"date":"1990-07-15","latitude":40.7128,"longitude":-74.006,"time":"14:30:00","timezone":"America/New_York","year":2026}post_forecast_timeline Cross-domain forecast timeline - Transits, ingresses, stations, dasha changes, critical days ~441
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.
| 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 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. |
| 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 (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… |
| 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.
{"birthData":{"date":"1990-07-15","time":"13:30:00","timezone":"America/New_York"}}post_forecast_transits Western astrology forecast - aspects, ingresses, stations, eclipses, moon phases ~328
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.
| 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 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. |
| 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 (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… |
| 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.
{"birthData":{"date":"1990-07-15","time":"13:30:00","timezone":"America/New_York"}}What is the Astrology Forecast MCP Server by RoxyAPI server?
Astrology Forecast MCP Server by RoxyAPI is listed in the public MCP registry as com.roxyapi/forecast. Astrology transit forecasts, timelines and significant-date feeds for AI agents. This page covers its hosted endpoint (https://roxyapi.com/mcp/forecast).
Is the Astrology Forecast MCP Server by RoxyAPI server safe to use?
Astrology Forecast MCP Server by RoxyAPI scores 88 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 Astrology Forecast MCP Server by RoxyAPI server expose?
Astrology Forecast MCP Server by RoxyAPI exposes 5 tools: post_forecast_timeline, post_forecast_transits, post_forecast_significant_dates, post_forecast_digest, post_forecast_solar_return. Their descriptions and schemas cost roughly 2,243 tokens of context every time the server is loaded.
Does the Astrology Forecast MCP Server by RoxyAPI server require authentication?
No. We connected to Astrology Forecast MCP Server by RoxyAPI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Astrology Forecast MCP Server by RoxyAPI server still maintained?
Astrology Forecast MCP Server by RoxyAPI is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.