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

cosmic-chemistry

https://cosmicchemistry.co

Registry code: 73d7f76d80406ecf

api record

Cosmic Chemistry computes Vedic (sidereal, Lahiri, whole-sign houses) astrology: Vedic astrology, made fun and honest. Present results as tendencies the person can check against their life, never as predictions. No fear, no doom, no gemstone or puja remedies, no life-span or health readings. When a Western app gives a different sign or house, say both systems are valid and measure from different starting points. Use the birth place exactly as the user gave it; if the answer says which place was used, mention it so they can correct it. End with the page link, and for patterns the person keeps…

endpoint
https://cosmicchemistry.co/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 cosmic-chemistry live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is cosmic-chemistry free to use?
Yes — the hub reached it with no key and no payment.
What tools does cosmic-chemistry have?
13 tools: vedic_birth_chart, vedic_rising_sign, moon_sign_nakshatra, sade_sati_check, saturn_return_dates, current_dasha, manglik_check, planet_in_house_meaning, ….
Is cosmic-chemistry 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 13 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 13 tools
3 open 10 never probed 3 of 13 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.

  • daily_panchang open 1h ago

    Use this when someone asks for today’s panchang or the Hindu calendar for a place: the tithi, nakshatra, yoga, karana, Rahu kaal (rahu kalam), Yamaganda, Gulika, Abhijit muhurat, choghadiya, sunrise and sunset, or which festival or vrat falls today ("aaj ka panchang", "what is today’s tithi", "Rahu kaal today in Pune", "is today Ekadashi", "good time to start today"). Also answers for another date. Needs no birth details. Send the town if the person has said it; without one the answer is for New Delhi. Do not use for a person’s birth chart or birth star.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "date": {
      "type": "string",
      "description": "The date wanted, as YYYY-MM-DD. Leave out for today at that place."
    },
    "place": {
      "type": "string",
      "description": "Town or city, with region or country if known, e.g. \"Pune, India\" or \"Austin, Texas\"."
    }
  },
  "additionalProperties": false
}
    arguments 15 lines
  • mercury_retrograde open 1h ago

    Use this when someone asks whether Mercury is retrograde now, when the next Mercury retrograde starts or ends, or for the Mercury retrograde dates of a year ("is Mercury in retrograde", "when does Mercury retrograde end", "Mercury retrograde 2027 dates"). Returns the period running now or the next one, with its shadow dates and signs, and the ones after it. Needs no birth details and no place. Say it without fear: it is a stretch of the calendar, not a warning.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "year": {
      "type": "integer",
      "maximum": 2031,
      "minimum": 2024,
      "description": "Optional: list every Mercury retrograde of this year."
    }
  },
  "additionalProperties": false
}
    arguments 13 lines
  • festival_and_vrat_dates open 1h ago

    Use this when someone asks when a Hindu festival, vrat or observance falls, or what is coming up: "when is Diwali", "next Ekadashi", "Karwa Chauth date", "Pradosh vrat this month", "festivals in November", "when is Pongal in Chennai". Returns the dated list for a place, from a start date (today if left out), for up to 120 days. For a festival in a later year, set "from" to about a month before its usual season. Dates can differ from city to city, so send the town if known; without one the list is for New Delhi. Needs no birth details.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {
    "days": {
      "type": "integer",
      "maximum": 120,
      "minimum": 1,
      "description": "How many days to list, 1 to 120. Default 45."
    },
    "from": {
      "type": "string",
      "description": "First day of the list, as YYYY-MM-DD. Leave out for today."
    },
    "name": {
      "type": "string",
      "description": "Optional: only days whose name contains this word, e.g. \"Ekadashi\", \"Diwali\", \"Pradosh\"."
    },
    "place": {
      "type": "string",
      "description": "Town or city, with region or country if known, e.g. \"Pune, India\" or \"Austin, Texas\"."
    }
  },
  "additionalProperties": false
}
    arguments 25 lines
  • vedic_birth_chart unknown never probed

    Use this when someone asks for their Vedic birth chart, kundli, janam kundali, sidereal chart, or where their planets are in Vedic astrology (signs, houses, nakshatras, rising sign). Returns all nine planets with sign, degree, house (needs birth time), nakshatra and pada. If the person asks for only one thing (rising sign, Moon sign, dasha, Manglik), use the narrower tool. Needs birth date and town, and the time for houses; ask if missing. Do not use for Western/tropical charts or daily horoscopes.

    mcp-tool

    {
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • vedic_rising_sign unknown never probed

    Use this when someone asks for their rising sign, ascendant or lagna in Vedic astrology, or why their Vedic rising sign differs from a Western app. Returns the Vedic rising sign, its ruler, and the Western rising sign for comparison. Needs the birth time.

    mcp-tool

    {
  "type": "object",
  "required": [
    "birth_date",
    "birth_time",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • moon_sign_nakshatra unknown never probed

    Use this when someone asks for their Moon sign (rashi), birth star or nakshatra and pada in Vedic astrology. Also use for "birth star", "janma nakshatra", "what is my rashi", "my zodiac sign in Vedic astrology". Works from the birth date and town; the time makes it exact when the Moon changes sign that day. Do not use for Western sun signs, horoscopes or the rising sign.

    mcp-tool

    {
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • sade_sati_check unknown never probed

    Use this when someone asks whether they are in Sade Sati, when their Sade Sati starts or ends, or about Saturn’s seven and a half years. Also use for Shani sade sati and "Saturn’s 7.5 years". Returns whether it is running now, its three phases with dates, and the next one. Needs birth date and town.

    mcp-tool

    {
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • saturn_return_dates unknown never probed

    Use this when someone asks when their Saturn return is (in Vedic, sidereal reckoning), whether they are in it now, or at what ages it comes. Also use for "Saturn return at 28/29" and Shani return. Returns every Saturn return with dates and ages. Needs birth date and town; ask if missing.

    mcp-tool

    {
  "type": "object",
  "required": [
    "birth_date",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}
    arguments 22 lines
  • current_dasha unknown never probed

    Use this when someone asks which mahadasha or antardasha they are running, their Vimshottari dasha timeline, when their next dasha begins, or when a dasha ends ("when does my Rahu dasha end", "my current dasha lord"). Returns every mahadasha with dates, and the current and next antardasha. Needs birth date, time and town.

    mcp-tool

    {
  "type": "object",
  "required": [
    "birth_date",
    "birth_time",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • manglik_check unknown never probed

    Use this when someone asks if they are Manglik or have Mangal dosha. Returns where Mars falls from the rising sign, the Moon and Venus. Present it honestly: about half of all charts count as Manglik by the common rule, so it is common, not a danger. Needs the birth time.

    mcp-tool

    {
  "type": "object",
  "required": [
    "birth_date",
    "birth_time",
    "birth_place"
  ],
  "properties": {
    "birth_date": {
      "type": "string",
      "description": "Date of birth, YYYY-MM-DD, e.g. 1993-03-17."
    },
    "birth_time": {
      "type": "string",
      "description": "Local clock time of birth, 24-hour HH:MM, e.g. 13:35. As exact as possible (from a birth certificate)."
    },
    "birth_place": {
      "type": "string",
      "description": "Town or city of birth, with region or country if known, e.g. \"Chicago, Illinois, US\" or \"Pune, India\"."
    }
  },
  "additionalProperties": false
}
    arguments 23 lines
  • planet_in_house_meaning unknown never probed

    Use this when someone asks what a planet in a house means in Vedic astrology, e.g. "Venus in the 8th house", "Saturn in 12th house meaning", "Sun in my 12th house". Use this instead of vedic_birth_chart when the person names a planet and a house, even in the first person ("my Venus is in my 8th"); do not ask for birth details. Returns what the house holds, what the planet brings, and our article when one exists. None of these tools cover daily horoscopes, gemstones, tarot or predictions.

    mcp-tool

    {
  "type": "object",
  "required": [
    "planet",
    "house"
  ],
  "properties": {
    "house": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "House number, 1 to 12."
    },
    "planet": {
      "enum": [
        "sun",
        "moon",
        "mars",
        "mercury",
        "jupiter",
        "venus",
        "saturn",
        "rahu",
        "ketu"
      ],
      "type": "string"
    }
  },
  "additionalProperties": false
}
    arguments 30 lines
  • moon_today unknown never probed

    Use this when someone asks where the Moon is right now or today: its sign (Vedic and Western), its nakshatra, its phase, or when the next full moon or new moon comes ("what sign is the Moon in today", "moon phase today", "next full moon", "today’s nakshatra"). Needs no birth details and no place. Do not use for a person’s own Moon sign at birth: use moon_sign_nakshatra for that.

    mcp-tool

    {
  "type": "object",
  "required": [],
  "properties": {},
  "additionalProperties": false
}
    arguments 6 lines
  • planetary_hours unknown never probed

    Use this when someone asks for the planetary hours or hora of a day and place, which planet rules the hour now, or when a planet’s hour comes ("planetary hours today in London", "what planetary hour is it", "when is the Venus hour today", "hora today"). Returns the twelve day hours and twelve night hours counted from sunrise, with clock times for that place, and the hour running now. Needs the town: ask if the person has not said it. Needs no birth details.

    mcp-tool

    {
  "type": "object",
  "required": [
    "place"
  ],
  "properties": {
    "date": {
      "type": "string",
      "description": "The date wanted, as YYYY-MM-DD. Leave out for today at that place."
    },
    "place": {
      "type": "string",
      "description": "Town or city, with region or country if known, e.g. \"Pune, India\" or \"Austin, Texas\"."
    }
  },
  "additionalProperties": false
}
    arguments 17 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 73d7f76d80406ecf.

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