Western zodiac sign from date of birth and sign compatibility scores. English and Hindi.
Maintain this server? Claim it
Call this server's tools from your browser. Nothing to install.
Requests go through mcptry because browsers can't call most MCP servers directly. Header values are sent to the server for that request only and are never stored or logged.
Tool list from our last check. Connect live to refresh it.
Score two signs 0-100 with the published rule: element base (same 80; fire-air 85; earth-water 85; fire-earth 45; fire-water 40; earth-air 50; air-water 55), modality same -5 / different +5, no modality adjustment for a sign with itself (same sign = 75), clamp and round; symmetric. Bands: 80+ strong, 65-79 good, 50-64 mixed, <50 challenging. Returns score, band, verdict (one line per band), elements, modalities, method_url '/guides/how-compatibility-is-scored', page_url. Case-insensitive; Hindi sign names accepted. Example input: {"sign_a":"Aries","sign_b":"Leo"}
First sign, English or Hindi
Second sign, English or Hindi
This tool isn't marked read-only, so it may change something on the server or in an account you connected.
Pick your client. Values in capitals, like YOUR_TOKEN, are yours to fill in.
claude mcp add --transport http findmyzodiac https://findmyzodiac.com/mcp
Score two signs 0-100 with the published rule: element base (same 80; fire-air 85; earth-water 85; fire-earth 45; fire-water 40; earth-air 50; air-water 55), modality same -5 / different +5, no modality adjustment for a sign with itself (same sign = 75), clamp and round; symmetric. Bands: 80+ strong, 65-79 good, 50-64 mixed, <50 challenging. Returns score, band, verdict (one line per band), elements, modalities, method_url '/guides/how-compatibility-is-scored', page_url. Case-insensitive; Hindi sign names accepted. Example input: {"sign_a":"Aries","sign_b":"Leo"}
| Argument | Type | Description |
|---|---|---|
| sign_a* | string | First sign, English or Hindi |
| sign_b* | string | Second sign, English or Hindi |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"sign_a",
"sign_b"
],
"properties": {
"sign_a": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "First sign, English or Hindi"
},
"sign_b": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "Second sign, English or Hindi"
}
}
}Western sun sign from a date of birth (year optional, ignored). Returns sign slug, name_en, name_hi, start, end, element, modality, ruler, is_cusp (first or last day), cusp_neighbour, convention 'standard calendar dates', url. Validation error for impossible dates like 02-30. Example input: {"month":7,"day":23,"lang":"en"}
| Argument | Type | Description |
|---|---|---|
| day* | integer | Day of birth, 1 to 31 |
| lang | string | Language of the sign name in url: en or hi |
| month* | integer | Month of birth, 1 to 12 |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"month",
"day"
],
"properties": {
"day": {
"type": "integer",
"maximum": 31,
"minimum": 1,
"description": "Day of birth, 1 to 31"
},
"lang": {
"enum": [
"en",
"hi"
],
"type": "string",
"default": "en",
"description": "Language of the sign name in url: en or hi"
},
"month": {
"type": "integer",
"maximum": 12,
"minimum": 1,
"description": "Month of birth, 1 to 12"
}
}
}We read every tool's name, description and inputs the way the model will, looking for instructions hidden from you. A clean result means no warning signs, not a guarantee. Scanned Oct 30, 2026.
No readOnlyHint / destructiveHint annotations, so clients can't tell a read from a write without asking.
Fix: Add annotations to each tool, e.g. { readOnlyHint: true } for tools that only read.