Skip to main content
Glama
astroway-mcp

astroway-mcp

Official
by astroway

Related Servers

Alternatives to astroway-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      B
      maintenance
      Precision-audited astrology MCP for natal charts, transits, synastry and moon phases. No API key.
      10
      91 npm
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to compute natal charts, horoscopes, synastry, transits, Vedic kundli, panchang, tarot, numerology and other insight domains through 258+ typed tools, hosted as Remote MCP over Streamable HTTP or run locally over stdio with one key.
      39
      439 npm
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Astrology MCP server that computes natal charts, transits, synastry, progressions, returns, eclipses, retrogrades, and moon phases from a real ephemeris, enabling AI agents to provide accurate astrological calculations without hallucination.
      12
      75 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients and LLMs to compute Vedic astrology charts, including 47 ayanamsha modes, 20 divisional charts, Vimshottari dasha, transits, Panchanga, and related calculations from birth details. It also resolves places to timezone and coordinates and exposes configuration and server-status tools.
      AGPL 3.0

    TDQS

    C2.6/5.0

    Scored across 827 tools

    Disambiguation2/5

    The surface contains many overlapping tools: Vedic compatibility has ashtakoot, dashakoota, full, couple-report, and separate porutham endpoints that return heavily overlapping answers; reports_generate duplicates 12 type-specific report tools; and every numerology operation is repeated across five systems. Detailed descriptions help, but at 827 tools an agent will frequently struggle to choose the right endpoint.

    Naming Consistency3/5

    Names are consistently snake_case with an astroway_ prefix, but structural conventions vary widely: noun-first names, endpoint-derived suffixes like _slug and _id_test, embedded group names, and extremely long per-sign names such as astroway_zodiac_signs_per_sign_deep_zodiac_aquarius. It remains readable but is not a predictable verb_noun scheme.

    Tool Count1/5

    827 tools is far beyond any reasonable scoped tool surface and is an extreme mismatch for agent use, overwhelming context and selection even when grouped. Many endpoints exist only as fine-grained variants that should be parameters or aggregated tools.

    Completeness4/5

    The domain coverage is enormous: Western, Vedic, Chinese, BaZi, Human Design, tarot, numerology, geomancy, reports, geo, and webhooks are all represented. Gaps remain, such as missing webhook delete/update operations and placeholder or deprecated endpoints, but the core surface is unusually comprehensive.

    Maintenance

    ActivityNo data
    ResponsivenessOutdated data