Jyotish — Vedic astrology for AI agents
REMOTE · JYOTISH-MCP-PRODUCTION.UP.RAILWAY.APP · SCANNED OCT 12
Vedic astrology for AI agents: chart facts, panchang windows, and Guna Milan compatibility.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 7 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1046 tokens (~130/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
- Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
- Structured output schemas are declared (13% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
- Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
How do I install the Jyotish — Vedic astrology for AI agents MCP server?
Jyotish — Vedic astrology for AI agents is a hosted endpoint at https://jyotish-mcp-production.up.railway.app/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · jyotish-mcp-production.up.railway.app
claude mcp add --transport http entradox-ai-jyotish-bot 'https://jyotish-mcp-production.up.railway.app/mcp'
{
"mcpServers": {
"entradox-ai-jyotish-bot": {
"url": "https://jyotish-mcp-production.up.railway.app/mcp"
}
}
} {
"servers": {
"entradox-ai-jyotish-bot": {
"type": "http",
"url": "https://jyotish-mcp-production.up.railway.app/mcp"
}
}
} [mcp_servers.entradox-ai-jyotish-bot] url = "https://jyotish-mcp-production.up.railway.app/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"entradox-ai-jyotish-bot": {
"type": "remote",
"url": "https://jyotish-mcp-production.up.railway.app/mcp",
"enabled": true
}
}
} openclaw mcp add entradox-ai-jyotish-bot --url 'https://jyotish-mcp-production.up.railway.app/mcp' --transport streamable-http
mcp_servers:
entradox-ai-jyotish-bot:
url: "https://jyotish-mcp-production.up.railway.app/mcp" {
"McpServers": {
"entradox-ai-jyotish-bot": {
"Transport": "http",
"Url": "https://jyotish-mcp-production.up.railway.app/mcp"
}
}
} assistant mcp add entradox-ai-jyotish-bot -t streamable-http -u 'https://jyotish-mcp-production.up.railway.app/mcp'
{
"mcpServers": {
"entradox-ai-jyotish-bot": {
"type": "http",
"url": "https://jyotish-mcp-production.up.railway.app/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 10 Oct 26 +3
No change was recorded against any check on this day. Stability & Change Management went from 40 to 57. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Oct 26 0
- Tool “get_panchang” rewrote its description, which is the text the model reads security
- Tool coverage: 86% → 60% ▼ functional
- Schema quality: 148 → 130 ▲ functional
- Tool “get_panchang” now declares an output schema ▲ functional
- First check of Tool coverage: 13 functional
- New tool “get_dasha” functional
- New tool “get_doshas” functional
- New tool “get_forecast” functional
- New tool “get_varga” functional
- Tool “get_panchang” changed its title: Hindu panchang for a place and date cosmetic
- 2 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 12 Oct 2026 · Probed https://jyotish-mcp-production.up.railway.app/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.up.railway.app | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 618edc56941aa1165ddb080bf9f799eb7c1 |
| SANs: *.up.railway.app, up.railway.app | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of jyotish-mcp-production.up.railway.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| railway.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://jyotish-mcp-production.up.railway.app/mcp | Verified | 200 | |
| http (plaintext) | http://jyotish-mcp-production.up.railway.app/mcp | HTTPS enforced | 301 | https://jyotish-mcp-production.up.railway.app/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ask_jyotish ~98
Grounded synthesis answer to a question, computed from the birth chart through the same accuracy-gated path as the retail chat endpoint (chart-anchor check and rewrite retry inside run_reading). The response envelope carries citation_status and accuracy-gate notes. lang: en or hi (default en).
| Name | Type | Req | Description |
|---|---|---|---|
| birth_data | object | yes | – |
| lang | string | – | – |
| question | string | yes | The question to answer from the chart. |
No output schema declared.
No examples provided.
get_chart_facts ~184
Deterministic Vedic chart facts for birth data: lagna, Moon sign/nakshatra, current dasha, planets in houses, house lords, dignities, combustions, D9/D10 ascendants, Sade Sati standing, yogas with classical-text citations, dasha timeline. Pure computation, no LLM. Same output as POST /api/b2b/chart-facts.
| Name | Type | Req | Description |
|---|---|---|---|
| dob | string | yes | Birth date, YYYY-MM-DD. |
| lat | number | yes | Birth latitude, -90 to 90. |
| lng | number | yes | Birth longitude, -180 to 180. |
| tob | string | yes | Birth time, HH:MM (24h). |
| tz | number|string | yes | UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata). |
No output schema declared.
No examples provided.
get_dasha ~74
Vimshottari dasha standing and full timeline for birth data: current maha / antar / pratyantar dasha plus every maha-dasha period with start and end dates. Deterministic, no LLM. Same compute path as POST /api/b2b/dasha.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_data | object | yes | – |
No output schema declared.
No examples provided.
get_doshas ~93
Dosha screen for birth data: Manglik standing under both conventions (Moon and Lagna), Kaal Sarp detection, Sade Sati phase, and extra classical yogas. Deterministic, no LLM. lang: en or hi (default en). Same compute path as POST /api/b2b/doshas.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_data | object | yes | – |
| lang | string | – | – |
No output schema declared.
No examples provided.
get_forecast ~152
Structured personalized forecast for birth data — per-area tones, day calendar, ingresses, dasha standing. period: daily (optional date), weekly, monthly (optional year+month), or yearly (optional year). Deterministic engine output, no LLM narration. lang: en or hi (default en). Same compute path as POST /api/b2b/forecast.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_data | object | yes | – |
| date | string | – | YYYY-MM-DD (daily period only). |
| lang | string | – | – |
| month | integer | – | Target month 1-12 (monthly period only). |
| period | string | yes | – |
| year | integer | – | Target year (monthly/yearly periods). |
No output schema declared.
No examples provided.
get_panchang Hindu panchang for a place and date ~189
Use when a user asks about the Hindu calendar day for a location — tithi, paksha, nakshatra, yoga, karana, vara and its lord, sunrise and sunset, plus Rahu Kaal, Yamaganda, Gulika Kaal and the Choghadiya day/night windows. Needs only a place and a date, so it works without anyone's birth details. Deterministic computation, no LLM. Same compute path as GET /api/panchang.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | – | YYYY-MM-DD (default: local today at the location). |
| lat | number | yes | Birth latitude, -90 to 90. |
| lng | number | yes | Birth longitude, -180 to 180. |
| tz | number|string | yes | UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata). |
| Name | Type | Req | Description |
|---|---|---|---|
| choghadiya | object | – | – |
| inauspicious_windows | object | – | – |
| karana | string|null | – | – |
| nakshatra | string|null | – | – |
| on_date | string | – | – |
| paksha | string|null | – | – |
| sunrise | string|null | – | – |
| sunset | string|null | – | – |
| tithi | string|null | – | – |
| tithi_num | integer | – | – |
| vara | string | – | – |
| vara_lord | string | – | – |
| yoga | string|null | – | – |
No examples provided.
get_varga ~95
Divisional chart (varga) placements for birth data — all sixteen supported divisions d1,d2,d3,d4,d7,d9,d10,d12,d16,d20,d24,d27,d30,d40,d45,d60. Deterministic, no LLM. Same compute path as POST /api/b2b/varga.
| Name | Type | Req | Description |
|---|---|---|---|
| birth_data | object | yes | – |
| varga | string | yes | – |
No output schema declared.
No examples provided.
guna_milan ~161
Vedic compatibility (Guna Milan / Ashtakoota) between two people, 36 points across eight kootas: varna, vashya, tara, yoni, graha_maitri, gana, bhakoot, nadi. Moon nakshatra and rashi for each native are computed from their birth data through the same chart engine as get_chart_facts — do not pass nakshatra/rashi yourself. Deterministic, no LLM. Each koota carries its score, its maximum, and a plain-language reason, so the result is auditable rather than a bare number.
| Name | Type | Req | Description |
|---|---|---|---|
| person_a | object | yes | First native's birth data. |
| person_b | object | yes | Second native's birth data. |
No output schema declared.
No examples provided.
What is the Jyotish — Vedic astrology for AI agents MCP server?
Jyotish — Vedic astrology for AI agents is an MCP server listed in the public MCP registry as io.github.entradox/ai-jyotish-bot. Vedic astrology for AI agents: chart facts, panchang windows, and Guna Milan compatibility. This page covers its hosted endpoint (https://jyotish-mcp-production.up.railway.app/mcp).
Is the Jyotish — Vedic astrology for AI agents MCP server safe to use?
Jyotish — Vedic astrology for AI agents scores 67 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Jyotish — Vedic astrology for AI agents MCP server expose?
Jyotish — Vedic astrology for AI agents exposes 8 tools: get_chart_facts, ask_jyotish, guna_milan, get_panchang, get_varga, and 3 more. Their descriptions and schemas cost roughly 1,046 tokens of context every time the server is loaded.
Does the Jyotish — Vedic astrology for AI agents MCP server require authentication?
No. We connected to Jyotish — Vedic astrology for AI agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Jyotish — Vedic astrology for AI agents MCP server still maintained?
Jyotish — Vedic astrology for AI agents is still listed as active in the MCP registry. We last reached this channel on 12 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.