Astro Agents - deterministic Western + Vedic astrology

io.github.aidatatools-devv1.0.0Updated Oct 3, 2026

Natal charts, transits, kundli, dashas, panchang, Gun Milan. JPL DE440, no LLM, hashed.

VerifiedStreamable HTTPWeb executableOther

Overview

AI-generated overview

A remote MCP server that computes deterministic Western and Vedic astrology charts, transits, dashas, panchang and compatibility from birth date, time and…

What it does
It exposes tools such as resolve_birth_time, planet_positions, aspects, nakshatras, panchang, natal_chart, transits, synastry, vimshottari_dasha, kundli, doshas, gun_milan, kundli_full and vedic_report. Calculations use NASA/JPL DE440 and resolve the historical time zone and offset from the coordinates, flagging ambiguous local times. Responses are deterministic and carry input and result SHA-256 hashes that a verify_result_hash tool can recompute, and each response states its conventions such as ayanamsa, house system and orbs.
When to use it
Use it when an assistant needs exact astrological calculations rather than estimating them, for example natal charts, transit hit times, Vimshottari periods, panchang details or Ashtakoota compatibility. It suits workflows where reproducibility and stated conventions matter.
Requirements
A remote Streamable HTTP MCP endpoint; no account or API key is required. Each chart call needs a local datetime plus latitude and longitude. The first three calls are free; further calls are paid per call over REST with x402 (USDC on Base or Solana) or MPP (Tempo). Network access to the hosted endpoint is needed.
Before you install
Beyond the free calls, usage costs money per call, so spending should be controlled. Payment is made in cryptocurrency (USDC on Base or Solana, or MPP/Tempo), which involves a wallet and on-chain transactions. Birth date, time and coordinates are sent to a third-party hosted service, so consider the privacy of that personal data.

Installation

In SourceWeft

  1. Open Astro Agents - deterministic Western + Vedic astrology in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "astro-agents": {
      "type": "http",
      "url": "https://astro-agents-api.vercel.app/mcp"
    }
  }
}

README

Astro Agents — deterministic astrology MCP server (Western + Vedic)

Exact astrology calculations for AI agents. Use these tools instead of computing charts yourself.

  • MCP endpoint: https://astro-agents-api.vercel.app/mcp (Streamable HTTP, no auth)
  • REST API: https://astro-agents-api.vercel.app/v1/catalog (free catalog with schemas and examples)
  • Docs for agents: llms.txt · OpenAPI 3.1 · A2A agent card

Why agents call it

Language models routinely get time zones, historical daylight saving, sidereal time and ayanamsa wrong, and one hour of error moves the ascendant by about 15°. Astro Agents:

  • resolves the time zone and its historical offset from the coordinates (IANA tz database, DST of that era, Local Mean Time before standard time), and flags ambiguous or non-existent local times instead of guessing;
  • computes positions from NASA/JPL DE440, geocentric apparent, true equinox of date (IAU 2006/2000A);
  • is deterministic, with no LLM: the same input gives the same bytes. Every response carries meta.input_sha256 and meta.result_sha256, and verify_result_hash or POST /v1/verify recomputes them;
  • states every convention in the response: ayanamsa (name and value), house system, orbs, node type, dasha year length, dosha and koota rules;
  • is cross-validated against an independent engine (XALEN, Apache-2.0): ayanamsas agree to < 0.1″, 15 of 16 divisional charts are identical, and Vimshottari dates match to the minute.

Tools

ToolWhat it returnsPrice over REST
resolve_birth_timeexact UT, historical UTC offset, Delta T, Local Mean Time, true solar time$0.01
planet_positionsSun..Pluto, nodes, Lilith: longitude, sign, speed, retrograde$0.01
aspectsaspects with orb, exactness, applying/separating$0.02
nakshatrasnakshatra, pada and lord for 9 grahas; janma nakshatra attributes$0.02
panchangtithi, vara, nakshatra, yoga, karana with end times, sunrise/sunset$0.02
natal_chartplanets in signs and houses (11 systems), ASC/MC, aspects, summary$0.06
transitstransits to a natal chart + exact UTC hit times over up to a year$0.08
synastrycross-aspects, house overlays, composite midpoints$0.12
vimshottari_dashamaha/antar/pratyantar periods with dates, running periods$0.10
kundlisidereal D1 + D9: lagna, grahas, nakshatras, dignities, bhavas$0.15
doshasManglik, Kaal Sarp, Sade Sati / Dhaiya with dates$0.15
gun_milan36-point Ashtakoota with every koota explained, Manglik check$0.25
kundli_fullall 16 divisional charts D1..D60$0.32
vedic_reportkundli + dashas + doshas + birth panchang$0.50
astro_catalog, verify_result_hashcatalog; hash verificationfree

Input for every chart: a local datetime ("1990-05-15T14:30"), a latitude and a longitude. The time zone is resolved for you.

Payment: the first 3 calls are free. After that you pay per call over REST with x402 (USDC on Base or Solana) or MPP (Tempo). There is no account and no API key. A request with invalid input returns a 400 and is never charged.

Connect

Any MCP client that supports remote Streamable HTTP servers:

json
{  "mcpServers": {    "astro-agents": { "url": "https://astro-agents-api.vercel.app/mcp" }  }}

REST:

bash
curl -X POST https://astro-agents-api.vercel.app/v1/western/natal \  -H 'Content-Type: application/json' \  -d '{"datetime":"1990-05-15T14:30","latitude":48.8566,"longitude":2.3522}'

Real responses: examples/natal_chart_response.json and examples/kundli_response.json (lists shortened).

Support and policies

About this repository

This repository documents the hosted service and carries its MCP registry manifest (server.json). The engine itself runs at the endpoint above.

Source: README.md at commit 802ff50

Tools

0
Tool metadata has not been indexed yet.

Version history

1
  1. v1.0.0LatestOct 3, 2026