Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.mythsensus/mythsensus-mcp

NPM · MYTHSENSUS-MCP · 2 COMPONENTS

Cosmic Score from 26 divination systems: the consensus when traditions disagree about you.

0 this week 81 Trust /100

Last scanned (14 hours ago)

Scores higher than 69% of npm servers

Category Entertainment and Games

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1534 tokens (~219/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 16 Nov 26 0
    • Stability: 0.97 → pass security
    • Package version: 0.3.11 → 0.3.17 functional
  • 15 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Nov 26 0
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Tool coverage: 100 → unverified ▼ functional
    • Capabilities: pass → unverified ▼ functional
    • Package version: 0.3.11 → 0.3.17 functional
  • 9 Nov 26 +6
    • Source repository: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 6 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 17 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Analysed npm/mythsensus-mcp@0.3.17

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 92 packages
Packages resolved 92
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~1,534 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
about_mythsensus_engine ~99

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

calculate_cosmic_score ~512

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.

NameTypeReqDescription
dayintegeryesBirth day (1-31)
hourinteger–Birth hour (0-23, optional — improves BaZi/Vedic/Western precision; default 12 noon)
langstring–Output language (optional; default th)
latnumber–Birth latitude (optional; default 13.75 = Bangkok)
locationstring–Optional birthplace — a city name ("Chiang Mai", "เชียงใหม่", "Tokyo") or "lat,lon". Typo-tolerant, resolved offline to coordinates + timezone (no network). Explicit lat/lon/timezone override it.
lonnumber–Birth longitude (optional; default 100.5 = Bangkok)
minuteinteger–Birth minute (0-59, optional; default 0)
monthintegeryesBirth month (1-12)
systemsarray–Optional — limit the consensus preview to specific systems. Free preview covers bazi/vedic/western/ninestar/thai; names are typo-tolerant ("vedik"→vedic, "four pillars"→bazi). Requests beyond the fre…
time_knownboolean–Set false when birth time is unknown — time-dependent layers (BaZi hour pillar, Ascendant/houses) are then flagged approximate. Default: inferred from whether hour is provided.
timezonenumber–Timezone offset hours (optional; default +7)
yearintegeryesBirth year (4-digit, e.g. 1990)

No output schema declared.

No examples provided.

daily_blessing ~149

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.

NameTypeReqDescription
datestring–Date to draw for, YYYY-MM-DD (optional; defaults to today)
dayintegeryes–
monthintegeryes–
yearintegeryes–

No output schema declared.

No examples provided.

get_deep_reading ~328

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.

NameTypeReqDescription
dayintegeryes–
hourinteger––
langstring––
latnumber––
locationstring–Optional birthplace — city name (typo-tolerant, Thai or English) or "lat,lon", resolved offline. Explicit lat/lon override it.
lonnumber––
minuteinteger––
monthintegeryes–
systemstringyesSystem slug (typo-tolerant — common aliases and small misspellings auto-correct, e.g. "vedik"→vedic). See list_26_systems for canonical slugs.
time_knownboolean–Set false when birth time is unknown (default: inferred from whether hour is provided).
timezonenumber––
yearintegeryes–

No output schema declared.

No examples provided.

get_deity_lore ~206

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.

NameTypeReqDescription
deitystringyesDeity name or partial (e.g. "Ganesha", "amaterasu", "thor").
langstring–Output language (optional; omit to get BOTH English and Thai).

No output schema declared.

No examples provided.

get_system_rules ~169

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.

NameTypeReqDescription
systemstring–Optional system slug (typo-tolerant). Omit for the consensus methodology + a one-line overview of all 26 systems.

No output schema declared.

No examples provided.

list_26_systems ~71

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?"

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the com.mythsensus/mythsensus-mcp server?

com.mythsensus/mythsensus-mcp runs locally as an npm package, launched with npx -y mythsensus-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · mythsensus-mcp

# add to Claude Code
claude mcp add com-mythsensus-mythsensus-mcp -- npx -y mythsensus-mcp
Common questions

What is the com.mythsensus/mythsensus-mcp server?

com.mythsensus/mythsensus-mcp is listed in the public MCP registry as com.mythsensus/mythsensus-mcp. Cosmic Score from 26 divination systems: the consensus when traditions disagree about you. This page covers its npm package (mythsensus-mcp).

Is the com.mythsensus/mythsensus-mcp server safe to use?

com.mythsensus/mythsensus-mcp scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.mythsensus/mythsensus-mcp server expose?

com.mythsensus/mythsensus-mcp exposes 7 tools: calculate_cosmic_score, get_deep_reading, list_26_systems, daily_blessing, about_mythsensus_engine, and 2 more. Their descriptions and schemas cost roughly 1,534 tokens of context every time the server is loaded.

Is the com.mythsensus/mythsensus-mcp server still maintained?

com.mythsensus/mythsensus-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the com.mythsensus/mythsensus-mcp server under?

com.mythsensus/mythsensus-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the com.mythsensus/mythsensus-mcp server?

VerifyMCP ran 16 checks on com.mythsensus/mythsensus-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.