NumeroClaw
Order a personalized numerology reading, paid by the person and delivered by email.
제작자가 쓴 설명(영어 원문)
Vedic astrology readings for AI agents: life areas, compatibility, business timing, gems, ephemeris.
이 세 가지는 절대 하나의 점수로 합치지 않아요. 의견, 측정, 인기는 서로 다른 것이니까요.
이 서버는 아직 쉬운 말로 된 요약을 쓰지 못했어요. 아래는 레지스트리에서 읽어 온 사실이에요.
쓰고 있는 AI 앱을 고른 다음 설정을 복사하세요.
Authorization비밀로 표시된 값은 내 계정의 열쇠예요. 절대 다른 사람과 공유하거나 채팅에 붙여 넣지 마세요.
필요한 것
어떤 앱을 쓰세요?
위에서 앱을 고르세요. 기억해 두었다가 다음부터는 버튼에 “…에 설치”라고 표시해요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
터미널에서 이 명령어를 실행하세요
claude mcp add --transport http astronest https://www.astronest.ai/api/developer/mcp --header 'Authorization: your-value'실행하기 전에 빈 값을 채워 주세요.
프로젝트의 .cursor/mcp.json 또는 ~/.cursor/mcp.json에 붙여 넣으세요
{
"mcpServers": {
"astronest": {
"url": "https://www.astronest.ai/api/developer/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
프로젝트의 .vscode/mcp.json에 붙여 넣으세요
{
"servers": {
"astronest": {
"type": "http",
"url": "https://www.astronest.ai/api/developer/mcp",
"headers": {
"Authorization": "your-value"
}
}
}
}브라우저가 앱을 열지 물어본 다음, 앱이 설정을 보여 주고 확인을 요청해요. 키 값은 비워 두니 직접 입력하세요.
이 주소는 요청 header에 키가 필요한데, 커넥터 추가 메뉴에서는 넣을 수 없어요. 대신 Claude Code, Cursor, VS Code를 쓰세요.
선택한 앱은 이 기기의 쿠키에만 저장돼요. 계정은 필요 없어요.
Authorization 비밀 HTTP header이 설정은 제작자의 레지스트리 정보로 만들었어요. README와 다르면 README를 따르세요.
도구 이름과 설명은 서버가 2026년 11월 6일에 알려 준 그대로예요. 우리가 아니라 제작자가 쓴 글이고, 일반 텍스트로만 보여 드려요.
get_chartUse this when the user wants their birth chart (kundli): ascendant, planets in signs and houses, yogas, the current planetary periods, or one of the classical sub-charts. Sidereal chart: ascendant, the nine grahas, twelve houses, yogas and the life-period (daśā) timeline. A moder
get_dashaUse this when the user asks which planetary period (daśā) they are in, when it ends, or which periods are coming. The current periods include the running pratyantardaśā; send depth 'pratyantardasha' for the full timeline at that level. Cost: 1 credit per call (only successful cal
get_guidanceUse this when the user asks how to conduct themselves in the period they are in: what to do and what to take care with, each with its classical reason. Guidance, not prediction. Plain-language guidance cards for each running daśā level (mahādaśā, antardaśā, …) at `referenceDate`
get_techniquesUse this when the user or an astrologer asks for a specific classical computation — planetary strength, transit point tables, another life-period timeline, the annual chart, house cusps, a named yoga, the birth pañcāṅga, Manglik, house lords and aspects — rather than for a readin
get_prashnaUse this when the user asks a specific question and wants it answered from the moment of asking rather than from a birth chart — "will this deal close?", "will I recover?", "will I find what I lost?" — or when an astrologer gives a horary number 1–249. Send where the user is as `
interpret_domainUse this when the user asks what their chart says about one area of life (career, marriage, finance, health, property, children, education, travel, legal and others) and a reproducible verdict with its reasons and sources is wanted. Prefer it to get_forecast when no written narra
get_life_readingUse this when the user wants their life as a whole: which life areas (marriage, children, career, business, money, property, family, travel, education, spirituality, health) are in focus when, across past and future, and where life stands now. The life's chapters (each mahādaśā i
get_domain_timelineUse this when the user asks about one area of life — when marriage, children, career, money, property or another area is in focus, or what a given stretch of years holds for it. One life area across the whole life: the planets that govern it on this chart, every period that bears
get_relationship_readingUse this when the user asks how two people get on in a bond other than marriage — business partners, siblings, a parent and child, or friends. Reads the bond the way the classical method reads it: the houses that govern this kind of bond and their lords in each chart, the natural
get_venture_timingUse this when the user asks when to start, launch, sign, borrow or expand a business, or which line of business their chart supports. A calendar of the coming months in four labels — commit (sign, open, launch), build (keep building; commit only what can be undone), guarded (low
assess_gemstoneUse this when the user asks whether they should wear a particular gemstone (blue sapphire, emerald, pukhraj, a crystal), or whether a stone they wear suits their chart. Answers the prescription, not the future: which planet the stone strengthens, what that planet owns from this a
get_compatibilityUse this when the user asks whether two people are a good match for marriage and wants the full reading, not only a score. For the fast 36-point score with Manglik alone, use get_guna_milan. Both charts read together for marriage. The 36-point Aṣṭakūṭa (guna milan) is one input:
get_guna_milanUse this when the user asks for the guna milan / kundli matching score (out of 36), or whether either person is Manglik. The classical Aṣṭakūṭa match for a pair (all eight kūṭas, with the Bhakoot and Nāḍī doṣas) and Manglik for both charts reckoned from the lagna, the Moon and Ve
find_muhurtaUse this when the user asks for an auspicious date or time (muhūrta) to do something, such as a wedding, launch, move or purchase, within a date range at a given place. Scans each day in the range and ranks windows for the subject. The pañcāṅga is computed for `eventPlace`, never
get_forecastUse this when the user asks an open question about what lies ahead in one area of life and wants a written answer. It takes tens of seconds; for a fast, structured verdict use interpret_domain. The interpret verdict for `domain`, voiced as a narrative answer to `question` by a la
resolve_timingUse this when the user asks whether now, or a particular date or range, is a good time for a decision such as changing jobs, marrying or investing. It takes tens of seconds. The interpret verdict for `domain`, voiced by a language model as an answer to a decision `question`, read
get_ephemeris_positionsUse this when you need where the Sun, Moon and planets are at a moment (sidereal or tropical), not a reading. Sun, Moon, planets and lunar nodes at one moment: longitude, latitude, distance, speed and retrograde flag, with sign, and nakṣatra and its quarter when sidereal. `equato
get_ephemeris_anglesUse this when you need the ascendant, midheaven or house cusps for a moment and place. Ascendant, midheaven and twelve cusps for a moment and place. Placidus is undefined beyond the polar circles at some moments; the call then returns 422 houses_undefined_at_latitude. Cost: 0.1 c
get_ephemeris_ayanamsaUse this when you need an ayanamsa value at a moment. The ayanāṁśa (the sidereal offset) at a moment, for each supported ayanāṁśa (mean, without nutation). Cost: 0.1 credit per call, billed as 1 credit per started block of 10 Ephemeris calls (only successful calls are charged; a
get_ephemeris_sunriseUse this when you need sunrise and sunset for a date and place, or where the Vedic day begins. Sunrise, sunset and the next sunrise for a local date and place: upper limb at the sea-level horizon with 36.6′ refraction. The Vedic day runs from sunrise to the next sunrise. Cost: 0.
get_ephemeris_seriesUse this when you need planetary positions across a range of dates, for a transit table or to find when a planet changes sign or stations. Positions from start to end (inclusive) every stepMinutes, for transit tables and station finding. At most 1,000 points (too_many_points beyo
누구나 볼 수 있는 정보를 점검했고, 코드는 읽지 않았어요. 해당하지 않는 항목은 개수에서 뺐어요. · 2026년 11월 8일 점검
레지스트리 이름이 GitHub 계정 onedotlinks 기준으로 확인되었고, 이 계정이 저장소를 소유하고 있어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
아직 GitHub에서 이 저장소를 읽어 오지 않았어요
737ms 만에 응답(HTTP 200)
로그인 필요 없음
도구 설명 21개를 읽었고, AI에게 보내는 숨겨진 지시는 없었어요
레지스트리에서 이 카테고리의 활성 서버 전체와 비교했어요. 스타는 게시자가 저장소를 소유한 경우에만 세요.
해당하는 기본 점검 3개 중 3개를 통과했어요. 코드는 읽지 않았어요. 키나 토큰을 넣기 전에 서버가 어떤 권한을 요구하는지 확인하고, 꼭 필요한 권한만 있는 키를 쓰세요.
입력해야 할 값: Authorization
제작자의 클라우드에서 실행돼요. 설치 없이 인터넷으로 연결하지만, 보내는 내용은 제작자의 서버를 거쳐요.
GitHub 저장소는 마지막으로 – 변경됐고, 최신 버전(1.2.0)은 4일 전 레지스트리에 올라왔어요.
Claude Desktop, Claude Code, Cursor, VS Code처럼 MCP를 지원하는 앱에서 쓸 수 있어요. URL로 연결되기 때문에, 원격 MCP 서버를 지원하는 앱(예: 개발자 모드의 ChatGPT)에서도 쓸 수 있어요.
같은 카테고리에는: NumeroClaw, Yinyang Masters, Homo Universalis — 7 Wisdoms (BaZi, Tarot, Vedic Jyotish, Mayan, I-Ching, Human…
같은 카테고리에서 다른 제작자가 만든 서버예요. 스타 순으로 정렬했어요.
카드 보는 법:★ GitHub 스타i세 기둥: 리뷰 · 점검 · 사용 정도i업데이트 = 최신 버전을 레지스트리에 공개한 날i
Order a personalized numerology reading, paid by the person and delivered by email.
Tarot, astrology, numerology, Tu Vi and Bazi tools plus guides on habits and manifestation.
Deterministic 7-Wisdoms (BaZi, Tarot, Vedic Jyotish, Mayan, I-Ching, Human Design, Kabbalah) MCP.
제작자의 저장소에서 쓰인 그대로 가져왔어요. PopNx MCP가 검토하거나 보증한 내용이 아니에요. HTML, 이미지, 스크립트는 제거했어요. 링크를 누르면 이 사이트를 벗어나요.
AstroNest is a Vedic astrology (Jyotiṣa) engine you can call as a REST API or connect to an AI agent over MCP. It computes on its own JPL DE440 ephemeris. The chart, periods and the readings (interpret, guidance, compatibility, guna milan) are deterministic: the same birth data always gives the same answer, with the reasons behind each reading. Only forecast and timing are worded by a language model, and they say so.
This repository has two things: how to connect AstroNest to an AI agent, and a Next.js quickstart on the REST API.
Endpoint (Streamable HTTP): https://www.astronest.ai/api/developer/mcp
Claude Code
claude mcp add --transport http astronest https://www.astronest.ai/api/developer/mcp \
--header "Authorization: Bearer YOUR_ASTRONEST_KEY"
`mcp.json` (Cursor, VS Code and other clients that read this format)
{
"mcpServers": { "astronest": { "url": "https://www.astronest.ai/api/developer/mcp", "headers": { "Authorization": "Bearer YOUR_ASTRONEST_KEY" } } } }
Also on Smithery and the MCP Registry as io.github.onedotlinks/astronest.
Each tool answers one question. The interpretive ones read the chart the way a practitioner does and return the reasons, not just positions:
| Tool | The question it answers |
|---|---|
get_life_reading | What does my life look like as a whole — which areas (marriage, children, career, money, property…) come into focus when, past and future? |
get_domain_timeline | When is marriage, career or another area in focus, or what do the next few years hold for it? |
get_relationship_reading | How do two people get on as business partners, siblings, parent and child, or friends? |
get_venture_timing | When should I launch, sign or borrow — and which line of business does my chart support? |
assess_gemstone | Should I wear this stone (blue sapphire, pukhraj, emerald…), and why or why not? |
get_compatibility, get_guna_milan | Kundli matching: the 36-point Aṣṭakūṭa score, Manglik from the lagna, Moon and Venus, and the full pair reading |
interpret_domain, get_guidance | What does my chart say about one area of life, and what do the running periods ask of me now? |
find_muhurta | Which days and windows in a date range suit an event? |
get_chart, get_dasha, ephemeris tools | The chart (with its classical sub-charts), the life-period (daśā) timeline down to the sub-sub-period, and raw JPL DE440 positions |
The readings describe what the chart shows and why. They are symbolic interpretation, not predictions, and not medical, legal, financial or psychological advice; every response carries that disclaimer.
A small Next.js app on the AstroNest Developer API. Enter a birth date, time and place and get:
None of the three AstroNest calls uses a language model. They are deterministic, so they return in seconds and the same input always gives the same answer.
402 credits_exhausted until you buy a credit pack; sandbox keys keep working. npm install
cp .env.example .env.local
3. **Run.**
npm run dev
Open http://localhost:3000.
browser ──► /api/astronest/{chart|guidance|interpret} ──► AstroNest API (your key, server-side)
└─► /api/explain ──────────────────────────────► your LLM (optional)
lib/astronest.ts is a typed client. It is the file to copy into your own app.app/api/astronest/[op]/route.ts forwards only those three operations, so the route can't be used to call every endpoint your key allows.app/api/explain/route.ts sends the reading AstroNest computed to any OpenAI-compatible chat-completions endpoint (OpenAI, Vercel AI Gateway, OpenRouter, a local Ollama) and tells the model to use only the facts it was given. Your model writes the words; AstroNest does the astrology.NEXT_PUBLIC_, and never call the API from the browser. The API sends no CORS headers, so browser calls fail anyway.localhost. Put your own sign-in (and ideally a rate limit) in front of them before you set ALLOW_PUBLIC_DEMO=true. The localhost check reads the request host, so don't rely on it behind a proxy that rewrites Host.| Endpoint | Credits | Notes |
|---|---|---|
POST /v1/chart | 1 | add location for astrocartography and a relocated frame |
POST /v1/dasha | 1 | the full life-period (daśā) timeline |
POST /v1/guidance | 3 | referenceDate for any other moment |
POST /v1/interpret | 5 | 15 domains |
POST /v1/timing/resolve | 7 | narrated by a language model; allow 90 s |
POST /v1/forecast | 8 | narrated by a language model; allow 90 s |
POST /v1/muhurta | 10 | auspicious windows in a date range |
POST /v1/compatibility | 12 | two charts read together |
POST /v1/guna-milan | 2 | the 36-point Aṣṭakūṭa match + Manglik (lagna, Moon, Venus) for a pair |
POST /v1/life-reading | 10 | the whole-life reading: chapters and 11 life areas, past and future (areas narrows it) |
POST /v1/domain-timeline | 3 | one life area across the life: every period that governs it, optionally within a date window |
POST /v1/relationship | 8 | business partners, siblings, parent & child, friends: bond houses, cross-chart contacts, the bond meter |
POST /v1/venture-timing | 10 | when to commit, build, guard or hold; the businesses you describe ranked on the chart |
POST /v1/gem-assessment | 5 | should this chart wear this stone: the verdict, every ground for and against, how long the reason lasts |
POST /v1/ephemeris/positions | 0.1 | raw positions at a moment (JPL DE440); no birth data needed |
POST /v1/ephemeris/angles | 0.1 | ascendant, MC and house cusps for a moment and place |
POST /v1/ephemeris/ayanamsa | 0.1 | the ayanāṁśa value for a moment, from the supported set |
POST /v1/ephemeris/sunrise | 0.1 | sunrise, sunset and next sunrise for a local date |
POST /v1/ephemeris/series | 1 | per started 100 points, up to 1,000 |
The four single-moment Ephemeris calls cost 0.1 credit each: 1 credit per started block of 10, counted across them per account (the call that opens a block reports units_charged: 1, the next nine report 0). Only successful (2xx) calls are charged. When credits run out, the API returns 402 credits_exhausted; buy a pack in the developer portal. Paid credits do not expire.