Is the Entradox Ai Jyotish Bot MCP server down?

mcp-registry/io.github.entradox/ai-jyotish-bot · v1.0.0

healthy
Last checked 2026-10-19 13:55 UTC · handshake 98ms

As of 2026-10-19 13:55 UTC, the Entradox Ai Jyotish Bot MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 35 minutes.

uptime (30d checks)
99.5%
checks observed
3,302
outages (90d)
4
tools
8

Vedic astrology for AI agents: chart facts, panchang windows, and Guna Milan compatibility.

Install Entradox Ai Jyotish Bot MCP server

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http entradox-ai-jyotish-bot-mcp-server https://jyotish-mcp-production.up.railway.app/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "entradox-ai-jyotish-bot-mcp-server": {
      "type": "http",
      "url": "https://jyotish-mcp-production.up.railway.app/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: C (76/100)

C (76/100): 0 error(s), 1 warning(s) across 8 tool(s); ~2,254 tokens of tool definitions.
Scores higher than 14% of 15,348 MCP servers Glimind has audited.
Its tool list costs an agent ~2,254 tokens per session — lighter than 55% of servers.
74 → 76 since 2026-10-17
no tool-poisoning patterns
Schemas100
Descriptions46
Safety hints30
Token cost100
Client compatibility100
Protocol100
Reliability100
Stability36

What to fix (3)

10 parameter(s) across 5 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: ask_jyotish, get_dasha, get_doshas, get_forecast, get_varga

7 of 8 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: ask_jyotish, get_chart_facts, get_dasha, get_doshas, get_forecast and 2 more

In the last 30 days: 0 tool(s) removed and 16 schema change(s).

Add new tools or optional parameters instead of renaming or removing; deprecate first (say so in the description) and remove later. Agents cache tool contracts. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 5 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.entradox%2Fai-jyotish-bot/fixes

get_chart_facts 1 change 
{
  "name": "get_chart_facts",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "dob",
      "tob",
      "lat",
      "lng",
      "tz"
    ],
    "properties": {
      "tz": {
        "type": [
          "number",
          "string"
        ],
        "description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
      },
      "dob": {
        "type": "string",
        "description": "Birth date, YYYY-MM-DD."
      },
      "lat": {
        "type": "number",
        "description": "Birth latitude, -90 to 90."
      },
      "lng": {
        "type": "number",
        "description": "Birth longitude, -180 to 180."
      },
      "tob": {
        "type": "string",
        "description": "Birth time, HH:MM (24h)."
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_dasha 1 change 
{
  "name": "get_dasha",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "birth_data"
    ],
    "properties": {
      "birth_data": {
        "type": "object",
        "required": [
          "dob",
          "tob",
          "lat",
          "lng",
          "tz"
        ],
        "properties": {
          "tz": {
            "type": [
              "number",
              "string"
            ],
            "description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
          },
          "dob": {
            "type": "string",
            "description": "Birth date, YYYY-MM-DD."
          },
          "lat": {
            "type": "number",
            "description": "Birth latitude, -90 to 90."
          },
          "lng": {
            "type": "number",
            "description": "Birth longitude, -180 to 180."
          },
          "tob": {
            "type": "string",
            "description": "Birth time, HH:MM (24h)."
          }
        }
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_doshas 1 change 
{
  "name": "get_doshas",
  "description": "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.",
  "inputSchema": {
    "type": "object",
    "required": [
      "birth_data"
    ],
    "properties": {
      "lang": {
        "enum": [
          "en",
          "hi"
        ],
        "type": "string"
      },
      "birth_data": {
        "type": "object",
        "required": [
          "dob",
          "tob",
          "lat",
          "lng",
          "tz"
        ],
        "properties": {
          "tz": {
            "type": [
              "number",
              "string"
            ],
            "description": "UTC offset (e.g. 5.5) or IANA zone name (e.g. Asia/Kolkata)."
          },
          "dob": {
            "type": "string",
            "description": "Birth date, YYYY-MM-DD."
          },
          "lat": {
            "type": "number",
            "description": "Birth latitude, -90 to 90."
          },
          "lng": {
            "type": "number",
            "description": "Birth longitude, -180 to 180."
          },
          "tob": {
            "type": "string",
            "description": "Birth time, HH:MM (24h)."
          }
        }
      }
    }
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/io.github.entradox/ai-jyotish-bot"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/io.github.entradox/ai-jyotish-bot"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

Markdown 
[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.entradox%2Fai-jyotish-bot.svg)](https://glimind.com/server/mcp-registry%2Fio.github.entradox%2Fai-jyotish-bot?ref=badge)
HTML 
<a href="https://glimind.com/server/mcp-registry%2Fio.github.entradox%2Fai-jyotish-bot?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.entradox%2Fai-jyotish-bot.svg" alt="MCP agent-readiness"></a>
reStructuredText 
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.entradox%2Fai-jyotish-bot.svg
   :target: https://glimind.com/server/mcp-registry%2Fio.github.entradox%2Fai-jyotish-bot?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f801abd2d9aaa1ce…, first seen 2026-10-17, included at leaf 5606 of 27,033. Version history · verify what your client received.

Tools (8)

Compare: most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Entradox Ai Jyotish Bot MCP server down right now?

As of 2026-10-19 13:55 UTC, the Entradox Ai Jyotish Bot MCP server is up with a Glimind reliability score of 78/100 (grade B). Over the last 30 days it answered 99.5% of Glimind's liveness checks. It had 4 outages in 90 days, with a median recovery of 35 minutes.

How many tools does Entradox Ai Jyotish Bot MCP server provide?

Entradox Ai Jyotish Bot MCP server advertises 8 tools, including ask_jyotish, get_chart_facts, get_dasha, get_doshas, get_forecast.

How do I install Entradox Ai Jyotish Bot MCP server?

Point your MCP client at this streamable-http endpoint: https://jyotish-mcp-production.up.railway.app/mcp

Is the Entradox Ai Jyotish Bot MCP server safe to connect to an AI agent?

Glimind scanned all 8 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Entradox Ai Jyotish Bot MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve