io.github.novaventures-ai/marriage-astro

NPM · MARRIAGE-ASTRO-MCP · SCANNED AUG 3

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

Available components

+22 this week 64 64 Trust /100

Trust breakdown (6 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 →

Supply Chain Security86

No malware found by supply-chain analysis.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
No install/post-install scripts declared.Pass
Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. View diagnostics → Partial

Provenance & Transparency45

Source repository is publicly reachable at the declared URL. View diagnostics → Pass
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 77 days ago).Pass
Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail

Schema Quality & AI Usability56

AI-judged instruction clarity (good).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 Management23

Stability observed for 7 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

Capabilities100

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

Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · marriage-astro-mcp

Claude Codex opencode OpenClaw Hermes Other

# add to Claude Code

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

# add to Codex CLI

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
    }
  }
}

# add to OpenClaw

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

# ~/.hermes/config.yaml

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

// mcp.json

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

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.

2 Aug 26 +47
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- Malware scan: unverified → pass ▲ security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Stability: unverified → 0.20 ▲ functional
- Maintenance: unverified → pass ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: MIT functional
31 Jul 26 −25
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
30 Jul 26 +18
- Tool coverage: unverified → 100 ▲ functional
28 Jul 26 −18
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
27 Jul 26 42

First indexed and scored.

Show 4 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 3 Aug 2026 · Analysed npm/[email protected]

Provenance none

Ecosystem: npm · Outcome: none

Dependencies 94 packages

94 packages in the resolved dependency tree · 94 deprecated · 29 stale.

The dependency tree was only partially resolved, so these counts may be incomplete.

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.

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.

On this page

Handy links

Scoring key

80+ high trust
60–79 medium
below 60 low

How we score

Score history · last 30 days

27 Jul 3 Aug