Skip to main content
Glama
565,283 tools. Updated 2026-09-13 23:18

"A server for analyzing horoscopes and fortune based on zodiac signs" matching MCP tools:

  • Get the complete list of 12 rashis (zodiac signs) in Vedic astrology. Returns Sanskrit names, Western equivalents, sidereal date ranges, symbols, governing Adityas, and personality characteristics for each rashi. Reference data for Mesha through Meen. Essential for zodiac sign lookup tables, astrology apps, and rashi-based UI components.
    ConnectorNo auth
  • Get healing crystals and gemstones associated with a specific zodiac sign. Returns summary data for each crystal. Use the /crystals/{id} detail endpoint for full healing properties. Supports all 12 zodiac signs from Aries through Pisces. Perfect for personalized crystal recommendations based on astrological birth chart data.
    ConnectorNo auth
  • Recommends crystals from a Vedic natal chart using house lordship rules for gem selection. This is the only API that derives crystal recommendations from a computed natal chart — not from zodiac sign or chakra preference. WORKFLOW: BEFORE: None — this tool internally computes the natal chart. No separate natal chart call required. AFTER: asterwise_get_crystal — get full detail (hardness, origins, affirmation, full caution text) on any recommended crystal by slug. AFTER: asterwise_get_remedies — broader classical remedial programme alongside gem recommendations. INPUT CONTRACT: Standard BirthData (date, time, lat, lon, timezone, ayanamsa). Defaults to Lahiri ayanamsa. time (required): Ascendant (Lagna) is time-sensitive. Inaccurate birth time changes the Lagna → changes all house lords → changes recommendations entirely. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — also a chart-based gem endpoint but uses a different engine (Atmakaraka + role-based prescription vs house lordship scoring); returns gem names not crystal database entries; does not include match_score or match_reasons. asterwise_get_crystal_recommendations — recommends crystals by zodiac sign, chakra, or intention keyword (no natal chart computation; Western metaphysical matching, not classical Jyotish). asterwise_get_crystal_by_planet — lists all crystals for a Vedic planet without house context — use this for reference, not prescription. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-recommendations-natal/
    ConnectorOAuth
  • Calculate positions of all 9 planets (Sun through Saturn, Rahu, Ketu) at regular time intervals with full KP hierarchy: sign lord, star lord, sublord, and sub-sublord. Returns longitude, zodiac sign, nakshatra, sublord, sub-sublord, and KP number (1-249) for each planet at each timestamp. Ideal for tracking planetary motion, finding optimal muhurta windows, analyzing transit patterns, and building KP ephemeris tables. Maximum range of 7 days with 15-minute to 24-hour intervals.
    ConnectorNo auth

Matching MCP Servers

  • F
    license
    Not graded
    quality
    C
    maintenance
    A read-only remote MCP server exposing Bazi chart calculation, Chinese almanac queries, and tarot card draws over Streamable HTTP, enabling AI hosts to incorporate these fortune-telling tools with structured, natural-language-friendly outputs.
    -
  • A
    license
    Not graded
    quality
    D
    maintenance
    Enables traditional Chinese fortune-telling through BaZi (Four Pillars) analysis, including solar/lunar date conversion, Five Element balance calculations, Ten Gods deduction, and destiny interpretation for metaphysics applications.
    34 npm
    MIT

Matching MCP Connectors

  • Korean saju fortune MCP: natal chart, today/daily/yearly luck, compatibility, and saved profiles.

  • BaZi (八字) MCP gateway + 玄学社区. 12 tools (4 fortune + 5 forum + 3 meta). x-api-key required.

  • Start a browser-based sign-in flow to get an API key for full access. Call this when you need detailed analysis results (reasoning, measurements) that require authentication. Returns a verification URL to show to the user. After the user signs in, poll check_device_auth with the returned user_code to get the API key. Returns: { "verification_url": str, "user_code": str, "expires_in": 600, "message": str }
    ConnectorNo auth
  • Recommends crystals from a Vedic natal chart using house lordship rules for gem selection. This is the only API that derives crystal recommendations from a computed natal chart — not from zodiac sign or chakra preference. WORKFLOW: BEFORE: None — this tool internally computes the natal chart. No separate natal chart call required. AFTER: asterwise_get_crystal — get full detail (hardness, origins, affirmation, full caution text) on any recommended crystal by slug. AFTER: asterwise_get_remedies — broader classical remedial programme alongside gem recommendations. INPUT CONTRACT: Standard BirthData (date, time, lat, lon, timezone, ayanamsa). Defaults to Lahiri ayanamsa. time (required): Ascendant (Lagna) is time-sensitive. Inaccurate birth time changes the Lagna → changes all house lords → changes recommendations entirely. DO NOT CONFUSE WITH: asterwise_get_gemstone_recommendations — also a chart-based gem endpoint but uses a different engine (Atmakaraka + role-based prescription vs house lordship scoring); returns gem names not crystal database entries; does not include match_score or match_reasons. asterwise_get_crystal_recommendations — recommends crystals by zodiac sign, chakra, or intention keyword (no natal chart computation; Western metaphysical matching, not classical Jyotish). asterwise_get_crystal_by_planet — lists all crystals for a Vedic planet without house context — use this for reference, not prescription. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-crystal-recommendations-natal/
    ConnectorOAuth
  • Today's universal sky: which planets are retrograde right now, the current moon phase and illumination, geocentric positions for 13 bodies (zodiac sign + Energy Blueprint gate/line), and a 30-day forward scan of retrograde stations and new/full moons. No input. Deterministic astronomy (JPL-validated ephemeris). Costs 1 call.
    ConnectorNo auth
  • What Caltrans changeable message signs are displaying right now. Data: statewide CMS sign text, blank and out-of-service signs already filtered - every record is a message a driver is physically seeing. Signs carry the road's operational truth ("CHAINS REQUIRED 10 MI AHEAD", "FULL CLOSURE HWY 96 DUE TO FIRE", "PREPARE TO STOP"), often before the event shows up in any other feed. Refresh: ~2-minute cache. Filters: route (e.g. "I-80") and/or center "lat,lon" with radius_km. Quote sign text verbatim to the user - it is the most current and most local signal this server has.
    ConnectorNo auth
  • Returns the exact string to sign, with the correct next nonce, for a free instant transfer between two ENROLLED accounts. Signs nothing and moves nothing — the sender signs the returned message, then POSTs {from,to,amount,nonce,signature} to /api/netting/transfer. BOTH parties must already be enrolled: Robyn will not hold a balance for a recipient who never consented, so to pay an unenrolled address use the ordinary non-custodial route instead.
    ConnectorNo auth
  • Render domain fortune cards (재물운·연애운·결혼운·직업운·건강운·학업운·이동운·재회운·총운). Pick only the domains the user asked about and write each card's text yourself. Compute chart facts server-side and render them in a widget card. Write the narrative/text fields yourself, grounded in a prior legend_saju_read_fortune call — the card labels them as AI interpretation. After the card renders, add only brief text the card does not already show.
    ConnectorNo auth
  • Fetch messages sent via aanet_send_message — the pull-based fallback for when you haven't registered a webhook on the message event. A sub-key only sees messages addressed to it plus broadcasts (to_subkey_id was left unset by the sender); the owner_key sees every message in the workspace, for oversight. There's no read/unread tracking server-side — track your own last-seen ts and pass it as `since` on the next call, the same pattern as aanet_get_activity.
    ConnectorNo auth
  • Fetch messages sent via aanet_send_message — the pull-based fallback for when you haven't registered a webhook on the message event. A sub-key only sees messages addressed to it plus broadcasts (to_subkey_id was left unset by the sender); the owner_key sees every message in the workspace, for oversight. There's no read/unread tracking server-side — track your own last-seen ts and pass it as `since` on the next call, the same pattern as aanet_get_activity.
    ConnectorNo auth
  • Calculate recommended RAM and ARC sizing for a ZFS storage pool based on workload type, pool size, deduplication status, and L2ARC cache size. Computes minimum and recommended RAM in gigabytes, ARC target size, and dedup table overhead. Accounts for workload-specific IO patterns: NAS (sequential, 1GB/TB), database (random, 2GB/TB), virtualization (mixed, 1.5GB/TB). Deduplication adds approximately 5GB per TB for the DDT. L2ARC index requires 1GB RAM per 10GB of L2ARC. Essential for TrueNAS, FreeNAS, and custom ZFS server builds.
    ConnectorNo auth
  • Estimate the cooling load (BTU/hr) for a homelab or server closet based on equipment wattage, room dimensions, insulation quality, and solar exposure. All electrical power converts to heat — this tool calculates equipment heat output, envelope heat gain through walls, and solar gain to produce a total BTU/hr cooling requirement. Recommends AC tonnage, mini-split sizing (rounded to standard 6K BTU increments), and exhaust fan CFM for ventilation-only cooling. Use after power_cost to size cooling for your homelab room.
    ConnectorNo auth
  • Build the MIB hosted-checkout link for a chosen offer (from compare_insurance_quotes). MOTOR REQUIRES the full details collected via get_purchase_requirements (vehicle + insured + next_of_kin) — without them this tool returns an error telling you what to collect. With them, the customer lands on a review summary of everything gathered in chat and only signs in and pays with Paystack — the agent never handles payment.
    ConnectorNo auth
  • No version argument. Cancel an open order. Two routes: pass 'signature' (signed over what prepare_cancel_order returned) to relay a gasless cancellation - state-changing, and the route an intent order takes; omit 'signature' entirely for the on-chain route, which returns the cancel transaction for the user to sign and send, the route an order that went on chain (a native-token sell) takes. The server never signs.
    Connector
    Destructive
    No auth
  • Prepare a BID/offer on a position: returns the Seaport order to sign (EIP-712), the currency approval needed, and how to submit it. Name markets (basenames) take `name` instead of tokenId — any REGISTERED name is biddable, listed or not. The agent reads its Seaport counter, signs, and POSTs the signed order — settlement stays on Seaport.
    ConnectorNo auth
  • Prepare a SELL listing or Dutch auction. Verifies the seller OWNS the position and it's transferable (not voted/attached), builds the Seaport order with the Interface fee injected by the server, and returns the one-time NFT approval + EIP-712 typed data to sign. Name markets (basenames) take `name` instead of tokenId. Never signs or holds keys.
    ConnectorNo auth
  • Prepare, decode, and verify an unsigned cross-chain native-USDC bridge construction aid for the caller-owned EOA or Safe, over the enumerated v1 Circle-CCTP route set (Ethereum, Polygon, Base, Arbitrum, Avalanche); any other chain, token, or bridge route is refused by name. The envelope's valid_until bounds freshness and is committed to the artifact digest; the signer account nonce is the on-chain replay boundary, and this tool cannot guarantee single execution. Returns ordered allowance-reset, approval, and call steps on the source chain only; never signs or submits. Every envelope from this server is valid for 300 seconds from construction (valid_until); a stale envelope is refused by the verifier — request a fresh one.
    ConnectorNo auth