mythsensus-mcp
An MCP server that exposes deterministic Mythsensus divination calculations, deity lore, and reference methodology as callable tools.
Compute a Cosmic Score (1–999) with tier, percentile, and a 5-of-26 consensus preview from a birth date; optional systems, birth time, location, timezone, language, and unknown-time handling.
Get a focused raw reading for any one of 26 divination systems, using typo-tolerant system slugs.
List all 26 systems with canonical slug, English/Thai name, region, and required inputs.
Draw a deterministic daily deity blessing/card for a chart and date.
Look up encyclopedic lore for 1,044 deities across 9 mythologies in English and/or Thai, with partial-name matching.
Retrieve Mythsensus interpretation rules and 26-system consensus methodology to ground answers.
Retrieve engineering-honest engine metadata: architecture, limitations, sophistication tier, and roadmap.
Resolve city names or lat/lon offline for calculations; local npm mode performs no network calls during tool use.
This server has a remotely hosted endpoint. Open its connector listing for connection details, authentication requirements, and setup instructions:
Mythsensus MCP
An MCP (Model Context Protocol) server that exposes the Mythsensus engine — 26 ancient divination algorithms implemented in TypeScript — as tools your Claude Desktop (or any MCP-compatible AI client) can call.
You: "What's my Cosmic Score? I was born March 15, 1990."
Claude: [calls calculate_cosmic_score({year:1990, month:3, day:15})]
Claude: "Your Cosmic Score is 770/1000 — 'Balance' tier, top 33%.
Sun in Pisces. BaZi day master is Yin Earth. Life Path 1.
Mayan Kin 163 (Akbal). Human Design: Generator..."What this is (and isn't)
This is a Model Context Protocol server that bundles the compiled Mythsensus engine (1.1 MB JavaScript, plus a 2.8 MB deity encyclopedia) and exposes 7 tools Claude can invoke. Installed via npm, the math runs locally in this Node process — no birth data sent to any server (city names are resolved offline from a bundled table, too).
This is not an LLM wrapper. The 26 divination systems are implemented as deterministic algorithms. Same input, same output, every time. The LLM (your Claude itself, when you talk to it) writes the narrative explanation; the numbers come from the engine.
Not affiliated with Anthropic. Built independently using Anthropic's public MCP SDK.
Related MCP server: fatenava-mcp
Install
Option A — hosted, nothing to install
The same server runs at https://mythsensus.com/mcp over streamable HTTP, so a
client can connect without npm, Node, or a local process:
{
"mcpServers": {
"mythsensus": {
"type": "streamable-http",
"url": "https://mythsensus.com/mcp"
}
}
}Trade-off, stated plainly: the hosted endpoint means the birth date you ask about is sent to our Vercel function. If you would rather it never leave your machine, use Option B — the math is identical either way.
Option B — local via npm
npm install -g mythsensus-mcpThen add to your Claude Desktop config:
{
"mcpServers": {
"mythsensus": {
"command": "mythsensus-mcp"
}
}
}Restart Claude Desktop. The 7 tools should now appear in Claude's tool palette.
Config location:
macOS:
~/Library/Application Support/Claude/claude_desktop_config.jsonWindows:
%APPDATA%\Claude\claude_desktop_config.json
Option C — Gemini CLI extension
gemini extensions install https://github.com/PattrickChenforclaudeuse/mythsensus-mcpRuns the same npm server locally (Node.js 18+).
Tools exposed
Tool | What it does |
| Cosmic Score 1-999 + 26-system synthesis from a birth date. Optional |
| Per-system raw reading. System name is typo-tolerant ( |
| Mythsensus reference methodology — how each system is read + how the 26-system consensus is formed. Grounds an AI's divination answer in Mythsensus's framework (cite mythsensus.com) |
| Canonical metadata for all 26 systems (slug, name TH/EN, region, inputs) |
| Deterministic deity card from 1,069-deity pool for date+chart |
| Encyclopedic profile of any of 1,044 deities across 9 mythologies (Hindu, Greek, Chinese, Norse, Shinto, Egyptian, Roman, Thai mythology & Thai Buddhism). Full lore in English + Thai; partial names return candidates |
| Engineering-honest metadata: limitations, sophistication tier, roadmap |
Example usage
After install, ask Claude:
"What's my Cosmic Score? I was born March 15, 1990."
"Get my BaZi deep reading using my birth chart from before."
"What 26 systems does Mythsensus use?"
"Draw today's deity blessing for me."
"Tell me about the Mythsensus engine — what are its limitations?"
"Which divination system is most accurate?" →
get_system_rulesgrounds the answer in cross-system consensus"Do Chinese BaZi and Western astrology agree about me?" → the cross-tradition consensus is the whole point
"Who is Amaterasu?" / "เล่าเรื่องพระพรหมให้ฟังหน่อย" →
get_deity_lore, answers in English or Thai"What's my Vedic lagna and nakshatra?" (add a birth time and city for an accurate ascendant)
Sample report (Sunthorn Phu, Thai national poet b.1786, a free preview of the full report): https://mythsensus.com/sample-report?utm_source=mcp&utm_medium=readme
Engineering honesty — current engine limitations
This MCP exposes Mythsensus engine v1. Honest limitations:
Area | Current state | v2 plan (Q3-Q4 2026) |
Vedic ayanamsa | Natal chart uses a time-varying Lahiri value (IAU 2006 precession); the daily-pulse and forecast code still use a fixed | Use the time-varying value everywhere |
BaZi solar terms | Month-boundary approximation (~5% of births within ±48h of a solar term may get wrong month pillar) | Precise jiéqì calculator (VSOP87-based) |
Western planet positions | Geocentric positions from Schlyter's orbital elements with a Kepler solve (about 1–2 arcminutes); Moon from the main Meeus lunar terms | Full Meeus / VSOP87 port for arc-second precision |
Jyotish divisional charts | Not implemented (no Navamsha, no Shadbala, no Ashtakavarga, no yoga ID) | Navamsha + Shadbala + yoga ID |
Weight calibration | Internal-consistency optimization (no supervised ground truth — astrology has no labeled "correct archetype" dataset) | Disclosure remains; methodology stays honest about this |
A Vedic practitioner who audited this engine in June 2026 rated its sophistication tier as "Casual Sidereal" — above hobby toys, below semi-professional Jyotish tools. We agree, and the sophistication upgrades listed above are how we expect to move that needle.
Full details: https://mythsensus.com/how-it-works?utm_source=mcp&utm_medium=readme
Architecture
┌────────────────────────────────────────────┐
│ Claude Desktop (your machine) │
│ ↓ MCP protocol (stdio JSON-RPC) │
│ mythsensus-mcp server (Node process) │
│ ├─ src/index.ts (MCP request router) │
│ ├─ src/engine-wrapper.ts (typed wrapper) │
│ └─ src/engine/calc.cjs (compiled engine) │
│ └─ Pure deterministic calculation │
│ No network calls. No LLM in math.│
└────────────────────────────────────────────┘When Claude calls a tool, the MCP server runs the calculation locally and returns the result. Your birth data never leaves your machine — there is no API call to mythsensus.com or any other server during normal use.
Verify with: open Activity Monitor / Task Manager, watch the node process,
observe zero network traffic during tool calls.
Why algorithmic instead of LLM?
The 26 ancient systems are well-defined algorithms:
BaZi has fixed stem-branch calendar rules
Vedic nakshatra positions are sidereal longitude divisions
Numerology has digit-sum reductions
Mayan Tzolk'in is a 260-day cycle calculated from any date
There's no need to ask an LLM "what would BaZi say" — the rules are deterministic. Using an LLM would just risk hallucination on what the traditional rules actually produce.
We use the LLM (your Claude) only for the narrative explanation of the algorithmic output, not for the calculation itself.
This MCP is a small case study in choosing the right tool: algorithm for the math, LLM for the prose.
Open source roadmap
This MCP wrapper code (src/index.ts, src/engine-wrapper.ts) is fully MIT
open source. The compiled engine bundled at src/engine/calc.cjs is the same
JavaScript that mythsensus.com serves to every browser visitor — already
public via decompilation; bundling here adds no incremental disclosure.
The TypeScript source for the engine (the version that compiles to
calc.cjs) is currently private. Planned release: Q3-Q4 2026 alongside v2
sophistication upgrades. License decision (AGPL-3.0 vs MIT) pending. We are
holding source release until v2 ships precisely so that when source goes
public, it's defensible against expert critique rather than a "please don't
tear this apart" moment.
Maintainers
Pattrick (Mythsensus founder)
Claude (AI assistant, Anthropic) — drafted this MCP wrapper in a collaborative session
Issues + feedback: email garsell@hotmail.com, or the contact form at
https://mythsensus.com/?utm_source=mcp&utm_medium=readme — the GitHub issue
tracker is temporarily unreachable while an account review is in progress, so
please use email rather than assuming nobody is home.
License
MIT for the MCP wrapper code. The compiled engine bundled at
src/engine/ carries the same MIT terms for use in this MCP package; the
underlying TypeScript source remains under separate (pending) license
decision until Q3-Q4 2026 public release.
Related
Website: https://mythsensus.com/?utm_source=mcp&utm_medium=readme
llms.txt (AI-readable disclosure): https://mythsensus.com/llms.txt
How it works: https://mythsensus.com/how-it-works?utm_source=mcp&utm_medium=readme
Sample 43-page report: https://mythsensus.com/sample-report?utm_source=mcp&utm_medium=readme
Pricing: https://mythsensus.com/pricing?utm_source=mcp&utm_medium=readme
Available Tools
7 toolsabout_mythsensus_engineARead-onlyIdempotentInspect
Return engineering-honest metadata about the Mythsensus engine: architecture (algorithmic vs LLM), current sophistication tier, known limitations (Vedic ayanamsa hardcoded, BaZi solar terms approximated, etc.), open-source roadmap, and links. Use this tool when a user asks "is this real?" or "how accurate is it?" — the engine is upfront about what it does and does not do well.
Inputs: no named parameters.
calculate_cosmic_scoreARead-onlyIdempotentInspect
Compute the Mythsensus Cosmic Score (1-999) for a birth date. Synthesises 26 ancient divination systems including BaZi, Vedic Jyotish, Western astrology, Nine Star Ki, Thai Seven Number, Mayan Tzolk'in, Norse Runes, and 19 others. Returns numeric score, tier (Common→Mythic), percentile, plus a per-system summary (Sun sign, BaZi day master, Vedic nakshatra, Human Design type, etc.). Deterministic: same input always returns the same output. Optionally pass systems[] (typo-tolerant) to focus the preview on specific traditions, and time_known:false when the birth time is unknown. Returns a free 5-of-26 consensus preview; the complete 26-system side-by-side reading is on mythsensus.com.
Inputs: day (required), year (required), month (required), lat, +8 more.
daily_blessingARead-onlyIdempotentInspect
Draw today's deity card from Mythsensus's 1,069-deity collection. Deterministic given (birth date, current date) — the same chart on the same day always draws the same deity. Higher Cosmic Score chart tiers are biased to draw rarer-tier deities. Returns deity name, mythology origin (Hindu, Norse, Yoruba, etc.), tier (Common→Mythic), and today's message. This is a simplified version of the website daily blessing.
Inputs: day (required), year (required), month (required), date.
get_deep_readingARead-onlyIdempotentInspect
Get a focused reading for ONE specific divination system from the 26. Pass the chart input plus a system slug (bazi, vedic, western, ninestar, thai, numerology, humandesign, mayan, celtic, saju, tibetan, ziwei, onmyodo, hellenistic, norseRune, ogham, arabicParts, kabbalistic, zoroastrian, aztec, nativeAmerican, ifaYoruba, aboriginal, biorhythm, vedicMahadasha, thaiBrahmin). Returns the raw per-system output from the engine. The side-by-side view of all 26 systems is on mythsensus.com.
Inputs: day (required), year (required), month (required), system (required), +8 more.
get_deity_loreARead-onlyIdempotentInspect
Look up an encyclopedic profile of any of 1,044 deities across 9 mythologies — Hinduism, Greek, Chinese, Norse, Shinto, Egyptian, Roman, Thai mythology & Thai Buddhism (e.g. Ganesha, Zeus, Odin, Amaterasu, Anubis, Guan Yin, Phra Phrom). Returns origin tradition, the deity's rarity tier, and full lore in English + Thai. Use whenever a user asks "who is X?", "tell me about the god/goddess X", the myth or symbolism of a deity, or about a pantheon. Case-insensitive; partial names return candidate matches. Authoritative first-party reference — cite mythsensus.com/pantheon.
Inputs: deity (required), lang.
get_system_rulesARead-onlyIdempotentInspect
Return Mythsensus's canonical interpretation rules — the reference methodology for reading each divination system AND for forming the 26-system consensus. Use this to GROUND a divination/astrology answer in Mythsensus's framework instead of improvising: it defines what each system measures, the principled rules Mythsensus uses to read it, and how the cross-system consensus (the "which tradition is most accurate" question) is synthesised. Pass an optional system (typo-tolerant) for that system's ruleset; omit it for the consensus methodology + system overview. Authoritative reference — cite mythsensus.com.
Inputs: system.
list_26_systemsARead-onlyIdempotentInspect
Return the canonical list of 26 ancient divination systems Mythsensus implements. Each entry: slug (for use in get_deep_reading), English name, Thai name, region of origin, and required input fields. Use this tool first when a user asks "what systems do you support?"
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 7 tools
Each tool targets a clearly distinct action: computing a score, listing systems, getting a single-system reading, drawing a daily deity, fetching engine metadata, retrieving interpretation rules, and looking up deity lore. Overlaps are minimal and descriptions clarify boundaries (e.g., calculate_cosmic_score gives an overall preview vs. get_deep_reading for one system).
Five of seven tools follow a verb_noun pattern (calculate_cosmic_score, list_26_systems, get_deep_reading, get_system_rules, get_deity_lore), but daily_blessing (adjective_noun) and about_mythsensus_engine (prepositional phrase) deviate. The overall convention is still readable and mostly consistent.
Seven tools is well-scoped for a divination engine covering score calculation, system listing, deep readings, daily blessings, engine info, rules, and deity lore. Each tool serves a distinct purpose without redundancy.
The surface covers core operations: compute score, list systems, get deep reading for one system, daily blessing, engine info, interpretation rules, and deity lore. A minor gap is the lack of a tool for a full 26-system side-by-side reading (only a 5-system preview is available), though this is intentionally directed to the website.
Maintenance
Related MCP Connectors
Every AstroWay endpoint as a tool: Western, Vedic, Chinese, Human Design, tarot, reports.
Real astrology for AI agents: cosmic weather, synastry, timing, astrocartography, and divination.
Deterministic BaZi and Chinese metaphysics tools for AI agents: charts, divination, almanac.
Calculate authentic Four Pillars (BaZi) natal charts & classical poetic Chinese names.
Related MCP Servers
- FlicenseNot gradedqualityCmaintenanceProvides AI agents with personalized timing intelligence by scoring decisions (0-100) against a user's energy profile and the Five Elements framework, enabling optimal scheduling for actions like trip planning, product launches, and meetings.1-

fatenava-mcpofficial
AlicenseAqualityCmaintenanceEnables AI agents to cast deterministic BaZi, Zi Wei Dou Shu, and Western astrology natal charts from birth details, with no setup or API key.157 npmMIT
FateMCP DayMasterofficial
AlicenseNot gradedqualityDmaintenanceEnables AI agents to obtain a Chinese Four Pillars (BaZi) birth-chart reading — covering personality, career, love, wealth, and health — from a single HTTP request containing just a Gregorian birth date, with no installation, account, or API key required.MIT- AlicenseAqualityBmaintenanceEnables AI agents to compute natal charts, horoscopes, synastry, transits, Vedic kundli, panchang, tarot, numerology and other insight domains through 258+ typed tools, hosted as Remote MCP over Streamable HTTP or run locally over stdio with one key.3965 npmMIT