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

lunonis

https://lunonis.com

Registry code: 60b801ddd766682a

api record

Lunonis calculates real natal charts (tropical zodiac, Placidus houses) and synastry from a birth date, time and city.

To get a chart ask the user for the birth date, the birth time if they know it, and the birth city, then call natal_chart.

endpoint
https://lunonis.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 lunonis live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is lunonis free to use?
Yes — the hub reached it with no key and no payment.
What tools does lunonis have?
3 tools: compatibility, natal_chart, search_places.
Is lunonis 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
495ms

last good check

priced tools
0

of 3 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 3 tools
3 never probed 0 of 3 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.

  • compatibility unknown 1h ago

    Compare two people's charts (synastry) from their birth data. Returns the overall tone (flowing, mixed or charged), whether the Sun elements match, the classic pairings (Venus-Mars, Sun-Moon, Moon-Moon, Venus-Venus), the tightest Moon, Venus, Mars and Sun contacts between the two charts, and a link to the free full comparison on lunonis.com. Counted aspects only: there is no compatibility score. Nothing is stored.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "personA",
        "personB"
      ],
      "properties": {
        "personA": {
          "type": "object",
          "required": [
            "date",
            "place"
          ],
          "properties": {
            "date": {
              "type": "string",
              "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
              "description": "Birth date, YYYY-MM-DD (1900-2100)"
            },
            "time": {
              "type": "string",
              "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
              "description": "Birth time, 24-hour HH:MM local time. Omit if unknown: the rising sign and houses are then left out, never guessed."
            },
            "place": {
              "type": "string",
              "maxLength": 80,
              "minLength": 1,
              "description": "Birth city name (e.g. \"Lviv\" or \"Lviv, Ukraine\"), or a place id from search_places. A name shared by several cities returns candidates to choose from."
            }
          },
          "description": "First person"
        },
        "personB": {
          "type": "object",
          "required": [
            "date",
            "place"
          ],
          "properties": {
            "date": {
              "type": "string",
              "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
              "description": "Birth date, YYYY-MM-DD (1900-2100)"
            },
            "time": {
              "type": "string",
              "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
              "description": "Birth time, 24-hour HH:MM local time. Omit if unknown: the rising sign and houses are then left out, never guessed."
            },
            "place": {
              "type": "string",
              "maxLength": 80,
              "minLength": 1,
              "description": "Birth city name (e.g. \"Lviv\" or \"Lviv, Ukraine\"), or a place id from search_places. A name shared by several cities returns candidates to choose from."
            }
          },
          "description": "Second person"
        }
      }
    }
    arguments 62 lines
  • natal_chart unknown 1h ago

    Calculate a real natal (birth) chart from a birth date, optional birth time and a city. Returns the Sun, Moon and rising signs, every planet with sign, degree and house, the five tightest aspects, an element and modality summary, and a link to the free full chart with the wheel on lunonis.com. Calculated in-house with an ephemeris (tropical zodiac, Placidus houses); nothing is stored. If the city name matches several places it returns status "ambiguous_place" with candidates: ask the user which one, then call again with that id as place.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "date",
        "place"
      ],
      "properties": {
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Birth date, YYYY-MM-DD (1900-2100)"
        },
        "lang": {
          "enum": [
            "en",
            "es",
            "pt",
            "fr",
            "de",
            "it",
            "pl",
            "tr",
            "ja",
            "zh",
            "uk"
          ],
          "type": "string",
          "description": "Language of the returned links (site language code). Default en."
        },
        "time": {
          "type": "string",
          "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
          "description": "Birth time, 24-hour HH:MM local time. Omit if unknown: the rising sign and houses are then left out, never guessed."
        },
        "place": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "Birth city name (e.g. \"Lviv\" or \"Lviv, Ukraine\"), or a place id from search_places. A name shared by several cities returns candidates to choose from."
        }
      }
    }
    arguments 43 lines
  • search_places unknown 1h ago

    Find birth cities by name. Returns up to 6 candidates { id, name, region, country }, the biggest first. Use it to disambiguate a city, then pass the chosen id as the place of natal_chart or compatibility.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "query"
      ],
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "City name, at least 2 characters (e.g. \"Paris\")"
        }
      }
    }
    arguments 15 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 60b801ddd766682a.

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

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.