Astronomical ephemeris and Vedic astrology (Jyotish) engine, written in Rust and exposed as 17 MCP tools: natal charts, panchanga, Vimshottari dashas, vargas, transits and transit search, muhurta search, ashtakavarga, shadbala, karakas, combustion, drishti, bhavas, synastry and composite charts. Runs locally over stdio. No network calls, no telemetry, no API keys and no configuration. **Install:** `cargo install vedaksha-mcp` then `vedaksha-mcp --stdio`, or `docker run --rm -i ghcr.io/arthiqlabs/vedaksha-mcp:v7.2.0 --stdio` (amd64 + arm64). Positions come from a clean-room implementation of VSOP87 and ELP/MPP02, with optional JPL SPK kernels, validated against JPL Horizons on a committed 24,350-row fixture; the SPK path agrees to 0.103 arcsec. Eleven sidereal ayanamsha systems are each derived forward from a primary source rather than tuned to match another implementation, and the derivation for each is recorded in the repository. **Licence:** BUSL-1.1 (source-available). Free for any non-commercial use. Commercial use is a one-time USD $500 per organisation. Each version converts to Apache-2.0 four years after its release.

MCP readiness

B · 83/100

Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here B, 80.5/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ

Valid MCP handshake	10/10	initialize and tools/list both answered.
Live MCP endpoint	25/25	Endpoint answers the MCP initialize handshake (1061 ms).
Protocol revision	6/10	Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.
Signed descriptor	n/a	No MCP standard defines a signed server descriptor.
Uptime (30 days)	15/15	22/22 probes succeeded over 30 days (100%).
Tool declaration	10/10	Lists 17 tool(s) with descriptions.
Verified identity	5/10	Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Freshness + modern flags	4/5	seen in a source within 7 days.
Auth declaration	0/5	How to authenticate is not stated.

Applicable criteria total 90 points, scaled to 100.

Responsiveness: Responsive (1061 ms; bands ≤2.5 s, ≤5 s, ≤8 s, slower; penalty only).

Measured 2026-11-11.

Nine criteria, the same as the A2A readiness score, read from our daily MCP probe (initialize + tools/list) and 30-day probe history. No MCP standard defines a signed server descriptor, so that criterion is n/a and the other 90 points are scaled to 100. Grades: A>=90, B>=75, C>=60, D>=40, F<40. Display only: search order uses the quality grade.

Compared with peers

Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.

Readiness: Higher than 60% of peers; This listing 83 · peer median 81
Latency: Faster than 10% of peers; This listing 871 ms · peer median 326 ms

Where it loses the most points, and how to win them back

Verified identity −5 — Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
Auth declaration −5 — State how to authenticate (an auth scheme, or that none is needed).
Now: How to authenticate is not stated.
Protocol revision −4 — Support the current protocol revision.
Now: Speaks MCP 2025-06-18, 2 revision(s) behind 2026-07-28.

How many agent tools actually work · All statistics

Listed in

Directories this entry was found in.

agenstry since 2026-10-22 ↗

How to connect

MCP endpoint (streamable-http)

https://vedaksha.net/api/mcp

JSON-RPC initialize probe

curl -X POST https://vedaksha.net/api/mcp \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'

Homepage

https://vedaksha.net

Listed at (agenstry)

https://agenstry.com/mcp/arthiq-labs/vedaksha