{
  "markdown": "# Mythsensus MCP\n\n[![npm version](https://img.shields.io/npm/v/mythsensus-mcp?color=cb3837&logo=npm)](https://www.npmjs.com/package/mythsensus-mcp)\n[![npm downloads](https://img.shields.io/npm/dm/mythsensus-mcp?color=cb3837&logo=npm)](https://www.npmjs.com/package/mythsensus-mcp)\n[![license: MIT](https://img.shields.io/npm/l/mythsensus-mcp?color=blue)](./LICENSE)\n[![Glama score](https://glama.ai/mcp/servers/PattrickChenforclaudeuse/mythsensus-mcp/badges/score.svg)](https://glama.ai/mcp/servers/PattrickChenforclaudeuse/mythsensus-mcp)\n\n> An MCP (Model Context Protocol) server that exposes the Mythsensus engine —\n> 26 ancient divination algorithms implemented in TypeScript — as tools your\n> Claude Desktop (or any MCP-compatible AI client) can call.\n\n```\nYou: \"What's my Cosmic Score? I was born March 15, 1990.\"\nClaude: [calls calculate_cosmic_score({year:1990, month:3, day:15})]\nClaude: \"Your Cosmic Score is 770/1000 — 'Balance' tier, top 33%.\n         Sun in Pisces. BaZi day master is Yin Earth. Life Path 1.\n         Mayan Kin 163 (Akbal). Human Design: Generator...\"\n```\n\n## What this is (and isn't)\n\n**This is** a Model Context Protocol server that bundles the compiled Mythsensus\nengine (1.1 MB JavaScript, plus a 2.8 MB deity encyclopedia) and exposes 7 tools\nClaude can invoke. Installed via npm, the math runs locally in this Node process\n— no birth data sent to any server (city names are resolved offline from a\nbundled table, too).\n\n**This is not** an LLM wrapper. The 26 divination systems are implemented as\ndeterministic algorithms. Same input, same output, every time. The LLM (your\nClaude itself, when you talk to it) writes the narrative explanation; the\nnumbers come from the engine.\n\n**Not affiliated with Anthropic.** Built independently using Anthropic's\npublic MCP SDK.\n\n## Install\n\n### Option A — hosted, nothing to install\n\nThe same server runs at `https://mythsensus.com/mcp` over streamable HTTP, so a\nclient can connect without npm, Node, or a local process:\n\n```json\n{\n  \"mcpServers\": {\n    \"mythsensus\": {\n      \"type\": \"streamable-http\",\n      \"url\": \"https://mythsensus.com/mcp\"\n    }\n  }\n}\n```\n\nTrade-off, stated plainly: the hosted endpoint means the birth date you ask\nabout is sent to our Vercel function. If you would rather it never leave your\nmachine, use Option B — the math is identical either way.\n\n### Option B — local via npm\n\n```bash\nnpm install -g mythsensus-mcp\n```\n\nThen add to your Claude Desktop config:\n\n```json\n{\n  \"mcpServers\": {\n    \"mythsensus\": {\n      \"command\": \"mythsensus-mcp\"\n    }\n  }\n}\n```\n\nRestart Claude Desktop. The 7 tools should now appear in Claude's tool\npalette.\n\nConfig location:\n- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`\n- **Windows**: `%APPDATA%\\Claude\\claude_desktop_config.json`\n\n## Tools exposed\n\n| Tool | What it does |\n|---|---|\n| `calculate_cosmic_score` | Cosmic Score 1-999 + 26-system synthesis from a birth date. Optional `systems[]` (focus the preview), `time_known` (honest unknown-birth-time handling), `location` (city name or `lat,lon`, resolved **offline**) |\n| `get_deep_reading` | Per-system raw reading. System name is **typo-tolerant** (`\"vedik\"`→vedic, `\"four pillars\"`→bazi) |\n| `get_system_rules` | 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) |\n| `list_26_systems` | Canonical metadata for all 26 systems (slug, name TH/EN, region, inputs) |\n| `daily_blessing` | Deterministic deity card from 1,069-deity pool for date+chart |\n| `get_deity_lore` | 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 |\n| `about_mythsensus_engine` | Engineering-honest metadata: limitations, sophistication tier, roadmap |\n\n## Example usage\n\nAfter install, ask Claude:\n\n- *\"What's my Cosmic Score? I was born March 15, 1990.\"*\n- *\"Get my BaZi deep reading using my birth chart from before.\"*\n- *\"What 26 systems does Mythsensus use?\"*\n- *\"Draw today's deity blessing for me.\"*\n- *\"Tell me about the Mythsensus engine — what are its limitations?\"*\n- *\"Which divination system is most accurate?\"* → `get_system_rules` grounds the answer in cross-system consensus\n- *\"Do Chinese BaZi and Western astrology agree about me?\"* → the cross-tradition consensus is the whole point\n- *\"Who is Amaterasu?\"* / *\"เล่าเรื่องพระพรหมให้ฟังหน่อย\"* → `get_deity_lore`, answers in English or Thai\n- *\"What's my Vedic lagna and nakshatra?\"* (add a birth time and city for an accurate ascendant)\n\nSample report (Sunthorn Phu, Thai national poet b.1786, free preview of the\n$19 product): https://mythsensus.com/sample-report?utm_source=mcp&utm_medium=readme\n\n## Engineering honesty — current engine limitations\n\nThis MCP exposes Mythsensus engine **v1**. Honest limitations:\n\n| Area | Current state | v2 plan (Q3-Q4 2026) |\n|---|---|---|\n| **Vedic ayanamsa** | Lahiri hardcoded at `24.0°` (accurate ±10 arcmin for births 2020-2030) | Time-varying `lahiriAyanamsa(y,m,d)` formula |\n| **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) |\n| **Western planet positions** | Custom trigonometric series (good for Sun + Mercury/Venus, arc-minute drift on outer planets) | Jean Meeus astronomical algorithms port |\n| **Jyotish divisional charts** | Not implemented (no Navamsha, no Shadbala, no Ashtakavarga, no yoga ID) | Navamsha + Shadbala + yoga ID |\n| **Weight calibration** | Internal-consistency optimization (no supervised ground truth — astrology has no labeled \"correct archetype\" dataset) | Disclosure remains; methodology stays honest about this |\n\nA Vedic practitioner who audited this engine in June 2026 rated its\nsophistication tier as **\"Casual Sidereal\"** — above hobby toys, below\nsemi-professional Jyotish tools. We agree, and the sophistication upgrades\nlisted above are how we expect to move that needle.\n\nFull details: https://mythsensus.com/how-it-works?utm_source=mcp&utm_medium=readme\n\n## Architecture\n\n```\n┌────────────────────────────────────────────┐\n│ Claude Desktop (your machine)              │\n│   ↓ MCP protocol (stdio JSON-RPC)          │\n│ mythsensus-mcp server (Node process)       │\n│   ├─ src/index.ts (MCP request router)     │\n│   ├─ src/engine-wrapper.ts (typed wrapper) │\n│   └─ src/engine/calc.cjs (compiled engine)  │\n│       └─ Pure deterministic calculation    │\n│           No network calls. No LLM in math.│\n└────────────────────────────────────────────┘\n```\n\nWhen Claude calls a tool, the MCP server runs the calculation locally and\nreturns the result. Your birth data never leaves your machine — there is\nno API call to mythsensus.com or any other server during normal use.\n\nVerify with: open Activity Monitor / Task Manager, watch the `node` process,\nobserve zero network traffic during tool calls.\n\n## Why algorithmic instead of LLM?\n\nThe 26 ancient systems are well-defined algorithms:\n- BaZi has fixed stem-branch calendar rules\n- Vedic nakshatra positions are sidereal longitude divisions\n- Numerology has digit-sum reductions\n- Mayan Tzolk'in is a 260-day cycle calculated from any date\n\nThere's no need to ask an LLM \"what would BaZi say\" — the rules are\ndeterministic. Using an LLM would just risk hallucination on what the\ntraditional rules actually produce.\n\nWe use the LLM (your Claude) only for the **narrative explanation** of the\nalgorithmic output, not for the calculation itself.\n\nThis MCP is a small case study in choosing the right tool: algorithm for the\nmath, LLM for the prose.\n\n## Open source roadmap\n\nThis MCP wrapper code (`src/index.ts`, `src/engine-wrapper.ts`) is fully MIT\nopen source. The compiled engine bundled at `src/engine/calc.cjs` is the same\nJavaScript that mythsensus.com serves to every browser visitor — already\npublic via decompilation; bundling here adds no incremental disclosure.\n\nThe **TypeScript source** for the engine (the version that compiles to\n`calc.cjs`) is currently private. Planned release: Q3-Q4 2026 alongside v2\nsophistication upgrades. License decision (AGPL-3.0 vs MIT) pending. We are\nholding source release until v2 ships precisely so that when source goes\npublic, it's defensible against expert critique rather than a \"please don't\ntear this apart\" moment.\n\n## Maintainers\n\n- Pattrick (Mythsensus founder)\n- Claude (AI assistant, Anthropic) — drafted this MCP wrapper in a\n  collaborative session\n\nIssues + feedback: email `garsell@hotmail.com`, or the contact form at\nhttps://mythsensus.com/?utm_source=mcp&utm_medium=readme — the GitHub issue\ntracker is temporarily unreachable while an account review is in progress, so\nplease use email rather than assuming nobody is home.\n\n## License\n\n**MIT** for the MCP wrapper code. The compiled engine bundled at\n`src/engine/` carries the same MIT terms for use in this MCP package; the\nunderlying TypeScript source remains under separate (pending) license\ndecision until Q3-Q4 2026 public release.\n\n## Related\n\n- Website: https://mythsensus.com/?utm_source=mcp&utm_medium=readme\n- llms.txt (AI-readable disclosure): https://mythsensus.com/llms.txt\n- How it works: https://mythsensus.com/how-it-works?utm_source=mcp&utm_medium=readme\n- Sample 43-page report: https://mythsensus.com/sample-report?utm_source=mcp&utm_medium=readme\n- Pricing: https://mythsensus.com/pricing?utm_source=mcp&utm_medium=readme\n",
  "bytes": 9574,
  "sha": "277bd7fe6a3c661d4d77ac565ee526194ca4ece46fe7610ff6c7d20f9c59b868",
  "repo_slug": "pattrickchenforclaudeuse/mythsensus-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_mythsensus_mythsensus_mcp_d20a253c/readme"
}