# Vedara: Vedic astrology

> Vedic astrology: birth charts, dashas, compatibility, transits and personal timing

- name: me.vedara/vedara
- version: 2.7.0
- connection class: R0 (autonomous)
- trust: 83/100 flags: no-repository
- quality: 91/100 (strong)
- owner: not claimed
- descriptor: https://api.protogrid.dev/v1/servers/me.vedara%2Fvedara
- tools: https://api.protogrid.dev/v1/servers/me.vedara%2Fvedara/tools

**An agent can connect right now, no human step.** Remote endpoint, no authentication, reachable on the last probe.

## Connection (mcpServers)

```json
{
  "mcpServers": {
    "vedara": {
      "type": "http",
      "url": "https://mcp.vedara.me/mcp"
    }
  }
}
```


## Trust

- hygiene: 80
- liveness: 100
- freshness: 100
- provenance: 55
- drivers: +dns-namespace +website +reachable +uptime-100% +updated-14d-ago -no-repository
- Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed.

## Quality 91/100 (strong)

### protocol: 75 (weight 25)

- warn `protocol.modern`: newest supported version is 2025-11-25; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
- n/a `protocol.stateless`: only applies to 2026-07-28 servers
- pass `protocol.transport`: streamable HTTP
- n/a `protocol.list_ttl`: only applies to 2026-07-28 servers

### authorization: n/a (weight 15)

- n/a `auth.prm`, `auth.as_metadata`, `auth.cimd`: no remote uses OAuth
- n/a `auth.secret_in_url`: no templated URL

### tool hygiene: 100 (weight 30)

- pass `tools.descriptions`: every tool has a description
- pass `tools.description_length`: descriptions are concise
- pass `tools.schemas`: every tool has an object input schema
- pass `tools.annotations`: 14 of 14 tools declare readOnlyHint or destructiveHint
- pass `tools.directory_hints`: every tool declares readOnlyHint, destructiveHint, idempotentHint and openWorldHint
- pass `tools.token_cost`: about 5,135 tokens to load every tool
- pass `tools.api_dump`: tools are not a one-to-one API dump
- pass `tools.hidden_text`: no hidden text in tool names, descriptions, schemas or annotations

### stability: 100 (weight 15)

- pass `stability.changes`: no tool changes in 30 days
- pass `stability.rug_pull`: no tool changed its meaning under the same name
- pass `stability.new_links`: no tool change named a new site

### dependencies: n/a (weight 15)

- n/a `deps.known_vulns`, `deps.mcp_sdk_version`, `deps.resolvable`: no npm or PyPI package

- tools: 14, about 5,135 tokens to load them all
- tool set hash: 3038d5cb36c813108a3e70c401cff1fe
- badge: [![protogrid quality](https://protogrid.dev/badge/me.vedara/vedara.svg)](https://protogrid.dev/servers/me.vedara/vedara)
- Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed.

### Tool changes

_No tool definition changes recorded._

## Remotes

- https://mcp.vedara.me/mcp (streamable-http, auth none, reachable true, uptime30d 1)

## Packages

_none_

## Tools (14)

- `analyze_doshas`: Analyze Manglik (Mangal dosha), Kaal Sarpa, and Sade Sati indicators for supplied birth data. Returns structured calculations, not deterministic life outcomes. Use city, region and country for a place. If a place is not found, ask the user to clarify it before trying another tool with the same place. Use only verified latitude and longitude; never guess coordinates.
- `check_compatibility`: Calculate traditional 36-point Ashtakoot (Guna Milan, gun milan, Kundli matching) compatibility for two consenting people, with Moon, Lagna, chart positions, and dosha flags. Do not frame the score as a command to start or end a relationship. Use city, region and country for a place. If a place is not found, ask the user to clarify it before trying another tool with the same place. Use only verified latitude and longitude; never guess coordinates.
- `compute_chart`: Calculate a Lahiri sidereal natal chart (a Kundli, Kundali, or Janam Kundali, the Vedic horoscope chart) from local birth date, local birth time, and either a place name or coordinates. Returns planetary positions, Ascendant, houses (bhavas), house lords and graha drishti. Optional include sections: divisional_charts (D9 Navamsa and D10 Dasamsa), yogas (including Raja and Dhana yogas), planet_strength (classical Shadbala in rupas, BPHS). Use only after the user agrees to share birth details. Use city, region and country for a place. If a place is not found, ask the user to clarify it before trying another tool with the same place. Use only verified latitude and longitude; never guess coordinates.
- `find_auspicious_time`: Find personalized Muhurta (shubh muhurat) windows, the best date and time to start a named Vedara activity, over a maximum 32-day inclusive range. Dates use YYYY-MM-DD. Free with a connected Vedara account that has a completed birth profile. An empty new-start result may include empty_state with its classical delay explanation and next_good (local date, start/end times and score), searched up to 14 days ahead within the account's Timing horizon, or a fallback suggestion. Operates only within the connected user's bounded private Vedara account. Uses saved or explicitly supplied coordinates and Vedara calculations, without public geocoding, web search, external recipients, or public publishing. Authentication, audit events, and rate limits are private account operations.
- `get_dasha_timeline`: Calculate the current Vimshottari mahadasha and a bounded timeline of planetary periods from supplied birth data, the starting point for career and relationship timing questions. Includes current antardasha and pratyantardasha. Optional from_date/to_date (YYYY-MM-DD) return overlapping sub-periods with full boundaries in an end-exclusive range of at most 1096 days; from_date alone defaults to 90 days. Depth must be between 1 and 20. Use city, region and country for a place. If a place is not found, ask the user to clarify it before trying another tool with the same place. Use only verified latitude and longitude; never guess coordinates.
- `get_my_chart`: Return the connected user's saved sidereal birth chart (their Kundli) without exposing stored birth details or internal identifiers. Includes houses (bhavas), house lords and graha drishti. Optional include sections: divisional_charts (D9 Navamsa, D10 Dasamsa), yogas (Raja and Dhana yogas), planet_strength (classical Shadbala in rupas, BPHS). Free with a connected Vedara account that has a completed birth profile. Operates only within the connected user's bounded private Vedara account. Uses saved or explicitly supplied coordinates and Vedara calculations, without public geocoding, web search, external recipients, or public publishing. Authentication, audit events, and rate limits are private account operations.
- `get_my_timing`: Return the connected user's current Vimshottari period and present sidereal transit snapshot (gochar), including transits to natal houses from the Ascendant and Moon and current antardasha and pratyantardasha. Free with a connected Vedara account that has a completed birth profile. Operates only within the connected user's bounded private Vedara account. Uses saved or explicitly supplied coordinates and Vedara calculations, without public geocoding, web search, external recipients, or public publishing. Authentication, audit events, and rate limits are private account operations.
- `get_sky_now`: Return sidereal planetary signs and nakshatras (the current gochar, or transit sky) for a date and IANA timezone. Defaults to today's date in UTC.
- `get_transits_to_chart`: Return gochar transits at local noon for a date (YYYY-MM-DD) and IANA timezone, mapped to natal houses from the Ascendant and Moon, with graha drishti, retrograde flags and natal planets touched. Date defaults to today in UTC. Birth data accepts a place name or verified coordinates; unresolved places return an error.
- `list_timing_activities`: List every activity Vedara can search auspicious timing for, with its id, label, category and accepted aliases. Call this before find_auspicious_time and pass one of the returned ids as the activity.
- `save_my_birth_profile`: Save a complete birth date, birth time, and birth place to the connected user's Vedara account when no complete birth profile is already saved. Requires confirmed_profile_write to be true after confirming the exact details with the user. Replaces any partial birth details, clears cached calculations, and starts recalculation.
- `share_chart`: Calculate a Lahiri sidereal natal chart and publish it as a public Vedara page, returning a link the user can keep or send to anyone. The page shows the chart, an optional first name, birth date, and place, never the birth time or coordinates. Use only after the user explicitly asks for a sharable link and agrees the chart will be publicly viewable by anyone who has it.
- `today_for_me`: What should I know about today: return raw deterministic Panchanga (Panchang), caution windows including Rahu Kaal (Rahu Kalam), Tara and Chandra Bala, and current dasha facts for the connected user's day. Requires a completed saved Vedara birth profile; ChatGPT provides any interpretation. Operates only within the connected user's bounded private Vedara account. Uses saved or explicitly supplied coordinates and Vedara calculations, without public geocoding, web search, external recipients, or public publishing. Authentication, audit events, and rate limits are private account operations.
- `update_my_birth_profile`: Update the complete birth date, birth time, and birth place stored in the connected user's Vedara account. Requires confirmed_profile_write to be true after confirming the exact details with the user. Clears cached calculations and starts recalculation.