_ registry / mcp streamable-http · checked 27m ago

astrocalc

https://astrocalc.in

Registry code: 4bd44bf91eaa4d84

api record

AstroCalc computes Vedic (Jyotish) charts with the Swiss Ephemeris, sidereal zodiac and Lahiri ayanamsa. Use these tools instead of estimating planetary positions, guna scores or dasha dates. If a place name is ambiguous, call search_place first. Birth time may be unknown; then say that the Lagna is approximate. Each result has a caveat and a link to the free full report on astrocalc.in: share the link with the user. Present doshas and low scores calmly, mention cancellations, and do not frame results as certain predictions or as medical, legal or financial advice.

endpoint
https://astrocalc.in/mcp
protocol
streamable-http ·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 astrocalc live?
Yes — it answered the hub's last check (checked 27m ago). It answered 100% of checks over the last 30 days.
Is astrocalc free to use?
Yes — the hub reached it with no key and no payment.
What tools does astrocalc have?
6 tools: kundli_milan, search_place, learn_answer, explain_dasha, yoga_rarity, free_kundli.
Is astrocalc 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
534ms

last good check

priced tools
0

of 6 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

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 6 tools
6 never probed 0 of 6 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.

  • kundli_milan unknown never probed

    Match two people's Vedic birth charts for marriage: Ashtakoota Guna Milan score out of 36 plus the Manglik (Mangal dosha) check for both, computed by AstroCalc's engine. Use it for "kundli milan", "guna milan", "horoscope matching", "how many gunas match", "is this match Manglik", Nadi or Bhakoot dosha questions. Do not estimate a guna score yourself; call this. Returns the total and band, all 8 kootas (Varna, Vashya, Tara, Yoni, Graha Maitri, Gana, Bhakoot, Nadi) with points and a plain-language meaning, which doshas are cancelled by classical exceptions, each person's Manglik status and the pair verdict, a caveat, and a link to the full free report. Each person needs a birth date and place; time is optional. Details are used in memory only and not stored. Present the result calmly: a score is one traditional input, not a decision about a relationship.

    mcp-tool

    {
  "type": "object",
  "required": [
    "person_a",
    "person_b"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the text fields: 'en' (English, default) or 'hi' (Hindi)."
    },
    "person_a": {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Birth latitude in decimal degrees (north positive). Give together with lon."
        },
        "lon": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Birth longitude in decimal degrees (east positive). Give together with lat."
        },
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date of birth, YYYY-MM-DD (Gregorian calendar)."
        },
        "time": {
          "type": "string",
          "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$",
          "description": "Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."
        },
        "place": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given."
        },
        "gender": {
          "enum": [
            "male",
            "female"
          ],
          "type": "string",
          "description": "Optional. Classical milan reads the boy's chart against the girl's; with a male/female pair the order is set by gender, otherwise person_a is read as the boy."
        }
      },
      "description": "Birth details of the first person.",
      "additionalProperties": false
    },
    "person_b": {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "lat": {
          "type": "number",
          "maximum": 90,
          "minimum": -90,
          "description": "Birth latitude in decimal degrees (north positive). Give together with lon."
        },
        "lon": {
          "type": "number",
          "maximum": 180,
          "minimum": -180,
          "description": "Birth longitude in decimal degrees (east positive). Give together with lat."
        },
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Date of birth, YYYY-MM-DD (Gregorian calendar)."
        },
        "time": {
          "type": "string",
          "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$",
          "description": "Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."
        },
        "place": {
          "type": "string",
          "maxLength": 120,
          "minLength": 2,
          "description": "Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given."
        },
        "gender": {
          "enum": [
            "male",
            "female"
          ],
          "type": "string",
          "description": "Optional. Classical milan reads the boy's chart against the girl's; with a male/female pair the order is set by gender, otherwise person_a is read as the boy."
        }
      },
      "description": "Birth details of the second person.",
      "additionalProperties": false
    }
  },
  "additionalProperties": false
}
    arguments 110 lines
  • search_place unknown never probed

    Find a birth place (city or town) and its coordinates, Indian places ranked first, from the same city list AstroCalc's kundli form uses. Use it before free_kundli, kundli_milan or explain_dasha when the place name is ambiguous or misspelled (e.g. "Bombay", "Prayagraj", several towns with one name), then pass the chosen label as place or its lat and lon. Returns up to 5 matches with label, state, country, latitude and longitude.

    mcp-tool

    {
  "type": "object",
  "required": [
    "query"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the summary text: 'en' (default) or 'hi'."
    },
    "query": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "Place name, optionally with state or country, e.g. 'Varanasi' or 'Aurangabad, Bihar'."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • learn_answer unknown never probed

    Find the AstroCalc Learn chapters that answer a Vedic astrology question, e.g. "what is Manglik dosha", "is 24 gunas enough", "what is Nadi dosha", "Saturn in the 7th house", "how do dashas work", "what is Sade Sati". Returns up to 3 chapters with title, a short summary paragraph, the canonical URL, and links to the most relevant sections, in English or Hindi. Use it to ground general explanations in a citable source and to give the user a page to read; it does not need birth data. Prefer quoting the summary and linking the URL over paraphrasing from memory.

    mcp-tool

    {
  "type": "object",
  "required": [
    "question"
  ],
  "properties": {
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of titles, summaries and URLs. Defaults to 'hi' for a question written in Devanagari, else 'en'."
    },
    "question": {
      "type": "string",
      "maxLength": 300,
      "minLength": 2,
      "description": "The question or topic, in English, Hindi or Hinglish."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • explain_dasha unknown 27m ago

    Explain Vimshottari dasha periods (Mahadasha / Antardasha), the main timing system of Vedic astrology. Two ways to call it: (1) with birth details (date, time, place) to get the person's running Mahadasha and Antardasha with exact start/end dates, what the period is about for their chart, and the next antardashas (uses the AstroCalc engine); or (2) with lord (and optionally antardasha) set to a planet, e.g. lord "Saturn", antardasha "Venus", for the general meaning and length of that period, with no birth data needed. Use it for "which dasha am I in", "what does Rahu mahadasha mean", "when does my Saturn period end". Birth details are not stored. Traditional information, not a prediction.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees (north positive). Give together with lon."
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees (east positive). Give together with lat."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Date of birth, YYYY-MM-DD (Gregorian calendar)."
    },
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the text fields: 'en' (English, default) or 'hi' (Hindi)."
    },
    "lord": {
      "type": "string",
      "maxLength": 20,
      "description": "Mahadasha planet for a general explanation: Sun, Moon, Mars, Mercury, Jupiter, Venus, Saturn, Rahu or Ketu (Hindi/Sanskrit names like Shani or Guru also work). Ignored when date is given."
    },
    "time": {
      "type": "string",
      "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$",
      "description": "Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."
    },
    "place": {
      "type": "string",
      "maxLength": 120,
      "minLength": 2,
      "description": "Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given."
    },
    "antardasha": {
      "type": "string",
      "maxLength": 20,
      "description": "Optional antardasha (sub-period) planet inside lord, e.g. \"Venus\"."
    }
  },
  "additionalProperties": false
}
    arguments 52 lines
  • yoga_rarity unknown 27m ago

    Look up how common a Vedic astrology yoga is, e.g. Gaja Kesari, Raja yoga, Hamsa, Malavya, Budhaditya, Kemadruma, Kaal Sarp, Neecha Bhanga Raja yoga. Returns "found in about 1 in N charts", the percentage, a rarity label (common / uncommon / rare), a one-line meaning and a Learn link, from AstroCalc's Monte-Carlo sample of 5,000 Indian birth charts run through its yoga engine. Use it when someone asks whether a yoga is rare or special, or to put a yoga from a chart in context. Accepts English or Hindi names. No birth data needed.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the text fields: 'en' (English, default) or 'hi' (Hindi)."
    },
    "yoga": {
      "type": "string",
      "maxLength": 80,
      "minLength": 2,
      "description": "One yoga name, e.g. \"Gaja Kesari\"."
    },
    "yogas": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 80,
        "minLength": 2
      },
      "maxItems": 10,
      "minItems": 1,
      "description": "Several yoga names at once (max 10)."
    }
  },
  "additionalProperties": false
}
    arguments 31 lines
  • free_kundli unknown 27m ago

    Compute a Vedic (Jyotish) birth chart from date, time and place of birth using AstroCalc's ephemeris engine (sidereal, Lahiri ayanamsa, Vimshottari dasha). Use it whenever someone asks for their kundli/janam kundali, Lagna (ascendant), Moon sign (rashi), nakshatra, current Mahadasha/Antardasha, yogas, or strong/weak life areas. Language models cannot compute planetary positions reliably; call this instead of estimating. Returns Lagna, Moon sign, Sun sign, nakshatra and pada, the running Mahadasha and Antardasha with dates, the most notable yoga with how rare it is ("1 in N charts"), life areas that are strong or need care with what helps, a caveat, and a link to the full free report. Birth details are used only to compute the chart in memory and are not stored. Results are traditional astrology information, not predictions or professional advice.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees (north positive). Give together with lon."
    },
    "lon": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees (east positive). Give together with lat."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Date of birth, YYYY-MM-DD (Gregorian calendar)."
    },
    "lang": {
      "enum": [
        "en",
        "hi"
      ],
      "type": "string",
      "description": "Language of the text fields: 'en' (English, default) or 'hi' (Hindi)."
    },
    "time": {
      "type": "string",
      "pattern": "^(([01]\\d|2[0-3]):[0-5]\\d|unknown)$",
      "description": "Local clock time of birth, 24-hour HH:MM (e.g. '06:45', '21:10'). Use 'unknown' (or omit) if not known: noon is used, the Moon sign stays reliable but the Lagna is approximate."
    },
    "place": {
      "type": "string",
      "maxLength": 120,
      "minLength": 2,
      "description": "Birth city or town, e.g. 'Lucknow' or 'Pune, Maharashtra, India'. The best match is used (Indian cities preferred); call search_place first if unsure. Not needed when lat and lon are given."
    }
  },
  "additionalProperties": false
}
    arguments 45 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 4bd44bf91eaa4d84.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/4bd44bf91eaa4d84/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/4bd44bf91eaa4d84/badge.svg)](https://brick.blue/agent/4bd44bf91eaa4d84?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.