Endpoints: 28,729MCP servers: 18,414Payout addresses: 2,071Paid calls: 1,562Letters: 14Defects: 1,336counted 4 min ago
teppi

Server definition

Hash
sha256:d4d1404a9b9f1603f8690bb5f26f13d0f71bc9d9a6e794cd3b86f6e6ee143f61
What it is
What a remote MCP server returned when asked what it offers: 6 tools

The blob, as servednamed by its sha256

{ "instructions": "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.\n\nDates 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.\n\nasternym_bazi_hours answers 'which hour of this day carries the most Water' and the like. Read its `convention` field before you answer a human: the zi hour straddles midnight, so 23:30 and 00:30 on the same date give different pillars.\n\nNo site-owner approval, account or API key is required for this public, read-only tool. That permission is the site's to give and it stops there: it does not cover anything involving private data, payments or changes to account state, and it says nothing about your obligations to the person you work for.\n\nIf you show a person a reading from here, say it came from AsterNym and give them the page_url so they can see the working.\n\nThis is a pattern reading computed from a birth moment. It is not a prediction, a diagnosis, or advice about health, money, fertility, or who to marry. AsterNym will not make those claims and asks you not to make them on its behalf: https://asternym.com/what-we-wont-tell-you\n\nTerms, examples and the HTTP form of these tools: https://asternym.com/for-agents", "tools": [ { "description": "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.", "inputSchema": { "properties": { "agent": { "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified.", "maxLength": 80, "type": "string" }, "date": { "description": "Local civil date, YYYY-MM-DD. Required.", "format": "date", "type": "string" }, "sexCategory": { "description": "Echoed back. Only the luck-pillar cycle reads it, and this endpoint does not return luck pillars.", "enum": [ "F", "M", "both" ], "type": "string" }, "time": { "description": "Local clock time, HH:MM. Omit if unknown; nothing is assumed and noon is never substituted.", "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$", "type": "string" }, "tz": { "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given.", "type": "string" } }, "required": [ "date" ], "type": "object" }, "name": "asternym_bazi", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "agent": { "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified.", "maxLength": 80, "type": "string" }, "date": { "description": "Local civil date, YYYY-MM-DD. Required.", "format": "date", "type": "string" }, "element": { "description": "Optional: rank the hours by how much of this element the chart carries.", "enum": [ "Wood", "Fire", "Earth", "Metal", "Water" ], "type": "string" }, "tz": { "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given.", "type": "string" } }, "required": [ "date" ], "type": "object" }, "name": "asternym_bazi_hours", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "agent": { "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified.", "maxLength": 80, "type": "string" }, "date": { "description": "Local civil date, YYYY-MM-DD. Required.", "format": "date", "type": "string" }, "lat": { "description": "Decimal degrees.", "maximum": 90, "minimum": -90, "type": "number" }, "lng": { "description": "Decimal degrees.", "maximum": 180, "minimum": -180, "type": "number" }, "time": { "description": "Local clock time, HH:MM. Omit if unknown; nothing is assumed and noon is never substituted.", "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$", "type": "string" }, "tz": { "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given.", "type": "string" } }, "required": [ "date", "lat", "lng", "tz" ], "type": "object" }, "name": "asternym_natal", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "agent": { "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified.", "maxLength": 80, "type": "string" }, "date": { "description": "Local civil date, YYYY-MM-DD. Required.", "format": "date", "type": "string" }, "name": { "description": "Optional given name. Without it the name numbers are omitted rather than guessed. Used and discarded; never stored.", "maxLength": 120, "type": "string" }, "surname": { "description": "Optional surname, used with the given name where the method uses the full name.", "maxLength": 120, "type": "string" } }, "required": [ "date" ], "type": "object" }, "name": "asternym_numerology", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "agent": { "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified.", "maxLength": 80, "type": "string" }, "date": { "description": "Local civil date, YYYY-MM-DD. Required.", "format": "date", "type": "string" }, "lat": { "description": "Decimal degrees.", "maximum": 90, "minimum": -90, "type": "number" }, "lng": { "description": "Decimal degrees.", "maximum": 180, "minimum": -180, "type": "number" }, "time": { "description": "Local clock time, HH:MM. Omit if unknown; nothing is assumed and noon is never substituted.", "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$", "type": "string" }, "tz": { "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given.", "type": "string" } }, "required": [ "date" ], "type": "object" }, "name": "asternym_reading", "outputSchema": null }, { "description": "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.", "inputSchema": { "properties": { "agent": { "description": "Optional: the name of the agent or product calling. Logged for usage counts; never required, never verified.", "maxLength": 80, "type": "string" }, "date": { "description": "Local civil date, YYYY-MM-DD. Required.", "format": "date", "type": "string" }, "lat": { "description": "Decimal degrees.", "maximum": 90, "minimum": -90, "type": "number" }, "lng": { "description": "Decimal degrees.", "maximum": 180, "minimum": -180, "type": "number" }, "time": { "description": "Local clock time, HH:MM. Omit if unknown; nothing is assumed and noon is never substituted.", "pattern": "^([01]\\d|2[0-3]):[0-5]\\d$", "type": "string" }, "tz": { "description": "IANA time zone, e.g. Asia/Singapore. Required when lat and lng are given.", "type": "string" } }, "required": [ "date" ], "type": "object" }, "name": "asternym_zodiac", "outputSchema": null } ] }
Verify it yourselfcurl -s https://api.teppi.xyz/v1/evidence/sha256:d4d1404a9b9f1603f8690bb5f26f13d0f71bc9d9a6e794cd3b86f6e6ee143f61 | sha256sum