# io.github.novaventures-ai/marriage-astro (npm · marriage-astro-mcp)

Vedic Astrology MCP Server - birth charts, compatibility, and dosha analysis.

- Trust score: 64/100 (medium)
- Change this week: +22
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `marriage-astro-mcp`: 64/100 (this document), [markdown](https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp.md), [page](https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp)

## Channel facts

- Registry: `npm`
- Package: `marriage-astro-mcp`
- Version: `1.0.2`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-08-03.

- **Supply Chain Security**: 86/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 77 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 6709 tokens (~304/item across 22 items; 22 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add novaventures-ai-marriage-astro -- npx -y marriage-astro-mcp
```

### Codex

```bash
codex mcp add novaventures-ai-marriage-astro -- npx -y marriage-astro-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "novaventures-ai-marriage-astro": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "marriage-astro-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add novaventures-ai-marriage-astro --command npx --arg -y --arg marriage-astro-mcp
```

### Hermes

```yaml
mcp_servers:
  novaventures-ai-marriage-astro:
    command: "npx"
    args: ["-y", "marriage-astro-mcp"]
```

### Other

```json
{
  "mcpServers": {
    "novaventures-ai-marriage-astro": {
      "command": "npx",
      "args": [
        "-y",
        "marriage-astro-mcp"
      ]
    }
  }
}
```

## 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-08-02 (score 64, +47)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Stability: unverified → 0.20
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Schema quality: unverified → good
- [functional] Licence: MIT

### 2026-07-31 (score 17, −25)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 42, +18)

- [functional improvement] Tool coverage: unverified → 100

### 2026-07-28 (score 24, −18)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-27 (score 42)

First indexed and scored.

## MCP tools (22)

### `get_birth_chart` (~184 tokens)

Generate a Vedic birth chart (planets, houses, nakshatras, ascendant, yogas, dashas) for one person.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `calculate_compatibility` (~437 tokens)

Calculate Ashtakoot Milan 36-point compatibility score between two people, including all 8 parameters (Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, Nadi) and dosha flags.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `analyze_dosha` (~411 tokens)

Check Mangal dosha, Nadi dosha, Kaal Sarpa, and other yoga/dosha patterns for one or two people.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_full_compatibility_report` (~415 tokens)

Generate the complete compatibility report including synastry, navamsa, divisional charts, dasha analysis, and timing. Requires developer plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_marriage_timing` (~178 tokens)

Find auspicious marriage windows based on Vimshottari Dasha and transit confluence. Requires developer plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_synastry` (~400 tokens)

Cross-chart planetary aspect analysis and house overlays between two people. Requires developer plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_navamsa_matching` (~405 tokens)

D9 Navamsa chart compatibility — the marriage-specific divisional chart analysis. Requires developer plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_kp_analysis` (~181 tokens)

Krishnamurti Paddhati (KP) stellar astrology analysis with 249 sub-lords. Requires developer plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_jaimini_dasha` (~184 tokens)

Jaimini/Chara Dasha analysis including Darakaraka and Upapada Lagna for marriage timing. Requires developer plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_self_analysis` (~172 tokens)

Single-person marriage readiness analysis — personality, timing forecast, spouse profile. Requires developer plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_divorce_risk` (~416 tokens)

Assess divorce probability from 7th and 2nd house afflictions. Unique feature — no other Vedic API provides this. Requires premium plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_infidelity_risk` (~413 tokens)

Analyze infidelity indicators from 5th, 8th, and 12th house patterns, plus protective factors. Requires premium plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_sexual_compatibility` (~406 tokens)

Venus/Mars synastry + sexual temperament matching + mutual satisfaction analysis. Requires premium plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_sexual_health` (~180 tokens)

Individual sexual health analysis — libido, PME/ED/Frigidity risk indicators from birth chart. Requires premium plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_mental_health_analysis` (~176 tokens)

Analyze anxiety, depression, narcissism, and emotional stability markers from birth chart. Requires premium plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_psychological_profile` (~173 tokens)

Attachment style, emotional patterns, and personality profile from planetary positions. Requires premium plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_conflict_zones` (~404 tokens)

Identify conflict triggers, hot-button topics, and tension patterns between two people. Requires premium plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_vulnerability_windows` (~403 tokens)

Find timing windows when the relationship is at highest stress/breakdown risk. Requires premium plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_inlaw_analysis` (~405 tokens)

Analyze compatibility with partner's family from 4th and 8th house indicators. Requires premium plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_spouse_prediction` (~177 tokens)

Predict future spouse's appearance, nature, profession, and when/how you will meet them. Requires premium plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_modern_challenges` (~417 tokens)

Digital age relationship analysis — social media impact, long-distance patterns, modern planet (Uranus/Neptune/Pluto) influence. Requires premium plan.

Input parameters:

- `person_a_date` (string, required): Person A's date of birth in YYYY-MM-DD format
- `person_a_gender` (string): Person A's gender (male/female/other)
- `person_a_latitude` (number, required): Person A's birth place latitude (e.g. 19.076 for Mumbai)
- `person_a_location` (string): Person A's birth place name (e.g. 'Mumbai, India')
- `person_a_longitude` (number, required): Person A's birth place longitude (e.g. 72.877 for Mumbai)
- `person_a_name` (string): Person A's name
- `person_a_time` (string): Person A's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_a_timezone` (string): Person A's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)
- `person_b_date` (string): Person B's date of birth in YYYY-MM-DD format (omit for single-person analysis)
- `person_b_gender` (string): Person B's gender (male/female/other)
- `person_b_latitude` (number): Person B's birth place latitude (e.g. 19.076 for Mumbai)
- `person_b_location` (string): Person B's birth place name (e.g. 'Mumbai, India')
- `person_b_longitude` (number): Person B's birth place longitude (e.g. 72.877 for Mumbai)
- `person_b_name` (string): Person B's name
- `person_b_time` (string): Person B's time of birth in HH:MM format (24h, defaults to 12:00)
- `person_b_timezone` (string): Person B's timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

### `get_remedies` (~172 tokens)

Lal Kitab remedies and gemstone recommendations based on planetary afflictions. Requires premium plan.

Input parameters:

- `date` (string, required): Date of birth in YYYY-MM-DD format
- `gender` (string): Gender (male/female/other)
- `latitude` (number, required): Birth place latitude (e.g. 19.076 for Mumbai)
- `location` (string): Birth place name (e.g. 'Mumbai, India')
- `longitude` (number, required): Birth place longitude (e.g. 72.877 for Mumbai)
- `name` (string): Person's name
- `time` (string): Time of birth in HH:MM format (24h, defaults to 12:00)
- `timezone` (string): Timezone name (e.g. 'Asia/Kolkata', defaults to UTC)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp#diagnostics

## Score history

- 2026-08-03: 64
- 2026-08-02: 64
- 2026-08-01: 17
- 2026-07-31: 17
- 2026-07-30: 42
- 2026-07-28: 24
- 2026-07-27: 42

## Links

- npm package: https://www.npmjs.com/package/marriage-astro-mcp
- Socket report: https://socket.dev/npm/package/marriage-astro-mcp
- Repository: https://github.com/novaventures-ai/MarriageAstro
- Changelog RSS feed: https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp