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

asternym

https://asternym.com

Registry code: 9dbce83b6daa1d6f

api record

AsterNym computes birth charts: BaZi (Four Pillars), Chinese and Western zodiac, and Pythagorean numerology, from the same engine that runs every page on asternym.com.

Dates are local civil dates (YYYY-MM-DD) and times are local 24-hour clock times (HH:MM). If you do not know the birth time, leave it out: the tools return a chart without an hour pillar and say so. They never assume noon, and you should not either.

endpoint
https://asternym.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 asternym live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is asternym free to use?
Yes — the hub reached it with no key and no payment.
What tools does asternym have?
6 tools: asternym_natal, asternym_bazi_hours, asternym_bazi, asternym_numerology, asternym_reading, asternym_zodiac.
Is asternym 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 98.8%· all time 98.8%

latency
396ms

last good check

priced tools
0

of 6 tools

_ answered our checks, 90 days 332 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
lifestyle & home
used for
  • compute a bazi four pillars chart
  • get a western natal chart
  • calculate numerology life path
  • find chinese and western zodiac signs
takes → gives
data → data
tools
6 reads
_ 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.

  • asternym_natal reads unknown 20h ago

    Ten planets with sign, degree, whole-sign house and retrograde flag; the Ascendant, midheaven and their opposites; the twelve whole-sign houses; the mean lunar nodes; the five major aspects with orb and whether each is applying or separating; plus stelliums, retrogrades and the Moon's phase. Tropical zodiac, geocentric apparent positions, astronomy-engine. This is the one endpoint that requires lat, lng and tz: the angles and houses are a place on the Earth meeting the sky. A time is optional, and without one the angles and houses are null rather than taken from noon, and the Moon is a noon estimate the notes warn about. The same thing over HTTP: POST https://asternym.com/api/v1/natal.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date",
    "lat",
    "lng",
    "tz"
  ],
  "properties": {
    "tz": {
      "type": "string",
      "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given."
    },
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Decimal degrees."
    },
    "lng": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Decimal degrees."
    },
    "date": {
      "type": "string",
      "format": "date",
      "description": "Local civil date, YYYY-MM-DD. Required."
    },
    "time": {
      "type": "string",
      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      "description": "Local clock time, HH:MM. Omit if unknown; nothing is assumed and noon is never substituted."
    },
    "agent": {
      "type": "string",
      "maxLength": 80,
      "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified."
    }
  }
}
    arguments 42 lines
  • asternym_bazi_hours reads unknown 20h ago

    The twelve 時辰 of a day, each with its hour pillar, hidden stems, ten god and the element counts of the whole chart at that hour. The 23:00-00:00 slot is returned separately as lateZi: from 23:00 the hour pillar has already turned to the next day's 子 (早子時) while the day pillar has not, so it differs from the 00:00-01:00 slot on the same date. These are the Chinese double-hours, not the Western planetary hours. The same thing over HTTP: POST https://asternym.com/api/v1/bazi/hours.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "tz": {
      "type": "string",
      "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given."
    },
    "date": {
      "type": "string",
      "format": "date",
      "description": "Local civil date, YYYY-MM-DD. Required."
    },
    "agent": {
      "type": "string",
      "maxLength": 80,
      "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified."
    },
    "element": {
      "enum": [
        "Wood",
        "Fire",
        "Earth",
        "Metal",
        "Water"
      ],
      "type": "string",
      "description": "Optional: rank the hours by how much of this element the chart carries."
    }
  }
}
    arguments 33 lines
  • asternym_bazi reads unknown 20h ago

    Pillars, day master, hidden stems (藏干) with their ten gods (十神), element counts, dominant and missing elements, na yin, the twelve stages and the void branches. The year turns at Li Chun, not at 1 January or Lunar New Year. Without a time there is no hour pillar and the response says so. The same thing over HTTP: POST https://asternym.com/api/v1/bazi.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "tz": {
      "type": "string",
      "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given."
    },
    "date": {
      "type": "string",
      "format": "date",
      "description": "Local civil date, YYYY-MM-DD. Required."
    },
    "time": {
      "type": "string",
      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      "description": "Local clock time, HH:MM. Omit if unknown; nothing is assumed and noon is never substituted."
    },
    "agent": {
      "type": "string",
      "maxLength": 80,
      "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified."
    },
    "sexCategory": {
      "enum": [
        "F",
        "M",
        "both"
      ],
      "type": "string",
      "description": "Echoed back. Only the luck-pillar cycle reads it, and this endpoint does not return luck pillars."
    }
  }
}
    arguments 36 lines
  • asternym_numerology reads unknown 3h ago

    Pythagorean numerology: Life Path, birthday number and its components, and with a name the expression, soul urge, personality, cornerstone, capstone and hidden passion. Master numbers are kept where the position allows. The same thing over HTTP: POST https://asternym.com/api/v1/numerology.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "date": {
      "type": "string",
      "format": "date",
      "description": "Local civil date, YYYY-MM-DD. Required."
    },
    "name": {
      "type": "string",
      "maxLength": 120,
      "description": "Optional given name. Without it the name numbers are omitted rather than guessed. Used and discarded; never stored."
    },
    "agent": {
      "type": "string",
      "maxLength": 80,
      "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified."
    },
    "surname": {
      "type": "string",
      "maxLength": 120,
      "description": "Optional surname, used with the given name where the method uses the full name."
    }
  }
}
    arguments 28 lines
  • asternym_reading reads unknown 3h ago

    Sun sign, Chinese animal and element, BaZi day master and pillars, Life Path and the AsterNym identity, from the same engine as every page on the site. The same thing over HTTP: POST https://asternym.com/api/v1/reading.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "tz": {
      "type": "string",
      "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given."
    },
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Decimal degrees."
    },
    "lng": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Decimal degrees."
    },
    "date": {
      "type": "string",
      "format": "date",
      "description": "Local civil date, YYYY-MM-DD. Required."
    },
    "time": {
      "type": "string",
      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      "description": "Local clock time, HH:MM. Omit if unknown; nothing is assumed and noon is never substituted."
    },
    "agent": {
      "type": "string",
      "maxLength": 80,
      "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified."
    }
  }
}
    arguments 39 lines
  • asternym_zodiac reads unknown 3h ago

    The Sun's sign from its apparent ecliptic longitude, with a cusp reported rather than resolved by assuming noon, and the Chinese animal, element and polarity with the Lunar New Year boundary. Note the two calendars differ on purpose: the Chinese year here turns at Lunar New Year, while the BaZi year pillar turns at Li Chun. The same thing over HTTP: POST https://asternym.com/api/v1/zodiac.

    mcp-tool

    {
  "type": "object",
  "required": [
    "date"
  ],
  "properties": {
    "tz": {
      "type": "string",
      "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given."
    },
    "lat": {
      "type": "number",
      "maximum": 90,
      "minimum": -90,
      "description": "Decimal degrees."
    },
    "lng": {
      "type": "number",
      "maximum": 180,
      "minimum": -180,
      "description": "Decimal degrees."
    },
    "date": {
      "type": "string",
      "format": "date",
      "description": "Local civil date, YYYY-MM-DD. Required."
    },
    "time": {
      "type": "string",
      "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$",
      "description": "Local clock time, HH:MM. Omit if unknown; nothing is assumed and noon is never substituted."
    },
    "agent": {
      "type": "string",
      "maxLength": 80,
      "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified."
    }
  }
}
    arguments 39 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 9dbce83b6daa1d6f.

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