# Naksha Vedic Astrology (remote · mcp.naksha.social)

Vedic kundli, daily sky, kundli milan, sade sati and mangal dosha from birth details.

- Trust score: 78/100 (medium)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.naksha.social`: 78/100 (this document), [markdown](https://verifymcp.io/servers/social-naksha-vedic-astrology/mcp.md), [page](https://verifymcp.io/servers/social-naksha-vedic-astrology/mcp)

## Channel facts

- Endpoint: `https://mcp.naksha.social/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 784 tokens (~156/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 98/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 94% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Naksha Vedic Astrology MCP server?

Naksha Vedic Astrology is a hosted endpoint at https://mcp.naksha.social/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.

### Claude

```bash
claude mcp add --transport http social-naksha-vedic-astrology 'https://mcp.naksha.social/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "social-naksha-vedic-astrology": {
      "url": "https://mcp.naksha.social/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "social-naksha-vedic-astrology": {
      "type": "http",
      "url": "https://mcp.naksha.social/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.social-naksha-vedic-astrology]
url = "https://mcp.naksha.social/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "social-naksha-vedic-astrology": {
      "type": "remote",
      "url": "https://mcp.naksha.social/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add social-naksha-vedic-astrology --url 'https://mcp.naksha.social/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  social-naksha-vedic-astrology:
    url: "https://mcp.naksha.social/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "social-naksha-vedic-astrology": {
      "Transport": "http",
      "Url": "https://mcp.naksha.social/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add social-naksha-vedic-astrology -t streamable-http -u 'https://mcp.naksha.social/mcp'
```

### Other

```json
{
  "mcpServers": {
    "social-naksha-vedic-astrology": {
      "type": "http",
      "url": "https://mcp.naksha.social/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 78, 0)

- [functional] Server version: 0.1.0 → 0.1.1

### 2026-11-02 (score 78, 0)

- [security] Stability: 0.97 → pass

### 2026-11-01 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-26 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-21 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `naksha_chart` (~166 tokens)

Calculate a Naksha birth chart

Use this when the user asks for a kundli, janam kundli, Vedic birth chart, "kundli banao", rising sign/lagna, moon sign/rashi ("what is my rashi"), nakshatra or planetary placements, and gives birth date, time and city. Use city text only; Naksha looks the city up in memory and does not save it. Do not use for Western sun-sign horoscopes, when the user only wants a rashi from a name, or for medical, legal or financial decisions.

Input parameters:

- `date` (string, required): YYYY-MM-DD birth date
- `placeName` (string, required): Birth city text only; Naksha geocodes it in memory
- `time` (string): Local birth time HH:MM

### `naksha_daily` (~155 tokens)

Read today’s Naksha sky

Use this when the user asks what today or this week looks like astrologically for them, "aaj ka din kaisa rahega", current Vedic transits or gochar, or wants a daily reading from their birth details. Use city text only for the birth place; Naksha looks it up in memory and does not save it. Do not use for general panchang or rahu kaal with no birth details, and do not make deterministic claims about health, death or finance.

Input parameters:

- `date` (string, required): YYYY-MM-DD birth date
- `placeName` (string, required): Birth city text only; Naksha geocodes it in memory
- `time` (string): Local birth time HH:MM

### `naksha_compatibility` (~174 tokens)

Compare two Naksha charts

Use this when the user asks about kundli milan, kundli matching for marriage, guna milan / ashtakoota score out of 36, or Vedic compatibility between two people and both birth details are provided. Use city text only for each birth place; Naksha looks each city up in memory and does not save it. Do not use for name-only matching or Western synastry, and do not make deterministic claims about a relationship.

Input parameters:

- `mode` (string)
- `person1` (object, required): Birth date, local time, and city text. Naksha geocodes the city in memory; never send raw coordinates.
- `person2` (object, required): Birth date, local time, and city text. Naksha geocodes the city in memory; never send raw coordinates.

### `naksha_sade_sati` (~155 tokens)

Check Naksha sade sati

Use this when the user asks "is my sade sati running", "sade sati calculator", "shani dhaiya", or about Saturn's transit over their moon sign, and gives either their rashi (moon sign) or birth date, time and city. Reports the current phase only; no remedies or fear language. Do not use for general Saturn news or for Western astrology.

Input parameters:

- `date` (string): YYYY-MM-DD birth date
- `placeName` (string): Birth city text only
- `rashi` (string): Moon sign, e.g. Kumbha, Makar, Aquarius. Use this OR birth details.
- `time` (string): Local birth time HH:MM

### `naksha_mangal_dosha` (~113 tokens)

Check Naksha mangal dosha

Use this when the user asks about mangal dosha, "am I manglik", or manglik status for marriage matching, and gives birth date, time and city. Reports the Mars placement factually and states the rule used; no remedies. Do not use without birth details or as a verdict about a marriage.

Input parameters:

- `date` (string, required): YYYY-MM-DD birth date
- `placeName` (string, required): Birth city text only
- `time` (string): Local birth time HH:MM

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/social-naksha-vedic-astrology/mcp#diagnostics

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 76
- 2026-10-28: 76
- 2026-10-27: 75
- 2026-10-26: 75
- 2026-10-25: 74
- 2026-10-24: 74
- 2026-10-23: 74
- 2026-10-22: 73
- 2026-10-21: 73
- 2026-10-20: 72
- 2026-10-19: 72
- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 69
- 2026-10-13: 69
- 2026-10-12: 68
- 2026-10-10: 67
- 2026-10-09: 67
- 2026-10-06: 66
- 2026-10-04: 65
- 2026-10-03: 64

## Common questions

### What is the Naksha Vedic Astrology MCP server?

Naksha Vedic Astrology is an MCP server listed in the public MCP registry as social.naksha/vedic-astrology. Vedic kundli, daily sky, kundli milan, sade sati and mangal dosha from birth details. This page covers its hosted endpoint (https://mcp.naksha.social/mcp).

### Is the Naksha Vedic Astrology MCP server safe to use?

Naksha Vedic Astrology scores 78 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 Naksha Vedic Astrology MCP server expose?

Naksha Vedic Astrology exposes 5 tools: naksha_chart, naksha_daily, naksha_compatibility, naksha_sade_sati, naksha_mangal_dosha. Their descriptions and schemas cost roughly 763 tokens of context every time the server is loaded.

### Does the Naksha Vedic Astrology MCP server require authentication?

No. We connected to Naksha Vedic Astrology without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Naksha Vedic Astrology MCP server still maintained?

Naksha Vedic Astrology is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Naksha Vedic Astrology MCP server?

VerifyMCP ran 12 checks on Naksha Vedic Astrology, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Naksha Vedic Astrology: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.naksha.social/mcp
- Website: https://naksha.social/
- Changelog RSS feed: https://verifymcp.io/servers/social-naksha-vedic-astrology/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/social-naksha-vedic-astrology/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/social-naksha-vedic-astrology/mcp.json
- HTML version of this page: https://verifymcp.io/servers/social-naksha-vedic-astrology/mcp