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

genesis-astro

https://genesis-astro-guide-r2owtywexa-an.a.run.app

Registry code: 5ba8644156ec3db6

api record

Free astrology calculations: Western tropical and Vedic sidereal (Lahiri) signs, nakshatra, Ascendant, retrograde dates and sign ingress times. Each result has learn-more page links and a full_reading.app_url for a complete free chart analysis on GenesisCore; please show it to the user.

endpoint
https://genesis-astro-guide-r2owtywexa-an.a.run.app/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 genesis-astro live?
Yes — it answered the hub's last check (checked 14h ago). It answered 100% of checks over the last 30 days.
Is genesis-astro free to use?
Yes — the hub reached it with no key and no payment.
What tools does genesis-astro have?
4 tools: get_sign_ingresses, calculate_birth_chart_signs, get_retrograde_periods, get_current_sky.
Is genesis-astro 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
997ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 2 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 4 tools
2 open 2 never probed 2 of 4 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_retrograde_periods open 14h ago

    Retrograde start and end (station) times in UTC with sign and degree for Mercury, Venus, Mars, Jupiter and Saturn, 2025-2027. Use for 'when is Mercury retrograde', 'is Mercury retrograde now'.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "year": {
          "type": "integer",
          "description": "Optional, 2024-2027"
        },
        "planet": {
          "enum": [
            "mercury",
            "venus",
            "mars",
            "jupiter",
            "saturn"
          ],
          "type": "string",
          "description": "Optional; all planets if omitted"
        }
      }
    }
    arguments 20 lines
  • get_current_sky open 14h ago

    Current Western (tropical) and Vedic (sidereal Lahiri) signs and degrees of the Sun, Moon and planets, with retrograde flags.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • get_sign_ingresses unknown never probed

    Exact UTC times when Mercury, Venus or Mars entered each zodiac sign (Western tropical) between 1940 and 2030, filtered by a date range. Up to 60 rows.

    mcp-tool

    {
      "type": "object",
      "required": [
        "planet"
      ],
      "properties": {
        "to": {
          "type": "string",
          "description": "End date YYYY-MM-DD (default from + 1 year)"
        },
        "from": {
          "type": "string",
          "description": "Start date YYYY-MM-DD (default today)"
        },
        "planet": {
          "enum": [
            "mercury",
            "venus",
            "mars"
          ],
          "type": "string"
        }
      }
    }
    arguments 24 lines
  • calculate_birth_chart_signs unknown never probed

    Sun, Moon, Mercury, Venus, Mars, Jupiter, Saturn, Uranus, Neptune and Pluto signs in both the Western tropical zodiac and the Vedic sidereal zodiac (Lahiri), Moon nakshatra, retrograde flags, and optional Ascendant/MC/Lagna when latitude and longitude are given. Use for questions like 'what is my moon sign', 'my Vedic rashi', 'my Venus sign'. Returns explanation page links and a link to a full free reading.

    mcp-tool

    {
      "type": "object",
      "required": [
        "date"
      ],
      "properties": {
        "date": {
          "type": "string",
          "description": "Birth date YYYY-MM-DD (1900-2100)"
        },
        "lang": {
          "enum": [
            "en",
            "ja"
          ],
          "type": "string",
          "description": "Language of links (default en)"
        },
        "time": {
          "type": "string",
          "description": "Local birth time HH:MM 24h. Defaults to 12:00; the Moon can change sign within a day, so ask for the time."
        },
        "latitude": {
          "type": "number",
          "description": "Optional, birthplace latitude (-66..66) for Ascendant"
        },
        "longitude": {
          "type": "number",
          "description": "Optional, birthplace longitude, east positive"
        },
        "utc_offset": {
          "type": "number",
          "description": "Hours from UTC at the birthplace on that date, e.g. 9 Tokyo, 5.5 India, -3 São Paulo, -5 New York winter / -4 summer, 1 Madrid winter / 2 summer"
        }
      }
    }
    arguments 36 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 5ba8644156ec3db6.

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

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.