deepnatal
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| calculate_natal_chartA | Compute a full natal/birth chart: ten planets with sign, degree, house and retrograde status, plus ascendant, midheaven and twelve house cusps. Every result is cross-checked by two independent astronomy implementations and the call FAILS rather than returning a chart when they disagree. Use this whenever a user asks for a birth chart, rising sign, or planetary placements — do not attempt the arithmetic yourself. Requires an exact birth time; if the time is unknown use calculate_chart_without_birth_time instead. |
| calculate_chart_without_birth_timeA | For users who do not know their birth time. Returns only what is genuinely knowable without it, and explicitly lists what is not: ascendant, midheaven and all house positions are omitted with reasons rather than estimated. Also reports whether the Moon changed sign during that day — it does on nearly half of all dates, which means the moon sign itself is undetermined without a time. Never substitute noon and present the result as fact; that is exactly what this tool exists to prevent. |
| verify_ascendantA | Recompute the ascendant along a third path that imports no astrology library at all — pure spherical geometry, the intersection of the ecliptic with the eastern horizon — and report how far it lands from the primary engine. Optionally pass a value produced ELSEWHERE (another website, an app, a printed chart) as |
| inspect_historical_timezoneA | Resolve a local birth date and time to UTC using historical timezone rules, and report whether daylight saving time was actually in effect on that date. This is the single most common source of wrong charts: many tools apply the PRESENT-DAY offset to a past date. Taiwan observed DST 1945-1961 and 1974-1979, mainland China 1986-1991, Japan 1948-1951 — a birth inside those windows is an hour off in tools that ignore them, which moves the ascendant about 15 degrees. Use this to explain WHY two charts differ. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/breezefeng/deepnatal'
If you have feedback or need assistance with the MCP directory API, please join our Discord server