Astro Agents - deterministic Western + Vedic astrology
RemoteAbout Astro Agents - deterministic Western + Vedic astrology
Astro Agents is a deterministic astrology MCP server for agents and astrology applications, covering Western and Vedic chart calculations. It uses NASA/JPL DE440, resolves historical time zones, and returns structured results with verifiable hashes.
Key features
- 01Western and Vedic chart calculations
- 02Historical time-zone resolution
- 03Natal charts, transits, and synastry
- 04Kundli, dashas, yogas, and panchang
- 05Structured results with hash verification
Use cases
- 01Generate a natal chart from birth details
- 02Calculate transits for a natal chart
- 03Compare two charts with synastry
- 04Check Vedic periods, yogas, or compatibility
MCP support
The remote Streamable HTTP MCP server exposes astrology calculation tools, including chart, transit, Vedic, and verification operations. It requires no authentication, and MCP calls are not charged.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://astro-agent.dev/mcpclaude mcp add --transport http aidatatools-dev-astro-agents https://astro-agent.dev/mcp{"mcpServers":{"aidatatools-dev-astro-agents":{"type":"http","url":"https://astro-agent.dev/mcp"}}}Open in Cursor{"servers":{"aidatatools-dev-astro-agents":{"type":"http","url":"https://astro-agent.dev/mcp"}}}Open in VS Code{"mcpServers":{"aidatatools-dev-astro-agents":{"type":"http","url":"https://astro-agent.dev/mcp"}}}{"mcpServers":{"aidatatools-dev-astro-agents":{"serverUrl":"https://astro-agent.dev/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
Tools
16| Parameter | Type | Required | Description |
|---|---|---|---|
| date | string | No | YYYY-MM-DD (use with 'time' instead of 'datetime'). |
| time | string | No | HH:MM or HH:MM:SS, 24 h. Omit if unknown (computed at 12:00 with a TIME_UNKNOWN warning). |
| datetime | string | No | Local birth date-time, ISO 8601: '1990-05-15T14:30' (local clock time at the place) or with an explicit offset '1990-05-15T14:30:00+02:00'. Alternative: 'date' + 'time'. |
| latitude | number | No | Decimal degrees, north positive. |
| timezone | string | No | IANA zone, e.g. 'Asia/Kolkata'. Optional: resolved from the coordinates, with the historical offset (DST, Local Mean Time) of that date. |
| longitude | number | No | Decimal degrees, east positive. |
| time_basis | enum | No | What the given clock time is: civil wall-clock (default), UTC, Local Mean Time, or true (apparent) solar time.civil | utc | lmt | true_solar |
| ambiguous_time | enum | No | Which occurrence to use when a local time happens twice (DST fall-back).earlier | later |
Details
From the project READMEAstro 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-agent.dev/mcp(Streamable HTTP, no auth) - REST API:
https://astro-agent.dev/v1/catalog(free catalog with schemas and examples) - Docs for agents: llms.txt · OpenAPI 3.1 · A2A agent card
What's new in 1.3.0 (2026-10-27)
-
kp_chart($0.15): KP (Krishnamurti Paddhati), with star, sub and sub-sub lords of every graha and Placidus cusp, cuspal sub-lords and A/B/C/D significators. -
yogas($0.10): deterministic yoga detection (Raja, Dhana, Gaja-Kesari, Pancha Mahapurusha, Neecha Bhanga, Kemadruma, Kaal Sarp…), each with the rule applied. -
Accuracy proven against NASA/JPL Horizons: 12,400 comparisons per measurement over 1800–2200.
- Positions agree within 0.024″ (0.0005″ mean).
- The longitude as served agrees within 0.062″ over 1962–2026.
Method and every number: benchmark.md · summary at
/v1/benchmark.
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_sha256andmeta.result_sha256, andverify_result_hashorPOST /v1/verifyrecomputes them; - states every convention in the response: ayanamsa (name and value), house system, orbs, node type, dasha year length, dosha and koota rules;
- returns typed, structured results: every MCP tool declares an
outputSchemafor itsstructuredContent; - 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;
- is benchmarked against NASA/JPL Horizons: positions within 0.024″ over 1800–2200 (benchmark).
Tools
| Tool | What it returns | Price over REST |
|---|---|---|
resolve_birth_time | exact UT, historical UTC offset, Delta T, Local Mean Time, true solar time | $0.01 |
planet_positions | Sun..Pluto, nodes, Lilith: longitude, sign, speed, retrograde | $0.01 |
aspects | aspects with orb, exactness, applying/separating | $0.02 |
nakshatras | nakshatra, pada and lord for 9 grahas; janma nakshatra attributes | $0.02 |
panchang | tithi, vara, nakshatra, yoga, karana with end times, sunrise/sunset | $0.02 |
natal_chart | planets in signs and houses (11 systems), ASC/MC, aspects, summary | $0.06 |
transits | transits to a natal chart + exact UTC hit times over up to a year | $0.08 |
synastry | cross-aspects, house overlays, composite midpoints | $0.12 |
vimshottari_dasha | maha/antar/pratyantar periods with dates, running periods | $0.10 |
yogas | Raja, Dhana, Gaja-Kesari, Pancha Mahapurusha, Neecha Bhanga, Kemadruma... each with its rule | $0.10 |
kundli | sidereal D1 + D9: lagna, grahas, nakshatras, dignities, bhavas | $0.15 |
doshas | Manglik, Kaal Sarp, Sade Sati / Dhaiya with dates | $0.15 |
kp_chart | KP: star, sub and sub-sub lords of grahas and Placidus cusps, A/B/C/D significators | $0.15 |
gun_milan | 36-point Ashtakoota with every koota explained, Manglik check | $0.25 |
kundli_full | all 16 divisional charts D1..D60 | $0.32 |
vedic_report | kundli + dashas + doshas + birth panchang | $0.50 |
astro_catalog, verify_result_hash | catalog; hash verification | free |
Input for every chart: a local datetime ("1990-05-15T14:30"), a latitude and a longitude. The time zone is resolved for you.
Payment: each client gets 3 free calls: on any tool over MCP, or on the five $0.01–0.02 routes over REST (every other REST route is always paid). After that you pay per call over REST with x402 (USDC on Base or Solana) or MPP (Tempo: OUSD or USDC.e). There is no account and no API key. Over MCP, a tool with no free call left returns the paid REST endpoint and its price; nothing is ever charged over MCP. A request with invalid input returns a 400 and is never charged.
Connect
Any MCP client that supports remote Streamable HTTP servers:
{
"mcpServers": {
"astro-agents": { "url": "https://astro-agent.dev/mcp" }
}
}
Hermes Agent (Nous Research):
hermes plugins install aidatatools-dev/astro-agents-mcp --enable # MCP server + astrology skill
Without --enable Hermes installs the plugin disabled; hermes plugins enable astro-agents turns it on. Or by hand:
hermes mcp add astro-agents --url https://astro-agent.dev/mcp # answer "n" to the authentication prompt
hermes skills install aidatatools-dev/astro-agents-mcp/skills/astrology # optional: when and how to use the tools
Any agent that reads Agent Skills (Claude Code, Codex, Cursor and others):
npx skills add aidatatools-dev/astro-agents-mcp
The skill lives in skills/astrology/SKILL.md.
REST:
curl -X POST https://astro-agent.dev/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
- Contact: [email protected]
- Support · Privacy Policy · Terms of Service
- Ownership of the origin is proven by an EIP-191 signature from the Base payout address (
x-discovery.ownershipProofsin/openapi.json).
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.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.