Astro Agents Verifiable Planetary Timing Data And Astrology

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-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

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;
• returns typed, structured results: every MCP tool declares an outputSchema for its structuredContent;
• 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

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 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.ownershipProofs in /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.