Back to Browse

Asterwise MCP Server

Developer ToolsModerate7.2MCP RegistryLocalRemote
Free

Server data from the Official MCP Registry

Vedic and Western astrology for AI agents: charts, dasha, matchmaking, panchanga, numerology, tarot.

About

Vedic and Western astrology for AI agents: charts, dasha, matchmaking, panchanga, numerology, tarot.

Remote endpoints: streamable-http: https://mcp.asterwise.com/mcp

Security Report

7.2
Moderate7.2Low Risk

The Asterwise MCP server is a well-structured astrology/divination tool with proper authentication, reasonable permissions for its category (network HTTP for API calls, env vars for credentials), and no critical security vulnerabilities. Minor findings include broad exception handling and some areas where input validation could be more explicit, but these do not pose significant security risks.

3 files analyzed · 4 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

system_info

Check that this permission is expected for this type of plugin.

How to Install & Connect

Available as Local & Remote

This plugin can run on your machine or connect to a hosted endpoint. during install.

Documentation

View on GitHub

From the project's GitHub README.

Asterwise MCP Server

Listed on mcpservers.org

Astrology and divination calculations as MCP tools. 103 tools covering Vedic and Western astrology, numerology, tarot, crystals, dreams, natal charts, Dasha, matchmaking and Panchanga, with interpretations that follow classical Jyotish method. Every position is verified against an independent Swiss Ephemeris run (asterwise.com/proof) and checked against NASA JPL Horizons, median 0.046 arcseconds over 80 positions (asterwise.com/accuracy).

Quick Start (2 minutes)

See it first: 46-second demo of Claude Desktop casting a chart through this server, and the independent Swiss Ephemeris cross-check.

Get your API key

Sign up free at asterwise.com/dashboard: 500 calls/month on the Sandbox tier. No credit card. No time limit.

Connect to Claude Desktop

Add to ~/Library/Application Support/Claude/claude_desktop_config.json:

{
  "mcpServers": {
    "asterwise": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://mcp.asterwise.com/mcp"
      ],
      "env": {
        "MCP_HEADER_AUTHORIZATION": "Bearer your-api-key-here"
      }
    }
  }
}

Connect to Cursor

Add to .cursor/mcp.json in your project:

{
  "mcpServers": {
    "asterwise": {
      "url": "https://mcp.asterwise.com/mcp",
      "headers": {
        "Authorization": "Bearer your-api-key-here"
      }
    }
  }
}

Test the connection

curl https://mcp.asterwise.com/health

Authentication

Two methods supported:

Method 1 — API Key (quick start)
Pass your Asterwise API key (starts with aw_) either as Authorization: Bearer <api-key> or as an X-API-Key: <api-key> header. Both are equivalent; use whichever your MCP client can set.

Method 2 — OAuth 2.1 (production)
Exchange your API key for a short-lived token:

curl -X POST https://mcp.asterwise.com/oauth/token \
  -H "Content-Type: application/json" \
  -d '{
    "grant_type": "client_credentials",
    "client_id": "your-api-key",
    "client_secret": "your-api-key"
  }'

Returns: {"access_token": "...", "expires_in": 3600, ...}

Use the token: Authorization: Bearer <access_token>

Access tokens are stateless HS256 JWTs. The API key is carried inside the token encrypted with a key derived from JWT_SECRET; only a SHA-256 hash of the key appears in the sub claim. Keep JWT_SECRET private.

Configuration

Copy .env.example to .env and set at least:

VariableRequiredDescription
ASTERWISE_API_BASE_URLYesAsterwise API base URL (e.g. https://api.asterwise.com).
JWT_SECRETFor /oauth/tokenAt least 32 characters; used to sign access tokens.
MCP_SERVER_HOST / MCP_SERVER_PORTNoBind address and port for the MCP HTTP server.
LOG_LEVELNoDefault INFO.
MCP_OAUTH_SECRETFor OAuthShared with asterwise-api; verifies access tokens issued by its /v1/oauth/token.
INTERNAL_API_TOKENFor OAuth client registrationShared with asterwise-api; used when forwarding dynamic client registration.
FRONTEND_URLFor /authorizeWhere the browser is sent for sign-in and consent (e.g. https://asterwise.com).
OPENAI_APPS_CHALLENGE_TOKENNoServed at /.well-known/openai-apps-challenge for directory verification.

Tools (103 total)

The MCP server exposes 103 tools organized by Python module. The categorization reflects code organization; tools may serve multiple traditions (e.g. matchmaking includes both Sanskrit Dashakoot and Tamil Porutham methods).

  • western — 16 tools (chart, transits, returns, progressions)
  • natal — 13 tools (chart, dasha trees, ascendant systems)
  • numerology — 11 tools (profile, compatibility, life path)
  • tarot — 9 tools (draws, spreads, suit references)
  • vedic_reference — 8 tools (nakshatra, planet nature, ayanamsha, classical reference)
  • numerology_gaps — 7 tools (expression, soul urge, personality, maturity, balance, karmic, personal cycles)
  • panchanga — 6 tools (panchanga, choghadiya, rahu kaal, hora)
  • crystals — 5 tools (list, by planet, recommendations, individual)
  • dasha — 5 tools (vimshottari, ashtottari, yogini, char, transits)
  • matchmaking — 5 tools (dashakoot, porutham, thirumana, papasamyam, compatibility)
  • horoscope — 4 tools (daily/weekly/monthly/yearly)
  • yoga_dosha — 4 tools (yogas, doshas, sade sati, pitra dosha)
  • angel_numbers — 3 tools (today, personal, lookup)
  • varshaphal — 3 tools (annual chart, saham, harsha bala)
  • dreams — 2 tools (symbols, individual)
  • panchanga_ext — 2 tools (calendar, festivals, tamil)

For the full tool list see docs.asterwise.com or the MCP server's tool listing endpoint.

Run locally

python -m venv .venv
source .venv/bin/activate
pip install -r requirements-dev.txt
export ASTERWISE_API_BASE_URL=https://api.asterwise.com
export JWT_SECRET="$(python -c 'import secrets; print(secrets.token_hex(32))')"
uvicorn server:app --host 0.0.0.0 --port 8080

uvicorn server:app is the same entry point the production Dockerfile and railway.toml use, so the auth middleware, OAuth routes and /health are all present locally. Runtime dependencies are pinned in requirements.txt; requirements-dev.txt adds the test tooling.

Tests

pytest

Coverage is enforced at 78% for core modules (auth, client, errors, logging_config, models, runtime, server); tool modules are excluded from the gate (see .coveragerc).

Status

https://status.asterwise.com

License

MIT. See LICENSE. Security reports: see SECURITY.md.

Reviews

No reviews yet

Be the first to review this server!