Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Naksha Vedic Astrology

REMOTE · MCP.NAKSHA.SOCIAL

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

+2 this week 78 Trust /100

Last scanned (3 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 5 Nov 2026.

Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability71
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 94% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Changelog

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.

  • 5 Nov 26 0
    • Server version: 0.1.0 → 0.1.1 functional
  • 2 Nov 26 0
    • Stability: 0.97 → pass security
  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 28 Oct 26 +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.

  • 26 Oct 26 +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.

  • 23 Oct 26 +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.

  • 21 Oct 26 +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.

Diagnostics

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 5 Nov 2026 · Probed https://mcp.naksha.social/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=naksha.social CN=WE1,O=Google Trust Services,C=US 3 Oct 2026 1 Jan 2027 ECDSA 256 ECDSA-SHA256 4a41315ec022bc6a13cc703a7b8da979
SANs: naksha.social, mcp.naksha.social, *.mcp.naksha.social
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.naksha.social. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
social. present 40816 8 Verified
naksha.social. 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://mcp.naksha.social/mcp Verified 200
http (plaintext) http://mcp.naksha.social/mcp Inconclusive 404
MCP tools · 5 exposed · ~763 tokens

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 →

Tool Tokens
naksha_chart ~166

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.

NameTypeReqDescription
datestringyesYYYY-MM-DD birth date
placeNamestringyesBirth city text only; Naksha geocodes it in memory
timestring–Local birth time HH:MM

No output schema declared.

No examples provided.

naksha_compatibility ~174

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.

NameTypeReqDescription
modestring––
person1objectyesBirth date, local time, and city text. Naksha geocodes the city in memory; never send raw coordinates.
person2objectyesBirth date, local time, and city text. Naksha geocodes the city in memory; never send raw coordinates.

No output schema declared.

No examples provided.

naksha_daily ~155

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.

NameTypeReqDescription
datestringyesYYYY-MM-DD birth date
placeNamestringyesBirth city text only; Naksha geocodes it in memory
timestring–Local birth time HH:MM

No output schema declared.

No examples provided.

naksha_mangal_dosha ~113

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.

NameTypeReqDescription
datestringyesYYYY-MM-DD birth date
placeNamestringyesBirth city text only
timestring–Local birth time HH:MM

No output schema declared.

No examples provided.

naksha_sade_sati ~155

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.

NameTypeReqDescription
datestring–YYYY-MM-DD birth date
placeNamestring–Birth city text only
rashistring–Moon sign, e.g. Kumbha, Makar, Aquarius. Use this OR birth details.
timestring–Local birth time HH:MM

No output schema declared.

No examples provided.

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.

remote · mcp.naksha.social

# add to Claude Code
claude mcp add --transport http social-naksha-vedic-astrology 'https://mcp.naksha.social/mcp'
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.