Lo Shu grid numerology for India: life path, Chaldean name number, compatibility.
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.
Takes two birth dates (dobA, dobB, YYYY-MM-DD) and returns a 0 to 100 harmony score, a label and the reasons from life path and mulank. Example input: {"dobA":"1990-05-14","dobB":"1992-11-03"}
First person's birth date, YYYY-MM-DD
Second person's birth date, YYYY-MM-DD
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 getsolulu https://getsolulu.com/mcp
Takes two birth dates (dobA, dobB, YYYY-MM-DD) and returns a 0 to 100 harmony score, a label and the reasons from life path and mulank. Example input: {"dobA":"1990-05-14","dobB":"1992-11-03"}
| Argument | Type | Description |
|---|---|---|
| dobA* | string | First person's birth date, YYYY-MM-DD |
| dobB* | string | Second person's birth date, YYYY-MM-DD |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"dobA",
"dobB"
],
"properties": {
"dobA": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "First person's birth date, YYYY-MM-DD"
},
"dobB": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Second person's birth date, YYYY-MM-DD"
}
}
}Takes a birth date (dob, YYYY-MM-DD) and returns the life path number (masters 11, 22, 33 kept) with its trail, plus mulank and bhagyank. Example input: {"dob":"1990-05-14"}
| Argument | Type | Description |
|---|---|---|
| dob* | string | Birth date as YYYY-MM-DD, between 1900 and 2100 |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"dob"
],
"properties": {
"dob": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Birth date as YYYY-MM-DD, between 1900 and 2100"
}
}
}Takes a birth date (dob, YYYY-MM-DD) and returns the filled 3x3 Lo Shu grid with present, missing and repeated numbers, completed planes, the arithmetic trail and a short reading. Example input: {"dob":"1990-05-14"}
| Argument | Type | Description |
|---|---|---|
| dob* | string | Birth date as YYYY-MM-DD, between 1900 and 2100 |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"dob"
],
"properties": {
"dob": {
"type": "string",
"pattern": "^\\d{4}-\\d{2}-\\d{2}$",
"description": "Birth date as YYYY-MM-DD, between 1900 and 2100"
}
}
}Takes a name in Latin letters (name) and returns its Chaldean destiny number, compound number and the per-letter trail. Example input: {"name":"Chloé"}
| Argument | Type | Description |
|---|---|---|
| name* | string | Name in Latin letters, up to 100 characters; accents are folded (Chloé becomes CHLOE) |
{
"type": "object",
"$schema": "https://json-schema.org/draft/2020-12/schema",
"required": [
"name"
],
"properties": {
"name": {
"type": "string",
"maxLength": 100,
"minLength": 1,
"description": "Name in Latin letters, up to 100 characters; accents are folded (Chloé becomes CHLOE)"
}
}
}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.