Vedic kundli, panchang, dashas, nakshatras and KP charts for AI agents, one API key.
AI & Agentsv1.0.0streamable-httproxyapi.com
| Criterion | Points | Observed |
|---|---|---|
| reachability | 25 / 25 | HTTP 200, initialize accepted in 180ms |
| protocol | 15 / 15 | valid JSON-RPC initialize result, protocolVersion 2025-06-18, serverInfo roxy-vedic-astrology@2.0.0 |
| tooling | 35 / 35 | tools/list OK: 43 tools e.g. "post_vedic_astrology_birth_chart"; 43/43 described, 43/43 fully-typed schemas, median description 453 chars |
| latency | 10 / 10 | initialize round-trip 180ms |
| provenance | 12 / 15 | description present; no repository URL; version 1.0.0; namespace com.roxyapi matches endpoint/repo |
Score 97/100 · latency 180ms · 43 tools · auth: open
Claude Code:
claude mcp add --transport http vedic-astrology https://roxyapi.com/mcp/vedic-astrology
Generic MCP client config:
{ "mcpServers": { "vedic-astrology": { "type": "http", "url": "https://roxyapi.com/mcp/vedic-astrology" } } }
MCP Queen is a graded index, not a middleman — your agent connects directly to the server above. Check the grade and evidence first; that's the point.
Share this server: permalink https://mcpqueen.com/s/com.roxyapi/vedic-astrology · referral link https://mcpqueen.com/go/com.roxyapi/vedic-astrology (counts as “routed via the queen”).
Live badge, re-probed continuously — put it in your README:
[](https://mcpqueen.com/s/com.roxyapi/vedic-astrology)
Think the grade is wrong? Fix the finding the evidence shows, then the next probe cycle picks it up automatically (full cycle ≈ 3 days) — or open a dispute via the MCP endpoint.
Email alerts when the grade changes or the endpoint stops answering. Double-opt-in, one-click unwatch, free while in beta.
| When (UTC) | Grade | Score | Latency |
|---|---|---|---|
| 2026-07-13 06:30 | A | 97 | 180ms |