MCP servers observed by Lowdown
info.astroway/forecast MCP server: daily status and tool changes
Answered initialize and tools/list on all 4 checks recorded in the last 30 days (2026-11-09 to 2026-11-18) (Lowdown checks this server every 3 days); 44 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-09; tool definitions last changed on 2026-11-15 after 6 days without change; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:info.astroway/forecast
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:info.astroway/forecast?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-18: the server answered initialize and tools/list.
- Observed days in the last 30: 4
- Answered initialize and tools/list: 4
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 4 observed days. Lowdown checks without credentials.
Did its tools change recently?
Tool definitions changed on 1 of 3 compared days.
- 2026-11-15: input or output schemas changed, descriptions changed, tool names changed, server version changed; tool count 45 → 44
What tools does it list?
44 tools on 2026-11-18:
astroway_account_statusastroway_cosmobiology_cosmogramastroway_cosmobiology_dial_90astroway_cosmobiology_eight_harmonic_aspectsastroway_cosmobiology_lefeldt_extensionsastroway_cosmobiology_midpoint_picturesastroway_cosmobiology_personal_point_treeastroway_cosmobiology_sensitive_pointsastroway_cosmobiology_transit_midpointsastroway_cosmobiology_uranian_tnpsastroway_cosmobiology_witte_formulasastroway_cost_estimateastroway_evolutionary_nodal_axis_detailastroway_evolutionary_pluto_natal_conditionastroway_evolutionary_skipped_stepsastroway_evolutionary_soul_typesastroway_evolutionary_yesterday_skyastroway_mcp_agent_debateastroway_mcp_agent_pool_statusastroway_mcp_ai_chatastroway_mcp_ai_comparison_coachastroway_mcp_ai_explain_aspectastroway_mcp_ai_explain_transitastroway_mcp_multi_agent_coordinateastroway_mcp_multi_chart_contextastroway_mcp_rag_searchastroway_mcp_streamingastroway_mcp_tool_call_streamastroway_mcp_tools_listastroway_prognostics_firdariaastroway_prognostics_forecast_calendarastroway_prognostics_lunar_returnastroway_prognostics_minor_progressionsastroway_prognostics_planetary_returnastroway_prognostics_primary_directionsastroway_prognostics_profectionsastroway_prognostics_progressionsastroway_prognostics_rectificationastroway_prognostics_rectification_trutineastroway_prognostics_solar_returnastroway_prognostics_symbolic_directionsastroway_prognostics_tertiary_progressionsastroway_prognostics_transit_calendarastroway_prognostics_transits
MCP Registry declaration
- Registry name:
info.astroway/forecast - Declared version: 0.4.7
- Status: active
- Declared hosts:
mcp.astroway.info
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:info.astroway/forecast", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:info.astroway/forecast?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).