Divineapi Western Astrology MCP Server

divineapi-western-astrology-mcp PyPI v1.5.0

Published by divineapi — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Official MCP server for Divine API's Western Astrology services — Natal, Synastry, Transit, Composite, Progressions

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Minimal
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 99/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 57

Each tool and what it can reach — statically extracted from the published source.

  • divine_western_arabic_lotsno sensitive capability
  • divine_western_ascendant_reportno sensitive capability
  • divine_western_aspect_patternsno sensitive capability
  • divine_western_aspect_tableno sensitive capability
  • divine_western_asteroid_positionsno sensitive capability
  • divine_western_chart_shapeno sensitive capability
  • divine_western_composite_aspect_tableno sensitive capability
  • divine_western_composite_house_cuspsno sensitive capability
  • divine_western_composite_natal_wheel_chartno sensitive capability
  • divine_western_composite_planetary_positionsno sensitive capability
Show 47 more tools ↓
  • divine_western_custom_transitno sensitive capability
  • divine_western_declinations_parallelsno sensitive capability
  • divine_western_dominantsno sensitive capability
  • divine_western_eclipseno sensitive capability
  • divine_western_fixed_stars_detailsno sensitive capability
  • divine_western_fixed_stars_listno sensitive capability
  • divine_western_full_transitno sensitive capability
  • divine_western_general_house_reportno sensitive capability
  • divine_western_general_sign_reportno sensitive capability
  • divine_western_house_cuspsno sensitive capability
  • divine_western_moon_phase_calendarno sensitive capability
  • divine_western_moon_phasesno sensitive capability
  • divine_western_natal_insightsno sensitive capability
  • divine_western_natal_wheel_chartno sensitive capability
  • divine_western_other_minor_bodiesno sensitive capability
  • divine_western_planet_combustion_transitno sensitive capability
  • divine_western_planet_retrograde_transitno sensitive capability
  • divine_western_planet_return_detailsno sensitive capability
  • divine_western_planet_returns_listno sensitive capability
  • divine_western_planetary_arc_directionsno sensitive capability
  • divine_western_planetary_ingressno sensitive capability
  • divine_western_planetary_midpointsno sensitive capability
  • divine_western_planetary_positionsno sensitive capability
  • divine_western_prenatal_detailsno sensitive capability
  • divine_western_prenatal_listno sensitive capability
  • divine_western_progressed_lunar_eventsno sensitive capability
  • divine_western_secondary_progressionsno sensitive capability
  • divine_western_synastry_aspectno sensitive capability
  • divine_western_synastry_conflicting_readingno sensitive capability
  • divine_western_synastry_contrasting_readingno sensitive capability
  • divine_western_synastry_emotional_compatno sensitive capability
  • divine_western_synastry_financial_compatno sensitive capability
  • divine_western_synastry_harmonious_readingno sensitive capability
  • divine_western_synastry_house_cuspsno sensitive capability
  • divine_western_synastry_intense_readingno sensitive capability
  • divine_western_synastry_natal_wheel_chartno sensitive capability
  • divine_western_synastry_physical_compatno sensitive capability
  • divine_western_synastry_planetary_positionsno sensitive capability
  • divine_western_synastry_sexual_compatno sensitive capability
  • divine_western_synastry_spiritual_compatno sensitive capability
  • divine_western_transit_basicno sensitive capability
  • divine_western_transit_dailyno sensitive capability
  • divine_western_transit_houseno sensitive capability
  • divine_western_transit_monthlyno sensitive capability
  • divine_western_transit_planetary_positionsno sensitive capability
  • divine_western_transit_weeklyno sensitive capability
  • divine_western_transit_wheel_chartno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v1.5.0 latest A 99/100 0 1.12.1 2026-07-27

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/divineapi-western-astrology-mcp/badge.svg)](https://mcptrustchecker.com/registry/divineapi-western-astrology-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/divineapi-western-astrology-mcp"><img src="https://mcptrustchecker.com/registry/divineapi-western-astrology-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/divineapi-western-astrology-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan divineapi-western-astrology-mcp --online --registry pypi

Use the free API → How scoring works

More in Lifestyle & Local