mcp-registry/io.github.amarpathak/birthstar · v1.30.0
As of 2026-10-17 14:14 UTC, the Amarpathak Birthstar MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 73.2 hours.
30 Vedic Jyotish tools: natal charts, dashas, yogas, nakshatras. Swiss Ephemeris.
Claude Code
claude mcp add --transport http amarpathak-birthstar-mcp-server https://mcp.birthstar.ai/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"amarpathak-birthstar-mcp-server": {
"type": "http",
"url": "https://mcp.birthstar.ai/mcp"
}
}
}
Third-party server, listed as discovered. Review its source before installing.
30 of 30 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.
69 parameter(s) across 27 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.
1 tool(s) look like they change state (create/send/delete/pay…) but declare no destructiveHint.
Set annotations {"readOnlyHint": false, "destructiveHint": true|false, "idempotentHint": …}. Clients use these to ask the user before a side effect and to auto-approve safe reads.
Handshake + tools/list takes ~1,816 ms.
Serve tools/list from memory, keep the process warm, and host close to your users. Every new agent session pays this before its first call.
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably.
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 27 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fio.github.amarpathak%2Fbirthstar/fixes
{
"name": "calculate_birth_star",
"description": "Compute just a person's Vedic birth star (nakshatra) and core anchors.\n\n A one-shot shortcut: use this when the birth star is the whole question. If\n you expect follow-up questions about the same person's chart, prefer\n create_chart, which caches the full chart behind a reusable handle.\n\n Args:\n dob: Date of birth, YYYY-MM-DD (proleptic Gregorian).\n tob: Time of birth, HH:MM or HH:MM:SS, 24-hour.\n tz: IANA timezone name (e.g. \"Asia/Kolkata\") or fixed offset \"+05",
"inputSchema": {
"type": "object",
"title": "calculate_birth_starArguments",
"required": [
"dob",
"tob",
"tz",
"lat",
"lon"
],
"properties": {
"tz": {
"type": "string",
"title": "Tz"
},
"dob": {
"type": "string",
"title": "Dob"
},
"lat": {
"type": "number",
"title": "Lat"
},
"lon": {
"type": "number",
"title": "Lon"
},
"tob": {
"type": "string",
"title": "Tob"
},
"ayanamsha": {
"type": "string",
"title": "Ayanamsha",
"default": "lahiri"
}
}
},
"annotations": {
"readOnlyHint": true
}
}{
"name": "create_chart",
"description": "Compute a full Vedic natal chart and cache it, returning a short handle.\n\n Call this FIRST. It returns a `chart_id` plus a small summary. Pass that\n chart_id to the other tools (get_grahas, get_houses, get_current_dasha,\n get_panchanga, get_yogas) to read specific parts of the chart without\n recomputing it.\n\n Args:\n dob: Date of birth, YYYY-MM-DD (proleptic Gregorian).\n tob: Time of birth, HH:MM or HH:MM:SS, 24-hour, local to `tz`.\n tz: IANA timezone name (e.",
"inputSchema": {
"type": "object",
"title": "create_chartArguments",
"required": [
"dob",
"tob",
"tz",
"lat",
"lon"
],
"properties": {
"tz": {
"type": "string",
"title": "Tz"
},
"dob": {
"type": "string",
"title": "Dob"
},
"lat": {
"type": "number",
"title": "Lat"
},
"lon": {
"type": "number",
"title": "Lon"
},
"tob": {
"type": "string",
"title": "Tob"
},
"ayanamsha": {
"type": "string",
"title": "Ayanamsha",
"default": "lahiri"
},
"node_type": {
"type": "string",
"title": "Node Type",
"default": "true"
},
"house_system": {
"type": "string",
"title": "House System",
"default": "whole_sign"
},
"transit_date": {
"anyOf": [
{
"type": "string"
},
{
"type": "null"
}
],
"title": "Transit Date",
"default": null
}
}
},
"annotations": {
"readOnlyHint": false,
"destructiveHint": false,
"idempotentHint": false
}
}{
"name": "describe_chart",
"description": "Get metadata and an inventory of what a cached chart contains.\n\n Useful for orienting before drilling in: returns the birth data and config\n it was computed with, the top-level sections available in the document, and\n how many fields the engine honestly marked as deferred or uncomputable.\n ",
"inputSchema": {
"type": "object",
"title": "describe_chartArguments",
"required": [
"chart_id"
],
"properties": {
"chart_id": {
"type": "string",
"title": "Chart Id"
}
}
},
"annotations": {
"readOnlyHint": true
}
}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.amarpathak/birthstar"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/io.github.amarpathak/birthstar"}) over MCP.
rectify_birth_time ~343 tokensget_timeline ~331 tokenscreate_chart ~326 tokenscalculate_birth_star ~263 tokensget_dasha_periods ~250 tokensStatic 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:
[](https://glimind.com/server/mcp-registry%2Fio.github.amarpathak%2Fbirthstar?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Fio.github.amarpathak%2Fbirthstar?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.amarpathak%2Fbirthstar.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fio.github.amarpathak%2Fbirthstar.svg :target: https://glimind.com/server/mcp-registry%2Fio.github.amarpathak%2Fbirthstar?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:cf2ee0dc83511eb1…, first seen 2026-10-17, included at leaf 1485 of 17,709. Version history · verify what your client received.
Compare: most reliable knowledge servers · most reliable data servers · most reliable other servers · most reliable ml servers · most reliable devops servers
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.
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"
}
}
}
As of 2026-10-17 14:14 UTC, the Amarpathak Birthstar MCP server is up with a Glimind reliability score of 82/100 (grade B). Over the last 30 days it answered 99.7% of Glimind's liveness checks. It had 2 outages in 90 days, with a median recovery of 73.2 hours.
Amarpathak Birthstar MCP server advertises 30 tools, including calculate_birth_star, create_chart, describe_chart, get_account_status, get_ashtakavarga.
Point your MCP client at this streamable-http endpoint: https://mcp.birthstar.ai/mcp
Glimind scanned all 30 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.
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.