Asterwise
REMOTE · MCP.ASTERWISE.COM · SCANNED SEP 21
Vedic and Western astrology for AI agents: charts, dasha, matchmaking, panchanga, numerology, tarot.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security97
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
- The authorisation server supports Client ID Metadata Documents, the current MCP client-registration mechanism. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 28896 tokens (~280/item across 103 items; 103 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 Management43
- Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 103 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 104 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
How do I install the Asterwise MCP server?
Asterwise is a hosted endpoint at https://mcp.asterwise.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.asterwise.com
claude mcp add --transport http com-asterwise-mcp 'https://mcp.asterwise.com/mcp'
{
"mcpServers": {
"com-asterwise-mcp": {
"url": "https://mcp.asterwise.com/mcp"
}
}
} {
"servers": {
"com-asterwise-mcp": {
"type": "http",
"url": "https://mcp.asterwise.com/mcp"
}
}
} [mcp_servers.com-asterwise-mcp] url = "https://mcp.asterwise.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-asterwise-mcp": {
"type": "remote",
"url": "https://mcp.asterwise.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-asterwise-mcp --url 'https://mcp.asterwise.com/mcp' --transport streamable-http
mcp_servers:
com-asterwise-mcp:
url: "https://mcp.asterwise.com/mcp" {
"McpServers": {
"com-asterwise-mcp": {
"Transport": "http",
"Url": "https://mcp.asterwise.com/mcp"
}
}
} assistant mcp add com-asterwise-mcp -t streamable-http -u 'https://mcp.asterwise.com/mcp'
{
"mcpServers": {
"com-asterwise-mcp": {
"type": "http",
"url": "https://mcp.asterwise.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 0
- Tool “asterwise_get_yogas” rewrote its description, which is the text the model reads security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 +1
- Stability: unverified → 0.03 ▲ functional
- 8 Sept 26 +39
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. security
- MCP protocol: unverified → pass ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
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 Sept 2026 · Probed https://mcp.asterwise.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.asterwise.com | CN=YE1,O=Let's Encrypt,C=US | 30 Jul 2026 | 28 Oct 2026 | ECDSA 256 | ECDSA-SHA384 | 5fab72366a793d555dd69cc039e8b28557b |
| SANs: mcp.asterwise.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.asterwise.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| asterwise.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="Asterwise MCP", resource_metadata="https://mcp.asterwise.com/.well-known/oauth-protected-resource"
Bearer realm="Asterwise MCP", resource_metadata="https://mcp.asterwise.com/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(), usb=(), magnetometer=(), accelerometer=(), gyroscope=(), browsing-topics=() |
Protected resource metadata
| Document | https://mcp.asterwise.com/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://mcp.asterwise.com |
| Authorisation server | https://mcp.asterwise.com |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.asterwise.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.asterwise.com/mcp | HTTPS enforced | 301 | https://mcp.asterwise.com/mcp |
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 →
asterwise_get_western_zodiac_compatibility Western Zodiac Compatibility ~226
Sign-to-sign compatibility without birth data. Based on element and modality affinity. Fast — no ephemeris calculation required. WORKFLOW: BEFORE: None — no birth data needed. AFTER: asterwise_get_western_compatibility — when full charts are available. INPUT CONTRACT: sign1, sign2 — English zodiac names (Aries … Pisces). DO NOT CONFUSE WITH: asterwise_get_western_compatibility — requires full birth data, more accurate. asterwise_get_western_synastry — aspect geometry between two full charts. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-western-zodiac-compatibility/
| Name | Type | Req | Description |
|---|---|---|---|
| response_format | string | – | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
| sign1 | string | yes | First zodiac sign, e.g. 'Aries'. |
| sign2 | string | yes | Second zodiac sign, e.g. 'Libra'. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
asterwise_get_yogas Yogas ~251
Evaluates the natal chart for named classical yogas and returns category, formation text, the classical texts each yoga is drawn from (classical_sources), a modern summary, and keywords per hit. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — same birth tuple should be understood before interpreting yoga names. AFTER: asterwise_get_doshas — complementary affliction scan on the same chart. INPUT CONTRACT: BirthData follows the global contract. time='00:00' is accepted without flag; yoga house logic may be wrong if true birth time is unknown. DO NOT CONFUSE WITH: asterwise_get_natal_chart — supplies graha_drishti and base chart rows, not the yoga catalogue. asterwise_get_panchanga — Panchanga yoga (Sun+Moon sum) is unrelated to these natal yogas. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-yogas/
| Name | Type | Req | Description |
|---|---|---|---|
| birth | object | yes | Birth data for a single person. |
| response_format | string | – | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
asterwise_get_yogini_dasha Yogini Dasha ~265
Computes the eight-Yogini, 36-year Yogini Dasha cycle with two-level period trees and DD/MM/YYYY boundaries from birth data. WORKFLOW: BEFORE: RECOMMENDED — asterwise_get_natal_chart — establishes birth context for interpreting Yogini lords. AFTER: asterwise_get_dasha — optional Vimshottari comparison for the same native. INPUT CONTRACT: Tree lives at data.periods.root[] — agents must not expect a top-level data.periods array. Calendar strings in periods use DD/MM/YYYY. BirthData follows the global contract. DO NOT CONFUSE WITH: asterwise_get_dasha — Vimshottari planet periods with data.periods[] and optional levels 1–5, not Yogini names. asterwise_get_ashtottari_dasha — 108-year system with data.periods.root[] but planet-based rows, not Yoginis. Full output and error contract: https://docs.asterwise.com/mcp/tools/get-yogini-dasha/
| Name | Type | Req | Description |
|---|---|---|---|
| birth | object | yes | Birth data for a single person. |
| response_format | string | – | Output format: 'markdown' (default) for a readable report, or 'json' for the raw structured payload. |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
What is the Asterwise MCP server?
Asterwise is an MCP server listed in the public MCP registry as com.asterwise/mcp. Vedic and Western astrology for AI agents: charts, dasha, matchmaking, panchanga, numerology, tarot. This page covers its hosted endpoint (https://mcp.asterwise.com/mcp).
Is the Asterwise MCP server safe to use?
Asterwise scores 84 out of 100 on VerifyMCP. 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 Asterwise MCP server expose?
Asterwise exposes 103 tools: asterwise_get_natal_chart, asterwise_get_divisional_chart, asterwise_get_chart_strength, asterwise_get_special_ascendants, asterwise_get_nakshatra_details, and 98 more. Their descriptions and schemas cost roughly 26,498 tokens of context every time the server is loaded.
Does the Asterwise MCP server require authentication?
Yes. Asterwise asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the Asterwise MCP server still maintained?
Asterwise is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.