Mythsensus Mcp

What is Mythsensus MCP?

An MCP server that bundles the Mythsensus engine — 26 ancient divination algorithms — as tools for Claude Desktop and any MCP‑compatible AI client. All calculations run locally in the Node process; no birth data is sent to any server.

How to use Mythsensus MCP?

Install globally with npm install -g mythsensus-mcp, then add "mythssensus": { "command": "mythssensus-mcp" } to Claude Desktop’s claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/claude_desktop_config.json; Windows: %APPDATA%\Claude\claude_desktop_config.json). Restart Claude Desktop and ask questions like “What’s my Cosmic Score? I was born March 15, 1990.” to invoke the tools.

Key features of Mythsensus MCP

• Exposes 6 deterministic divination tools
• Computation runs entirely offline on your machine
• 26 systems: BaZi, Vedic, Numerology, Mayan Tzolk’in, etc.
• Typo‑tolerant system names for deep readings
• Deterministic 1,069‑deity daily blessing
• Engineering‑honest metadata with known limitations

Use cases of Mythsensus MCP

• Get a Cosmic Score (1–999) with 26‑system synthesis from a birth date
• Obtain per‑system raw readings (e.g., BaZi, Vedic nakshatra) without external API calls
• Ask Claude to explain how Mythsensus cross‑references systems using the get_system_rules tool
• Draw a daily deity blessing determined by date and birth chart
• Explore the engine’s methodology, limitations, and roadmap through about_mythssensus_engine

FAQ from Mythsensus MCP

Do my birth data leave my machine?

No. All calculations happen locally in the Node process; there are no network calls to mythsensus.com or any server during normal tool use. Even city names are resolved offline from a bundled table.

What tools does Mythsensus MCP expose?

Six tools: calculate_cosmic_score, get_deep_reading, get_system_rules, list_26_systems, daily_blessing, and about_mythssensus_engine. Full details are in the tools table in the README.

What are the current engine limitations?

Vedic ayanamsa uses a hardcoded Lahiri offset (accurate ±10 arcmin for 2020–2030 births). BaZi month pillars may be wrong for ~5% of births within ±48h of a solar term. Outer planet positions have arc‑minute drift. Jyotish divisional charts are not implemented. Weight calibration is internal‑consistency based, not supervised.

Why is the engine algorithmic instead of LLM‑based?

The 26 systems are deterministic algorithms (e.g., BaZi stem‑branch rules, nakshatra divisions, numerology sums). Using an LLM for the math would risk hallucination; the LLM is only used for narrative explanation of the algorithmic output.

Is Mythsensus MCP affiliated with Anthropic?

No. It is independently built using Anthropic’s public MCP SDK.