_ registry / mcp http-sse · checked 1h ago

AstroLogics

https://www.astrologics.in

Registry code: 5fe3db0a9f2e21a3

api record

Vedic astrology calculations: birth chart, dasha, panchang, muhurat, matching, doshas, horoscope.

from a public catalogue that lists it, not from the operator

endpoint
https://www.astrologics.in/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is AstroLogics live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is AstroLogics free to use?
Partly — some of its tools are open, others need a key or payment.
What tools does AstroLogics have?
23 tools: get_panchang, check_marriage_compatibility, get_numerology, list_my_charts, search_birth_place, get_birth_chart, get_vimshottari_dasha, get_planet_positions, ….
Is AstroLogics safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
275ms

last good check

priced tools
0

of 23 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 23 tools
2 open1 auth-required 20 never probed 3 of 23 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_festival_calendar open 1h ago

    List Hindu festival, vrat, Ekadashi, Sankranti and Shraddha dates in a date range (covers the 2026 calendar; dates as observed in India).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "to": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "End date, YYYY-MM-DD. Defaults to 60 days after the start."
    },
    "from": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Start date, YYYY-MM-DD. Defaults to today."
    }
  }
}
    arguments 16 lines
  • get_horoscope open 1h ago

    Get the horoscope for one zodiac sign or for all twelve, for today, the current week, the current month or the year. Returns the reading plus numeric aspect scores, lucky factors and current transits.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "sign": {
      "type": "string",
      "description": "One of aries, taurus, gemini, cancer, leo, virgo, libra, scorpio, sagittarius, capricorn, aquarius, pisces. Omit to get all twelve."
    },
    "period": {
      "enum": [
        "2026",
        "today",
        "weekly",
        "monthly"
      ],
      "type": "string",
      "description": "Defaults to today."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    }
  }
}
    arguments 28 lines
  • get_antardasha auth-required 1h ago

    Get the running Vimshottari mahadasha, antardasha (bhukti) and pratyantardasha with their dates, the next ones, and the antardasha sequence. Uses a saved chart from the signed-in user's AstroLogics account or given birth details, with the chart features of the user's plan.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD (when not using a saved chart)."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM (when not using a saved chart)."
    },
    "chart": {
      "type": "string",
      "maxLength": 100,
      "description": "A saved chart's id or name from list_my_charts. Or give the birth details below instead."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees (when not using a saved chart)."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees (when not using a saved chart)."
    }
  }
}
    arguments 41 lines
  • get_panchang unknown never probed

    Get the Vedic panchang for a date and place: tithi, nakshatra, yoga, karana, vara and Rahu Kaal.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Date, YYYY-MM-DD."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees."
    }
  }
}
    arguments 36 lines
  • check_marriage_compatibility unknown never probed

    Calculate the 36-guna Ashtakoota marriage compatibility score between two people from their birth details. The calculation is Moon-based, so birth time is optional; supplying it is more accurate because the Moon moves about 13 degrees a day.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "boy",
    "girl"
  ],
  "properties": {
    "boy": {
      "type": "object",
      "required": [
        "date",
        "latitude",
        "longitude"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        "time": {
          "type": "string",
          "pattern": "^\\d{2}:\\d{2}$"
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180
        },
        "place_name": {
          "type": "string",
          "maxLength": 120
        }
      },
      "description": "First person: birth date, optional time, latitude and longitude."
    },
    "girl": {
      "type": "object",
      "required": [
        "date",
        "latitude",
        "longitude"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$"
        },
        "time": {
          "type": "string",
          "pattern": "^\\d{2}:\\d{2}$"
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180
        },
        "place_name": {
          "type": "string",
          "maxLength": 120
        }
      },
      "description": "Second person: birth date, optional time, latitude and longitude."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    }
  }
}
    arguments 84 lines
  • get_numerology unknown never probed

    Calculate numerology core numbers from a full name and birth date: life path, birth, destiny (expression), soul urge, personality and personal year numbers, with meanings, lucky numbers, colours and days, and the ruling planet.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name",
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "name": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Full name as the person uses it."
    }
  }
}
    arguments 21 lines
  • list_my_charts unknown never probed

    List the birth charts saved in the signed-in user's AstroLogics account (name, relationship, birth date, time and place). Requires the user to have connected their AstroLogics account.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 100,
      "description": "Optional: only charts whose name contains this text."
    }
  }
}
    arguments 11 lines
  • search_birth_place unknown never probed

    Resolve a place name to coordinates for use as the birth place of a Vedic chart. Call this first when the user gives a place name rather than latitude and longitude.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "q"
  ],
  "properties": {
    "q": {
      "type": "string",
      "maxLength": 120,
      "minLength": 2,
      "description": "Place name, for example \"Noida\" or \"Darbhanga, Bihar\"."
    },
    "country": {
      "type": "string",
      "maxLength": 40,
      "description": "Optional country preference such as \"in\". Matching widens automatically when that country has no result."
    }
  }
}
    arguments 20 lines
  • get_birth_chart unknown never probed

    Calculate a sidereal (Lahiri) Vedic birth chart: the ascendant, the nine grahas with sign, degree, nakshatra and house, and the navamsa, dashamsa and hora ascendants. Requires birth date and coordinates. Birth time improves accuracy and defaults to 12:00 when unknown.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time at the birth place, HH:MM. Defaults to 12:00 if unknown."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees."
    },
    "place_name": {
      "type": "string",
      "maxLength": 120,
      "description": "Optional place name as the user gave it, used only to prefill the details link."
    }
  }
}
    arguments 46 lines
  • get_vimshottari_dasha unknown never probed

    Calculate the Vimshottari mahadasha periods from a birth chart: the nine periods with start and end dates, which one is running now and how many years remain in it. Requires birth date, birth time and coordinates.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "time",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time at the birth place, HH:MM. Required: the dasha balance depends on the Moon's exact position."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees."
    }
  }
}
    arguments 42 lines
  • get_planet_positions unknown never probed

    Get the sidereal (Lahiri) positions of the nine grahas and the ascendant for any date, time and place: sign, degree, nakshatra, pada and retrograde state. Defaults to now in New Delhi when date, time or place are omitted.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Date, YYYY-MM-DD. Defaults to today (IST)."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local time, HH:MM. Defaults to now."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees. Omit with longitude for New Delhi."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees."
    }
  }
}
    arguments 36 lines
  • get_transit_calendar unknown never probed

    List upcoming planetary transit events (sign changes, retrograde and direct stations, eclipses) from today for up to 180 days, plus the grahas retrograde right now.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 180,
      "minimum": 1,
      "description": "How many days ahead to cover. Defaults to 90."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    }
  }
}
    arguments 20 lines
  • find_muhurat unknown never probed

    Find the most auspicious upcoming dates for an activity using panchang rules (tithi, nakshatra, yoga, weekday, Panchak, Tara Bala). Activities: marriage, griha-pravesh, business, vehicle, travel, education, namkaran, property.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "activity",
    "latitude",
    "longitude"
  ],
  "properties": {
    "top": {
      "type": "integer",
      "maximum": 20,
      "minimum": 1,
      "description": "How many dates to return. Defaults to 10."
    },
    "days": {
      "type": "integer",
      "maximum": 366,
      "minimum": 1,
      "description": "How many days to scan. Defaults to 90."
    },
    "from": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "First date to consider, YYYY-MM-DD. Defaults to today."
    },
    "activity": {
      "enum": [
        "marriage",
        "griha-pravesh",
        "business",
        "vehicle",
        "travel",
        "education",
        "namkaran",
        "property"
      ],
      "type": "string",
      "description": "The activity to find dates for."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude of the place, decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude of the place, decimal degrees."
    }
  }
}
    arguments 62 lines
  • get_choghadiya unknown never probed

    Get the 16 day and night choghadiya periods for a date and place with their quality (auspicious or not), start and end times in local time, the period running now and the next favourable one.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Date, YYYY-MM-DD."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Longitude in decimal degrees."
    }
  }
}
    arguments 36 lines
  • check_sade_sati unknown never probed

    Check whether Shani Sade Sati or Dhaiya (Saturn's transit over the natal Moon) is running for a person, which phase, its dates, and the full list of Sade Sati and Dhaiya windows across about 30 years around now. Based on the Moon sign; birth time is needed only when the Moon changed sign on the birth date.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM. Optional."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees."
    }
  }
}
    arguments 41 lines
  • check_manglik_dosha unknown never probed

    Check Manglik (Mangal) dosha in a birth chart: whether Mars occupies a dosha house from the ascendant, Moon or Venus, its strength, and any classical cancellation. Requires birth date, birth time and coordinates (the ascendant depends on the time).

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "time",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM. Required."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees."
    }
  }
}
    arguments 42 lines
  • check_kaal_sarp_dosha unknown never probed

    Check Kaal Sarp dosha in a birth chart: whether all seven planets lie on one side of the Rahu-Ketu axis, and if so which of the twelve named types it is. Birth time is optional.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM. Optional."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees."
    }
  }
}
    arguments 41 lines
  • check_pitra_dosha unknown never probed

    Check a birth chart for the commonly cited Pitra dosha combinations: the Sun with Rahu or Ketu, Rahu or Ketu in the 9th house, the Sun with Saturn in the 9th house, and the 9th lord with Rahu or Ketu. Lists each combination found. Birth time is needed for the house-based checks.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM. Without it only the Sun-Rahu and Sun-Ketu checks are made."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees."
    }
  }
}
    arguments 41 lines
  • check_gand_mool unknown never probed

    Check whether a person was born with the Moon in a Gand Mool nakshatra (Ashwini, Ashlesha, Magha, Jyeshtha, Mula or Revati), with the pada and whether it falls on the sign junction (gandanta). Birth time is optional; without it the result says if the Moon changed nakshatra that day.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM. Optional."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees."
    }
  }
}
    arguments 41 lines
  • get_my_chart unknown never probed

    Get a saved birth chart from the signed-in user's AstroLogics account by its id or name (for example "Mom"), with the chart features included in the plan the user already has: planets, houses, the Vimshottari dasha running today (currentDasha) and, where included, antardasha, dasha periods, yogas and divisional charts.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "chart"
  ],
  "properties": {
    "chart": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "The chart id from list_my_charts, or its name."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    }
  }
}
    arguments 23 lines
  • save_chart unknown never probed

    Save a new birth chart to the signed-in user's AstroLogics account so it appears in their saved charts on the website and app. Only call this when the user asks to save a chart. Saving the same birth details again returns the existing chart.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "name",
    "date",
    "latitude",
    "longitude"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "name": {
      "type": "string",
      "maxLength": 100,
      "minLength": 1,
      "description": "Name for the chart, for example \"Priya\" or \"Mom\"."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM. Defaults to 12:00 if unknown."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees."
    },
    "place_name": {
      "type": "string",
      "maxLength": 120,
      "description": "Birth place name as the user gave it."
    },
    "relationship": {
      "type": "string",
      "maxLength": 50,
      "description": "Optional relationship to the user, for example \"self\", \"spouse\", \"mother\"."
    }
  }
}
    arguments 50 lines
  • get_yogas unknown never probed

    List the classical yogas present in a birth chart (for example Gaja Kesari, Raja and Dhana yogas) with the planets that form each, its strength and its traditional meaning. Uses a saved chart from the signed-in user's AstroLogics account or given birth details, with the chart features of the user's plan.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD (when not using a saved chart)."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM (when not using a saved chart)."
    },
    "chart": {
      "type": "string",
      "maxLength": 100,
      "description": "A saved chart's id or name from list_my_charts. Or give the birth details below instead."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees (when not using a saved chart)."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees (when not using a saved chart)."
    }
  }
}
    arguments 41 lines
  • get_divisional_chart unknown never probed

    Get a divisional (varga) chart: D2 Hora, D9 Navamsa (marriage and dharma), D10 Dashamsa (career) or D12 Dwadashamsa (parents), with each graha's sign and house and the chart's interpretation where available. Uses a saved chart from the signed-in user's AstroLogics account or given birth details, with the chart features of the user's plan.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "division"
  ],
  "properties": {
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD (when not using a saved chart)."
    },
    "time": {
      "type": "string",
      "pattern": "^\\d{2}:\\d{2}$",
      "description": "Local birth time, HH:MM (when not using a saved chart)."
    },
    "chart": {
      "type": "string",
      "maxLength": 100,
      "description": "A saved chart's id or name from list_my_charts. Or give the birth details below instead."
    },
    "division": {
      "enum": [
        "D2",
        "D9",
        "D10",
        "D12"
      ],
      "type": "string",
      "description": "Which divisional chart."
    },
    "language": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Set to \"hi\" to add Hindi (Devanagari) names next to the English ones, for answering in Hindi."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees (when not using a saved chart)."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees (when not using a saved chart)."
    }
  }
}
    arguments 54 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 5fe3db0a9f2e21a3.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/5fe3db0a9f2e21a3/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/5fe3db0a9f2e21a3/badge.svg)](https://brick.blue/agent/5fe3db0a9f2e21a3?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.