How do I install the io.github.novaventures-ai/marriage-astro MCP server?

io.github.novaventures-ai/marriage-astro runs locally as an npm package, launched with npx -y marriage-astro-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

io.github.novaventures-ai/marriage-astro

NPM · MARRIAGE-ASTRO-MCP · SCANNED SEP 25

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

Available components

npm · marriage-astro-mcp 74

−5 this week 74 74 Trust /100

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security98

No malware found by supply-chain analysis.Pass
No known CVEs affecting this package version or its production dependencies.Pass
No install/post-install scripts declared.Pass
31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial

Provenance & Transparency19

Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
Clear OSI-approved license (MIT).Pass
Actively maintained (last published 130 days ago).Pass
Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified

Schema Quality & AI Usability61

AI-judged instruction clarity (excellent).Pass
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. See how to fix → Fail
Usage-examples check failed: none of the tools include examples. See how to fix → Fail

Stability & Change Management83

Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial

Tool Coverage100

100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
100% of tool parameters carry a description.Pass

Tool Safety100

No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
We read all 22 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass

Capabilities100

Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass

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.

25 Sept 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
24 Sept 26 −3
- Stability: pass → 0.80 functional
23 Sept 26 −5
- Source repository: pass → fail ▼ security
- Stability: 0.97 → pass security
- Security disclosure: fail → unverified ▼ functional
22 Sept 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.
19 Sept 26 +1

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
17 Sept 26 −2
- Stability: pass → 0.80 functional
16 Sept 26 0
- Stability: 0.97 → pass security
15 Sept 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.

Show 5 earlier entries Hide earlier entries

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 25 Sept 2026 · Analysed npm/marriage-astro-mcp@1.0.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result	No attestation
Ecosystem	npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages

Packages resolved	95
Stale	31
Tree resolution	Complete

Background: SBOMs and build attestations, explained →

MCP tools · 22 exposed · ~6,709 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

analyze_dosha ~411

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

calculate_compatibility ~437

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 Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_birth_chart ~184

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_conflict_zones ~404

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_divorce_risk ~416

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_full_compatibility_report ~415

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_infidelity_risk ~413

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_inlaw_analysis ~405

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_jaimini_dasha ~184

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_kp_analysis ~181

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_marriage_timing ~178

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_mental_health_analysis ~176

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_modern_challenges ~417

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_navamsa_matching ~405

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_psychological_profile ~173

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_remedies ~172

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_self_analysis ~172

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_sexual_compatibility ~406

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_sexual_health ~180

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_spouse_prediction ~177

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

Input Output Examples

Name	Type	Req	Description
date	string	yes	Date of birth in YYYY-MM-DD format
gender	string	–	Gender (male/female/other)
latitude	number	yes	Birth place latitude (e.g. 19.076 for Mumbai)
location	string	–	Birth place name (e.g. 'Mumbai, India')
longitude	number	yes	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)

No output schema declared.

No examples provided.

get_synastry ~400

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

get_vulnerability_windows ~403

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

Input Output Examples

Name	Type	Req	Description
person_a_date	string	yes	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	yes	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	yes	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)

No output schema declared.

No examples provided.

Common questions

What is the io.github.novaventures-ai/marriage-astro MCP server?

io.github.novaventures-ai/marriage-astro is an MCP server listed in the public MCP registry as io.github.novaventures-ai/marriage-astro. Vedic Astrology MCP Server - birth charts, compatibility, and dosha analysis. This page covers its npm package (marriage-astro-mcp).

Is the io.github.novaventures-ai/marriage-astro MCP server safe to use?

io.github.novaventures-ai/marriage-astro scores 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 2026. It declares no install or post-install scripts. 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 io.github.novaventures-ai/marriage-astro MCP server expose?

io.github.novaventures-ai/marriage-astro exposes 22 tools: get_birth_chart, calculate_compatibility, analyze_dosha, get_full_compatibility_report, get_marriage_timing, and 17 more. Their descriptions and schemas cost roughly 6,709 tokens of context every time the server is loaded.

Is the io.github.novaventures-ai/marriage-astro MCP server still maintained?

io.github.novaventures-ai/marriage-astro is still listed as active in the MCP registry. We last reached this channel on 25 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.novaventures-ai/marriage-astro MCP server under?

io.github.novaventures-ai/marriage-astro declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Badge

Put this score in your README. The image is served from a stable URL, updates when the score does, and links back to the evidence on this page. It shows nothing that is not already published here.

Score Verified Plain

The two-cell badge: our name, and this channel's current score out of 100.

Markdown

 [![VerifyMCP trust score for io.github.novaventures-ai/marriage-astro](https://verifymcp.io/badge/novaventures-ai-marriage-astro/marriage-astro-mcp.svg)](https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp)

HTML

 <a href="https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp"><img src="https://verifymcp.io/badge/novaventures-ai-marriage-astro/marriage-astro-mcp.svg" alt="VerifyMCP trust score for io.github.novaventures-ai/marriage-astro" height="20"></a>

A single cell stating that the server is listed here. Carries no number.

Markdown

 [![VerifyMCP trust score for io.github.novaventures-ai/marriage-astro](https://verifymcp.io/badge/novaventures-ai-marriage-astro/marriage-astro-mcp.svg?variant=verified)](https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp)

HTML

 <a href="https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp"><img src="https://verifymcp.io/badge/novaventures-ai-marriage-astro/marriage-astro-mcp.svg?variant=verified" alt="VerifyMCP trust score for io.github.novaventures-ai/marriage-astro" height="20"></a>

The score alone, tier-coloured, for a badge row that is already crowded.

Markdown

 [![VerifyMCP trust score for io.github.novaventures-ai/marriage-astro](https://verifymcp.io/badge/novaventures-ai-marriage-astro/marriage-astro-mcp.svg?variant=plain)](https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp)

HTML

 <a href="https://verifymcp.io/servers/novaventures-ai-marriage-astro/marriage-astro-mcp"><img src="https://verifymcp.io/badge/novaventures-ai-marriage-astro/marriage-astro-mcp.svg?variant=plain" alt="VerifyMCP trust score for io.github.novaventures-ai/marriage-astro" height="20"></a>

Score history · last 30 days

27 Aug 25 Sept

Trust score by day, last 30 days
Day	Score
27 Aug	79
28 Aug	80
29 Aug	80
30 Aug	80
31 Aug	81
1 Sept	81
2 Sept	78
3 Sept	79
4 Sept	79
5 Sept	80
6 Sept	80
7 Sept	80
8 Sept	81
9 Sept	81
10 Sept	79
11 Sept	79
12 Sept	80
13 Sept	80
14 Sept	80
15 Sept	81
16 Sept	81
17 Sept	79
18 Sept	79
19 Sept	80
20 Sept	80
21 Sept	80
22 Sept	81
23 Sept	76
24 Sept	73
25 Sept	74