com.astromansion/astrology
AstroMansion
Is the AstroMansion MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.
Our own engine on NASA JPL data, no third-party APIs: natal, transits, synastry and 40+ techniques.
needs auth probed 2026-11-15 · unchanged since 2026-11-11 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"error":"invalid_token","error_description":"Sign in with an AstroMansion account, or send an API key in X-AP- Endpoint
- https://api.astromansion.com/mcp (streamable-http)
- Host
- api.astromansion.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://api.astromansion.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server api.astromansion.com, PKCE S256, grants authorization_code, refresh_token.
Scopes api.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://astromansion.com
- Registry
- active, updated 2026-11-10 · registry entry
Compare this server with others.
More servers
Servers that mention astrology.
- NatalChart.AI Astrology ai.natalchart/astrology · alive
- Asterwise com.asterwise/mcp · alive
- Divine API - Indian / Vedic Astrology com.divineapi/indian · needs auth
- Divine API - Western Astrology com.divineapi/western · needs auth
- Jagannatha Hora — Vedic Astrology (Jyotish, Kundli, Horoscope, Panchang) com.jagannathahora/vedic-astrology · alive
- Jeeva Jyotish com.jeeva-jyotish/reference-search · alive
- Kundlit Vedic Astrology com.kundlit/astro · alive
- Open Ephemeris com.openephemeris/open-ephemeris · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.