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

astrolog-chatgpt-app

https://astrolog-app.com

Registry code: 83e064340bed53ea

api record

Astrolog exposes public navigation metadata for Astrolog and Mi Astrologa tools, plus a real astronomical engine. For user requests about finding an Astrolog astrology, tarot, I Ching, horoscope, transit, synastry, solar return, or chart page, call search_astrolog_features first. Call render_astrolog_features only when an interactive launch widget is helpful. Use locale "en" for astrolog-app.com and locale "es" for miastrologa.com unless the user asks otherwise.

For anything that requires actual planetary positions, do NOT answer from memory — call the engine tools, which compute from NASA JPL…

endpoint
https://astrolog-app.com/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 astrolog-chatgpt-app live?
Yes — it answered the hub's last check (checked 5h ago). It answered 100% of checks over the last 30 days.
Is astrolog-chatgpt-app free to use?
Yes — the hub reached it with no key and no payment.
What tools does astrolog-chatgpt-app have?
6 tools: resolve_birthplace, compute_natal_chart, compute_transits, render_astrolog_features, search_astrolog_features, sky_today.
Is astrolog-chatgpt-app 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
186ms

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

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

  • render_astrolog_features open 5h ago

    Render an interactive Astrolog launch widget for the selected public features. It opens ordinary free-tool pages and contains no product, purchase or checkout actions. Call search_astrolog_features first when you need to inspect or refine the matching results.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 240
    },
    "domain": {
      "enum": [
        "astrolog-app.com",
        "miastrologa.com"
      ],
      "type": "string"
    },
    "locale": {
      "enum": [
        "en",
        "es"
      ],
      "type": "string"
    }
  }
}
    arguments 29 lines
  • search_astrolog_features open 5h ago

    Find matching public Astrolog or Mi Astrologa pages for a user request. Returns canonical free-tool links and short descriptions, never product, purchase or checkout links. Use this before rendering the launch widget.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1
    },
    "query": {
      "type": "string",
      "maxLength": 240
    },
    "domain": {
      "enum": [
        "astrolog-app.com",
        "miastrologa.com"
      ],
      "type": "string"
    },
    "locale": {
      "enum": [
        "en",
        "es"
      ],
      "type": "string"
    }
  }
}
    arguments 29 lines
  • sky_today open 5h ago

    Get what the sky is actually doing right now, computed from NASA JPL DE440S ephemerides with Skyfield: current geocentric longitude, sign and degree for every planet plus Chiron and the Mean Node, the real Moon phase and illumination, which planets are retrograde at this moment, and the aspects currently in orb with their exact orbs. Needs no birth data. Use this for "what is happening astrologically today" questions instead of answering from memory.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "locale": {
      "enum": [
        "en",
        "es"
      ],
      "type": "string",
      "description": "en or es. Only affects the returned links."
    }
  }
}
    arguments 14 lines
  • resolve_birthplace unknown never probed

    Turn a place name into the exact latitude, longitude and IANA timezone needed by compute_natal_chart and compute_transits, using Astrolog's own database of ~100,000 cities. ALWAYS call this instead of supplying coordinates or a timezone from memory: the timezone determines the Ascendant and every house cusp, so a plausible but wrong zone produces a confidently wrong chart. Returns several candidates when a name is ambiguous (there are many Springfields, and a Paris in Texas) — show them to the user and let them choose rather than picking one. Returns an empty list when nothing matches, in which case ask the user for a larger nearby city or the country, and do NOT fall back to remembered coordinates.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "query"
  ],
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 10,
      "minimum": 1,
      "description": "Maximum candidates to return. Default 4."
    },
    "query": {
      "type": "string",
      "maxLength": 120,
      "minLength": 2,
      "description": "Place as the user said it, e.g. \"Lyon\", \"Springfield, Illinois\", \"Bogota\"."
    }
  }
}
    arguments 21 lines
  • compute_natal_chart unknown never probed

    Compute a real natal (birth) chart from NASA JPL DE440S ephemerides with Skyfield: exact planetary longitudes, sign and degree, house placements (Placidus by default, Whole Sign on request), Ascendant and Midheaven, and the aspects between them. Requires an exact birth date, local birth time, latitude, longitude and IANA timezone, and it cannot compute houses or an Ascendant without a birth time. It does not geocode: call resolve_birthplace first to turn a place name into those exact numbers, and never supply coordinates or a timezone from memory — the zone sets the Ascendant and every house cusp, so a wrong one yields a confidently wrong chart. Returns the computed chart data and a plain link to the same free chart; it does not return product, price, offer-specific, purchase or checkout links.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "time",
    "latitude",
    "longitude",
    "timezone"
  ],
  "properties": {
    "city": {
      "type": "string",
      "maxLength": 120,
      "description": "Human-readable birth place label, for display only."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      "description": "Local birth time at the birth place, 24-hour HH:MM."
    },
    "locale": {
      "enum": [
        "en",
        "es"
      ],
      "type": "string",
      "description": "Language for the returned free-chart link. Defaults to en."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees, north positive."
    },
    "timezone": {
      "type": "string",
      "minLength": 3,
      "description": "IANA timezone of the birth place, e.g. \"Europe/Madrid\". Required — a wrong zone moves the Ascendant and every house cusp."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees, east positive."
    },
    "house_system": {
      "enum": [
        "placidus",
        "whole"
      ],
      "type": "string",
      "description": "House system. Defaults to placidus."
    }
  }
}
    arguments 61 lines
  • compute_transits unknown never probed

    Compute real transits to a natal chart over a date window, from NASA JPL DE440S ephemerides with Skyfield. Takes the same birth parameters as compute_natal_chart plus a start and end date, and returns the transiting body, the natal body it aspects, the aspect, the orb and the UTC instant of each hit. The window is capped at 90 days (about four months) and longer windows are sampled more coarsely, so this is a forecast timeline, not minute-precise event timing. Computation can take up to a minute for long windows. The natal foundation and transit scan are computed in memory; this tool does not create a person or save a report.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "date",
    "time",
    "latitude",
    "longitude",
    "timezone",
    "start",
    "end"
  ],
  "properties": {
    "end": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Last day of the transit window, YYYY-MM-DD. At most 90 days after start."
    },
    "city": {
      "type": "string",
      "maxLength": 120,
      "description": "Human-readable birth place label, for display only."
    },
    "date": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "Birth date, YYYY-MM-DD."
    },
    "time": {
      "type": "string",
      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      "description": "Local birth time at the birth place, 24-hour HH:MM."
    },
    "start": {
      "type": "string",
      "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
      "description": "First day of the transit window, YYYY-MM-DD."
    },
    "locale": {
      "enum": [
        "en",
        "es"
      ],
      "type": "string",
      "description": "Language for the returned free-chart link. Defaults to en."
    },
    "latitude": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Birth latitude in decimal degrees, north positive."
    },
    "timezone": {
      "type": "string",
      "minLength": 3,
      "description": "IANA timezone of the birth place, e.g. \"Europe/Madrid\". Required — a wrong zone moves the Ascendant and every house cusp."
    },
    "longitude": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Birth longitude in decimal degrees, east positive."
    },
    "house_system": {
      "enum": [
        "placidus",
        "whole"
      ],
      "type": "string",
      "description": "House system. Defaults to placidus."
    }
  }
}
    arguments 73 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 83e064340bed53ea.

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