Sahadeva
REMOTE · SAHADEVA.MAGICTEAMS.AI · SCANNED OCT 4
Vedic astrology MCP: panchanga, kundli matching, muhurta, dashas.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability50
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 6811 tokens (~109/item across 62 items; 54 tools + 8 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 Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 21% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 54 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 56 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Sahadeva MCP server?
Sahadeva is a hosted endpoint at https://sahadeva.magicteams.ai/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sahadeva.magicteams.ai
claude mcp add --transport http everyai-com-sahadeva 'https://sahadeva.magicteams.ai/mcp'
{
"mcpServers": {
"everyai-com-sahadeva": {
"url": "https://sahadeva.magicteams.ai/mcp"
}
}
} {
"servers": {
"everyai-com-sahadeva": {
"type": "http",
"url": "https://sahadeva.magicteams.ai/mcp"
}
}
} [mcp_servers.everyai-com-sahadeva] url = "https://sahadeva.magicteams.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"everyai-com-sahadeva": {
"type": "remote",
"url": "https://sahadeva.magicteams.ai/mcp",
"enabled": true
}
}
} openclaw mcp add everyai-com-sahadeva --url 'https://sahadeva.magicteams.ai/mcp' --transport streamable-http
mcp_servers:
everyai-com-sahadeva:
url: "https://sahadeva.magicteams.ai/mcp" {
"McpServers": {
"everyai-com-sahadeva": {
"Transport": "http",
"Url": "https://sahadeva.magicteams.ai/mcp"
}
}
} assistant mcp add everyai-com-sahadeva -t streamable-http -u 'https://sahadeva.magicteams.ai/mcp'
{
"mcpServers": {
"everyai-com-sahadeva": {
"type": "http",
"url": "https://sahadeva.magicteams.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 3 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- MCP protocol: Implements a current MCP spec version (2026-07-28). functional
- MCP protocol version: 2025-11-25 → 2026-07-28 functional
- 2 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 1 Oct 26 65
First indexed and scored.
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 8 Oct 2026 · Probed https://sahadeva.magicteams.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=magicteams.ai | CN=WE1,O=Google Trust Services,C=US | 1 Oct 2026 | 30 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 61f82da03a8a2cfc0eb08c389bf0a7f5 |
| SANs: magicteams.ai, sahadeva.magicteams.ai, *.sahadeva.magicteams.ai | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sahadeva.magicteams.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| magicteams.ai. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | default-src 'self'; base-uri 'none'; object-src 'none'; frame-ancestors 'none'; form-action 'self'; script-src 'self'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | no-referrer |
| permissions-policy | camera=(), microphone=(), payment=(), usb=(), geolocation=(self) |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sahadeva.magicteams.ai/mcp | Verified | 200 | |
| http (plaintext) | http://sahadeva.magicteams.ai/mcp | HTTPS enforced | 301 | https://sahadeva.magicteams.ai/mcp |
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 →
analyze_arudha_and_upapada Analyze Arudha and Upapada structures ~119
Analyze Arudha and Upapada structures
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_career_structure analyze career structure ~133
Evidence-linked analyze career structure without deterministic outcome claims.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topics | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_chart_topic Analyze one chart topic with an evidence ledger ~158
Runs the shared deterministic judgment pipeline for career, education, property, relationships, or spirituality. Returns supporting and opposing evidence, relevant Varga confirmation, current Dasha activation, uncertainty, matched reviewed citations, unresolved source keys, and explicit abstention boundaries. The web app uses the same judgment engine.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | – | – |
| birthTimeAccuracyMinutes | number | – | – |
| date | string | yes | – |
| language | string | – | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | – |
| time | string | yes | – |
| timezone | string | – | – |
| timezoneOffset | number | – | – |
| topic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_education_structure analyze education structure ~133
Evidence-linked analyze education structure without deterministic outcome claims.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topics | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_finance_structure analyze finance structure ~133
Evidence-linked analyze finance structure without deterministic outcome claims.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topics | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_house Analyze one natal house with support and opposition ~143
Returns the selected house, lord condition, occupants, functional lordship, relevant relationship edges, supporting and opposing evidence, unresolved source keys and sensitive-house restrictions.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| house | integer | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_lal_kitab Inspect Lal Kitab house structure and source sections ~162
Converts verified natal placements to Lal Kitab fixed houses and returns source locators for all nine planet-house sections. Prediction prose, annual-chart emulation and remedies remain withheld until atomic extraction, scan verification and lineage review.
| Name | Type | Req | Description |
|---|---|---|---|
| birthTimeAccuracyMinutes | number | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| Name | Type | Req | Description |
|---|---|---|---|
| blockedOutputs | array | yes | – |
| conjunctions | array | yes | – |
| controlledDisclosurePolicy | object | yes | – |
| conversion | object | yes | – |
| placements | array | yes | – |
| safety | object | yes | – |
| schemaVersion | – | yes | – |
| sourceCoverage | object | yes | – |
| tradition | object | yes | – |
No examples provided.
analyze_marriage_structure analyze marriage structure ~133
Evidence-linked analyze marriage structure without deterministic outcome claims.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topics | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_nakshatra_profile analyze nakshatra profile ~137
Evidence-linked analyze nakshatra profile without deterministic outcome claims.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topics | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_property_and_vehicle analyze property and vehicle ~134
Evidence-linked analyze property and vehicle without deterministic outcome claims.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topics | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_remedies Build a source-grounded chart remedy protocol ~207
Combines the topic evidence ledger, belief/cost/burden preferences, Iṣṭa and guiding Devatā calculation, Muhurta-as-remedy routing, optional charity and low-risk conduct. Every candidate exposes its source and publication gate. It withholds unreviewed gemstones, initiation-only mantras, fasting and costly rituals.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | – | – |
| birthTimeAccuracyMinutes | number | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| preferences | object | yes | – |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_spiritual_path analyze spiritual path ~133
Evidence-linked analyze spiritual path without deterministic outcome claims.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topics | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_transit_activation Analyze natal, Dasha and transit activation together ~149
Analyze natal, Dasha and transit activation together
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | yes | – |
| date | string | yes | – |
| endIso | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| startIso | string | yes | – |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_varga Analyze one divisional chart ~127
Analyze one divisional chart
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topic | string | – | – |
| varga | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
analyze_yogas Analyze Yoga formation, strength and opposition ~114
Analyze Yoga formation, strength and opposition
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
assess_prediction_readiness Assess prediction and tradition readiness ~45
Reports independent readiness gates for calculations, executable rules, worked examples, practitioner review and outcome calibration. It explicitly reports Lal Kitab as source-only until a dedicated reviewed engine exists.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| decision | object | yes | – |
| gates | array | yes | – |
| overallStatus | – | yes | – |
| recommendedMcpBuildOrder | array | yes | – |
| safety | object | yes | – |
| schemaVersion | – | yes | – |
| traditions | array | yes | – |
No examples provided.
audit_chart_calculation Audit chart calculation provenance and sensitivity ~151
Checks engine certification, timezone provenance, conventions and important sign/Nakshatra/Pada boundary distances before interpretation. It does not claim an external ephemeris recomputation.
| Name | Type | Req | Description |
|---|---|---|---|
| birthTimeAccuracyMinutes | number | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| Name | Type | Req | Description |
|---|---|---|---|
| boundaryAudit | array | yes | – |
| convention | object | yes | – |
| decision | object | yes | – |
| engine | object | yes | – |
| inputProvenance | object | yes | – |
| notice | string | yes | – |
| schemaVersion | – | yes | – |
| validation | object | yes | – |
No examples provided.
audit_prediction_claim Audit one prediction claim before narration ~113
Applies calculation, approved-rule, opposition, calibration and harm gates and returns publish, caution or abstain.
| Name | Type | Req | Description |
|---|---|---|---|
| approvedRules | array | – | – |
| calculationCertified | boolean | – | – |
| claim | string | yes | – |
| claimClass | string | – | – |
| empiricallyCalibrated | boolean | – | – |
| harmClass | string | – | – |
| nearBoundary | boolean | – | – |
| opposingEvidence | array | – | – |
| supportingEvidence | array | – | – |
| unresolvedSourceKeys | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
audit_reading_evidence Audit reading prose against calculated placements and safety rules ~125
Audit reading prose against calculated placements and safety rules
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| text | string | yes | – |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
build_claim_evidence_ledger build claim evidence ledger ~136
Evidence-linked build claim evidence ledger without deterministic outcome claims.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topics | array | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
calculate_ashtakavarga Calculate Bhinnashtakavarga and Sarvashtakavarga ~122
Calculate Bhinnashtakavarga and Sarvashtakavarga
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
calculate_compatibility Calculate Ashtakoota, Porutham and Kuja compatibility ~84
Resolves both birth places, calculates both charts, and returns separate auditable North Indian 36-point Ashtakoota and South Indian ten-Porutham breakdowns plus Mangal/Kuja Dosha evidence. Traditional research preview; never a relationship verdict.
| Name | Type | Req | Description |
|---|---|---|---|
| bride | object | yes | – |
| groom | object | yes | – |
| language | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| ashtakoota | object | yes | – |
| kujaDosha | object | yes | – |
| porutham | object | yes | – |
| safety | object | yes | – |
| schemaVersion | – | yes | – |
| sourceCoverage | object | yes | – |
| subjects | object | yes | – |
No examples provided.
calculate_dasha_system Calculate a declared Dasha system ~130
Calculate a declared Dasha system
| Name | Type | Req | Description |
|---|---|---|---|
| asOfIso | string | yes | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| system | string | yes | – |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
calculate_devata_profile Calculate Iṣṭa and guiding Devatā candidates ~191
Calculates Iṣṭa, Dharma, Pālana, Guru and Kula Devatā anchors from an explicit lineage preset: occupants, Rashi Drishti, then sign lord with visible tie-breaks. Unsupported lineages are withheld rather than silently mixed. It never prescribes initiation-only mantra or claims one uniquely correct deity.
| Name | Type | Req | Description |
|---|---|---|---|
| birthTimeAccuracyMinutes | number | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| lineage | string | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
calculate_doshas Calculate evidence-first Dosha patterns ~160
Calculates Mangal/Kuja, Kaal Sarpa enclosure, Kemadruma, and conservative Pitru-related structural candidates with raw/effective severity and explicit cancellation or mitigation evidence.
| Name | Type | Req | Description |
|---|---|---|---|
| birthTimeAccuracyMinutes | number | – | – |
| date | string | yes | – |
| language | string | – | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| Name | Type | Req | Description |
|---|---|---|---|
| patterns | array | yes | – |
| rulebook | object | yes | – |
| safety | object | yes | – |
| schemaVersion | – | yes | – |
| subject | object | yes | – |
| summary | object | yes | – |
No examples provided.
calculate_gochara_from_known_place Calculate gochara from a verified place ~76
Resolves a verified catalogue place and its IANA timezone before calculating sidereal transits, avoiding manual coordinate and offset entry.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| language | string | – | – |
| natalLagnaSign | integer | yes | – |
| place | string | yes | – |
| time | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| engine | object | yes | – |
| instantJulianDay | number | yes | – |
| natalLagnaSign | integer | yes | – |
| placements | array | yes | – |
| resolvedPlace | object | yes | – |
No examples provided.
calculate_prashna Ask a Prashna question ~133
Casts a server-time horary chart, checks chart fitness, and returns an auditable structural judgment plus outcome-confirmation hook.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | yes | – |
| language | string | – | – |
| latitude | number | – | – |
| longitude | number | – | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| question | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
calculate_strength_profile Calculate a separated planetary strength profile ~113
Calculate a separated planetary strength profile
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
compare_conventions Compare chart conventions without silent mixing ~137
Compares Lahiri with selected alternative ayanamsa projections for one topic, identifies changed Lagna, topic lord, karaka, sign, house and Nakshatra anchors, and marks when a Lahiri judgment must not be reused. Alternative full derived charts remain explicitly unvalidated.
| Name | Type | Req | Description |
|---|---|---|---|
| conventions | array | – | – |
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | – |
| time | string | yes | – |
| timezone | string | – | – |
| timezoneOffset | number | – | – |
| topic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_reading_versions Explain why two reading versions changed ~37
Compares engine, ruleset, input and conclusion status changes.
| Name | Type | Req | Description |
|---|---|---|---|
| first | object | yes | – |
| second | object | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_traditions Compare traditions without blending them ~37
Compares explicitly supplied tradition ledgers while preserving separate methods, evidence, contradictions and readiness states.
| Name | Type | Req | Description |
|---|---|---|---|
| ledgers | array | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
consult_jyotishya Ask Sahadeva — master Jyotisha consultation ~329
PRIMARY TOOL FOR EVERY NORMAL USER QUESTION AND FIRST READING. Always runs a complete person-first screen covering identity, education, employment, business, money, love, marriage, health routines, family/property, children and spirituality, plus strengths, Doshas/cancellations and safe practical support. It then gives extra Varga and timing depth to the exact question, checks contradictions and reports coverage. Use specialist tools only when this result requests additional inputs or the user asks for technical matrices. Deterministic: it never invokes another AI model.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | – | – |
| birthTimeAccuracyMinutes | number | – | – |
| date | string | yes | – |
| detail | string | – | – |
| focus | string | – | – |
| language | string | – | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | – |
| profileRef | string | – | Stable profile reference returned by the first consultation. Pass it on later questions together with the same birth details. |
| question | string | – | – |
| readingMode | string | – | Use auto normally: without profileRef it creates the full first-reading dossier; with profileRef it returns a focused follow-up. |
| remedyPreferences | object | – | Optional explicit consent and burden preferences. Without these, personalized traditional remedies remain withheld. |
| time | string | yes | – |
| timezone | string | – | – |
| timezoneOffset | number | – | – |
| traditions | array | – | Traditions to compare as separate ledgers. They are interconnected by topic but never blended. |
Structured output declared, but exposes no named fields.
No examples provided.
explain_chart_sources Explain the source and review status behind a chart topic ~33
Returns book-section locators and rule-review status without treating discovered prose as executable doctrine.
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
explore_lal_kitab_sources Explore complete Lal Kitab source coverage ~38
Returns all source families, locators, coverage counts, lexical risk signals and graduated disclosure policy without republishing source body text.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | object | yes | – |
| families | array | yes | – |
| notice | string | yes | – |
| policy | object | yes | – |
| schemaVersion | – | yes | – |
| source | object | yes | – |
No examples provided.
find_marriage_windows Find structural marriage-planning windows ~114
Finds overlaps between Jupiter transiting the natal seventh sign and Venus or seventh-lord Vimshottari periods. Returns planning windows, never a guaranteed marriage prediction.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | – |
| startDate | string | yes | – |
| time | string | yes | – |
| timezone | string | – | – |
| timezoneOffset | number | – | – |
| years | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| natal | object | yes | – |
| range | object | yes | – |
| safety | object | yes | – |
| schemaVersion | – | yes | – |
| subject | object | yes | – |
| windows | array | yes | – |
No examples provided.
find_muhurta Find ranked Muhurta windows ~171
Ranks candidate windows over a bounded date range using activity Panchanga fitness, prohibited-period avoidance, optional Tara/Chandra Bala, instant Lagna structure, and activity-karaka condition. Returns every pass/fail reason and draft source key.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | yes | – |
| endDate | string | yes | – |
| latitude | number | – | – |
| limit | integer | – | – |
| longitude | number | – | – |
| natal | object | – | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| startDate | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | yes | – |
| rulebook | object | yes | – |
| safety | object | yes | – |
| schemaVersion | – | yes | – |
| windows | array | yes | – |
No examples provided.
find_muhurta_with_natal_fit Find Muhurta windows fitted to a natal chart ~153
Ranks a maximum seven-day range using Panchanga, prohibited intervals, Tara Bala and Chandra Bala. Medical procedures are unsupported.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | yes | – |
| endDate | string | yes | – |
| latitude | number | – | – |
| limit | integer | – | – |
| longitude | number | – | – |
| natal | object | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| startDate | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
Structured output declared, but exposes no named fields.
No examples provided.
fuse_timing Fuse promise, Dasha, transit, Ashtakavarga and Varga timing ~153
Applies natal promise as a hard gate and returns uncalibrated, auditable timing windows with learnable factor weights.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| endIso | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| startIso | string | yes | – |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
generate_full_life_report Generate a complete evidence-linked life report ~185
Builds a normal-person South Indian astrology report covering identity, mind, family, communication, home, learning, routines, relationships, change, beliefs, career, networks, rest, measured strengths, Vargas, structural Yogas, current Dasha and upcoming Antardashas. Interpretations remain qualified and evidence-linked.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | – | ISO date or instant for the current-timing section; defaults to now |
| birthTimeAccuracyMinutes | number | – | – |
| date | string | yes | – |
| focus | string | – | – |
| horizonYears | integer | – | – |
| language | string | – | – |
| latitude | number | yes | – |
| longitude | number | yes | – |
| name | string | yes | – |
| place | string | yes | – |
| time | string | yes | – |
| timezone | string | – | – |
| timezoneOffset | number | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| anchors | object | yes | – |
| ashtakavarga | object | yes | – |
| aspects | object | yes | – |
| currentTiming | object | yes | – |
| divisionalChartAnchors | object | yes | – |
| measuredStrengths | array | yes | – |
| placements | array | yes | – |
| plainLanguageReading | object | yes | – |
| safety | object | yes | – |
| schemaVersion | – | yes | – |
| sourceCoverage | object | yes | – |
| subject | object | yes | – |
| uncertainty | object | yes | – |
No examples provided.
generate_report_pdf Generate a hosted shareable PDF report ~104
Generates the full reading context as a server-side PDF and returns a hosted URL valid for 30 days.
| Name | Type | Req | Description |
|---|---|---|---|
| asOfDate | string | – | – |
| date | string | yes | – |
| horizonYears | number | – | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | – |
| time | string | yes | – |
| timezone | string | – | – |
| timezoneOffset | number | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| contentType | – | yes | – |
| expiresAt | string | yes | – |
| id | string | yes | – |
| safety | object | yes | – |
| url | string | yes | – |
No examples provided.
get_depth_analysis Get strength, Varga and additional-Dasha depth ~147
Returns Vimsopaka and Ishta/Kashta evidence, topic-specific cross-Varga synthesis, special Lagnas, expanded Yoga candidates and additional-Dasha status.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | – |
| latitude | number | – | – |
| longitude | number | – | – |
| name | string | yes | – |
| place | string | – | Catalogue query or display label when explicit coordinates are supplied |
| time | string | yes | – |
| timezone | string | – | Required IANA timezone when explicit coordinates are supplied, for example Asia/Kolkata |
| timezoneOffset | number | – | Optional fallback offset; derived from timezone and the requested local date when omitted |
| topic | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Sahadeva MCP server?
Sahadeva is an MCP server listed in the public MCP registry as io.github.everyai-com/sahadeva. Vedic astrology MCP: panchanga, kundli matching, muhurta, dashas. This page covers its hosted endpoint (https://sahadeva.magicteams.ai/mcp).
Is the Sahadeva MCP server safe to use?
Sahadeva scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Sahadeva MCP server expose?
Sahadeva exposes 54 tools: search_locations, calculate_compatibility, get_panchanga, find_muhurta, calculate_doshas, and 49 more. Their descriptions and schemas cost roughly 6,689 tokens of context every time the server is loaded.
Does the Sahadeva MCP server require authentication?
No. We connected to Sahadeva without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sahadeva MCP server still maintained?
Sahadeva is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.