_ registry / mcp streamable-http · checked 1h ago

mythsensus

https://mythsensus.com

Registry code: 76ed7f059ec4d8e8

api record

MCP server exposing the Mythsensus engine — calculate Cosmic Score across 26 ancient divination algorithms (BaZi, Vedic, Western, Nine Star Ki, Mayan, Norse Runes, Thai Seven Number, and more) deterministically, client-side, from a birth date.

from a public catalogue that lists it, not from the operator

endpoint
https://mythsensus.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mythsensus live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is mythsensus free to use?
Yes — the hub reached it with no key and no payment.
What tools does mythsensus have?
7 tools: calculate_cosmic_score, daily_blessing, get_deity_lore, get_deep_reading, list_26_systems, about_mythsensus_engine, get_system_rules.
Is mythsensus safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.8%

90 days 99.5%· all time 99.5%

latency
324ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 640 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
_ what it is for
topic
lifestyle & home
used for
  • calculate a divination score from a birth date
  • draw a daily deity card
  • look up deity lore
takes → gives
data → text, data
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
5 open 2 never probed 5 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_deity_lore reads open 7h ago

    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.

    mcp-tool

    {
  "type": "object",
  "required": [
    "deity"
  ],
  "properties": {
    "lang": {
      "enum": [
        "th",
        "en"
      ],
      "type": "string",
      "description": "Output language (optional; omit to get BOTH English and Thai)."
    },
    "deity": {
      "type": "string",
      "description": "Deity name or partial (e.g. \"Ganesha\", \"amaterasu\", \"thor\"). Case-insensitive; partial matches return candidates."
    }
  }
}
    arguments 20 lines
  • get_deep_reading reads open 13h ago

    Get a focused reading for ONE specific divination system from the 26. This MCP covers the 5 preview systems (bazi, vedic, western, ninestar, thai); the other 21 are on mythsensus.com.

    mcp-tool

    {
  "type": "object",
  "required": [
    "year",
    "month",
    "day",
    "system"
  ],
  "properties": {
    "day": {
      "type": "integer",
      "maximum": 31,
      "minimum": 1
    },
    "lat": {
      "type": "number"
    },
    "lon": {
      "type": "number"
    },
    "hour": {
      "type": "integer",
      "maximum": 23,
      "minimum": 0
    },
    "lang": {
      "enum": [
        "th",
        "en"
      ],
      "type": "string"
    },
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 1500
    },
    "month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1
    },
    "minute": {
      "type": "integer",
      "maximum": 59,
      "minimum": 0
    },
    "system": {
      "type": "string",
      "description": "System slug — see list_26_systems"
    },
    "timezone": {
      "type": "number"
    }
  }
}
    arguments 56 lines
  • list_26_systems reads open 23h ago

    Return the canonical list of 26 ancient divination systems Mythsensus implements (slug, English + Thai name, region, required inputs). Use first when asked "what systems do you support?".

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • about_mythsensus_engine reads open 23h ago

    Engineering-honest metadata about the Mythsensus engine: architecture (algorithmic vs LLM), known limitations, open-source roadmap, links. Use when a user asks "is this real?" / "how accurate is it?".

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_system_rules reads open 23h ago

    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.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "system": {
      "type": "string",
      "description": "Optional system slug (typo-tolerant). Omit for the consensus methodology + a one-line overview of all 26 systems."
    }
  }
}
    arguments 9 lines
  • calculate_cosmic_score reads unknown 13h ago

    Compute the Mythsensus Cosmic Score (1–1,000) 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, band (Dawn→Divine), percentile, plus a 5-of-26 per-system consensus preview. Deterministic: same input always returns the same output.

    mcp-tool

    {
  "type": "object",
  "required": [
    "year",
    "month",
    "day"
  ],
  "properties": {
    "day": {
      "type": "integer",
      "maximum": 31,
      "minimum": 1,
      "description": "Birth day (1-31)"
    },
    "lat": {
      "type": "number",
      "description": "Birth latitude (optional; default 13.75 = Bangkok)"
    },
    "lon": {
      "type": "number",
      "description": "Birth longitude (optional; default 100.5 = Bangkok)"
    },
    "hour": {
      "type": "integer",
      "maximum": 23,
      "minimum": 0,
      "description": "Birth hour (0-23, optional — improves BaZi/Vedic/Western precision; default 12 noon)"
    },
    "lang": {
      "enum": [
        "th",
        "en"
      ],
      "type": "string",
      "description": "Output language (optional; default th)"
    },
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 1500,
      "description": "Birth year (4-digit, e.g. 1990)"
    },
    "month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1,
      "description": "Birth month (1-12)"
    },
    "minute": {
      "type": "integer",
      "maximum": 59,
      "minimum": 0,
      "description": "Birth minute (0-59, optional; default 0)"
    },
    "timezone": {
      "type": "number",
      "description": "Timezone offset hours (optional; default +7)"
    }
  }
}
    arguments 60 lines
  • daily_blessing reads unknown 13h ago

    Draw today's deity card from Mythsensus's 1,069-deity collection. Deterministic given (birth date, current date). Higher Cosmic Score tiers bias toward rarer deities. Returns deity, mythology origin, tier, and message.

    mcp-tool

    {
  "type": "object",
  "required": [
    "year",
    "month",
    "day"
  ],
  "properties": {
    "day": {
      "type": "integer",
      "maximum": 31,
      "minimum": 1
    },
    "date": {
      "type": "string",
      "description": "Date to draw for, YYYY-MM-DD (optional; default today)"
    },
    "year": {
      "type": "integer",
      "maximum": 2100,
      "minimum": 1500
    },
    "month": {
      "type": "integer",
      "maximum": 12,
      "minimum": 1
    }
  }
}
    arguments 29 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 76ed7f059ec4d8e8.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/76ed7f059ec4d8e8/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/76ed7f059ec4d8e8/badge.svg)](https://brick.blue/agent/76ed7f059ec4d8e8?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.