com.tarotari.www/tarotari
REMOTE · WWW.TAROTARI.COM
Rider-Waite tarot deck and computed astronomy: charts, positions, exact aspect moments
Available components
Last scanned (20 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1094 tokens (~136/item across 8 items; 8 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 11 Nov 26 +1
- Stability: 0.97 → pass security
- 10 Nov 26 −1
- Stability: pass → 0.97 functional
- 9 Nov 26 +1
- Stability: 0.97 → pass security
- 8 Nov 26 −1
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Oct 26 0
- Stability: 0.97 → pass security
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → 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 Nov 2026 · Probed https://www.tarotari.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tarotari.com | CN=YE2,O=Let's Encrypt,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 66fdf6f3c35fb45021df3110b458141f336 |
| SANs: *.tarotari.com, tarotari.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 www.tarotari.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| tarotari.com. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.tarotari.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.tarotari.com/api/mcp | Served over HTTP | 200 |
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 →
aspect_exact_time Exact moment of an aspect ~190
Finds the moments when two planets form an exact angle: conjunction, sextile, square, trine or opposition. Steps through positions and refines by bisection, accurate to the minute. The same method yields new moons, full moons and sign ingresses, for which mean formulas are unfit.
| Name | Type | Req | Description |
|---|---|---|---|
| aspect | string | yes | Тип аспекта |
| from | string | yes | Начало периода поиска, ГГГГ-ММ-ДД |
| planet_a | string | yes | Первая планета |
| planet_b | string | yes | Вторая планета |
| to | string | yes | Конец периода поиска, ГГГГ-ММ-ДД. Не более 400 дней от начала |
| tz_offset_minutes | number | – | Смещение часового пояса в минутах от UTC: 180 для Москвы, 0 для UTC. По умолчанию 0 |
No output schema declared.
No examples provided.
moon_state State of the Moon ~151
Moon phase, illumination, lunar day, sign and degree for a given moment. Illumination and the lunar day are counted from the real Sun-Moon conjunction, not from the mean synodic formula, which is off by hours and, near midnight, by a whole lunar day.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Дата в формате ГГГГ-ММ-ДД |
| time | string | – | Время ЧЧ:ММ по местному поясу, по умолчанию 12:00 |
| tz_offset_minutes | number | – | Смещение часового пояса в минутах от UTC: 180 для Москвы, 0 для UTC. По умолчанию 0 |
No output schema declared.
No examples provided.
natal_chart Birth chart ~168
A full birth chart for a date, time and place: planetary positions, house cusps, aspects with orbs, the balance of elements and modalities, and major configurations.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Дата в формате ГГГГ-ММ-ДД |
| house_system | string | – | Система домов, по умолчанию whole |
| lat | number | yes | Широта места рождения, градусы |
| lon | number | yes | Долгота места рождения, градусы |
| time | string | yes | Время рождения ЧЧ:ММ по местному поясу |
| tz_offset_minutes | number | – | Смещение часового пояса в минутах от UTC: 180 для Москвы, 0 для UTC. По умолчанию 0 |
No output schema declared.
No examples provided.
planet_positions Planetary positions ~132
Ecliptic longitudes of ten planets for a given moment: sign, degree within the sign, retrograde status. Computed from VSOP87 ephemerides rather than read from tables.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Дата в формате ГГГГ-ММ-ДД |
| time | string | – | Время ЧЧ:ММ по местному поясу, по умолчанию 12:00 |
| tz_offset_minutes | number | – | Смещение часового пояса в минутах от UTC: 180 для Москвы, 0 для UTC. По умолчанию 0 |
No output schema declared.
No examples provided.
tarot_birth_card Tarot birth card ~60
The personal major arcanum from a birth date: the digits of the date summed and reduced to 1-22. The classic Tarot Birth Card calculation.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Дата в формате ГГГГ-ММ-ДД |
No output schema declared.
No examples provided.
tarot_card Tarot card meaning ~88
The meaning of a single Rider-Waite card: upright and reversed, arcanum, suit, links to the image and the page. Looks up by slug (major-00, cups-07) or by Russian name.
| Name | Type | Req | Description |
|---|---|---|---|
| card | string | yes | Слаг карты (major-00, wands-12) или название на русском (Шут, Семёрка Кубков) |
No output schema declared.
No examples provided.
tarot_deck The full deck ~63
All 78 cards of the Rider-Waite deck with upright and reversed meanings. Can be limited to a group: major, wands, cups, swords, pentacles.
| Name | Type | Req | Description |
|---|---|---|---|
| group | string | – | Группа карт. Без неё возвращается вся колода |
No output schema declared.
No examples provided.
tarot_draw Draw a spread ~104
Draws cards from the deck without repeats, in upright and reversed positions. With a seed the output is deterministic: the same seed gives the same spread.
| Name | Type | Req | Description |
|---|---|---|---|
| allow_reversed | boolean | – | Разрешить перевёрнутые положения, по умолчанию true |
| count | number | – | Сколько карт вытянуть, 1–15. По умолчанию 3 |
| seed | number | – | Зерно генератора для воспроизводимого расклада |
No output schema declared.
No examples provided.
How do I install the com.tarotari.www/tarotari MCP server?
com.tarotari.www/tarotari is a hosted endpoint at https://www.tarotari.com/api/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 · www.tarotari.com
claude mcp add --transport http com-tarotari-www-tarotari 'https://www.tarotari.com/api/mcp'
What is the com.tarotari.www/tarotari MCP server?
com.tarotari.www/tarotari is an MCP server listed in the public MCP registry as com.tarotari.www/tarotari. Rider-Waite tarot deck and computed astronomy: charts, positions, exact aspect moments. This page covers its hosted endpoint (https://www.tarotari.com/api/mcp).
Is the com.tarotari.www/tarotari MCP server safe to use?
com.tarotari.www/tarotari scores 72 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 com.tarotari.www/tarotari MCP server expose?
com.tarotari.www/tarotari exposes 8 tools: tarot_card, tarot_deck, tarot_draw, tarot_birth_card, planet_positions, and 3 more. Their descriptions and schemas cost roughly 956 tokens of context every time the server is loaded.
Does the com.tarotari.www/tarotari MCP server require authentication?
No. We connected to com.tarotari.www/tarotari without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.tarotari.www/tarotari MCP server still maintained?
com.tarotari.www/tarotari is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the com.tarotari.www/tarotari MCP server?
VerifyMCP ran 12 checks on com.tarotari.www/tarotari, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about com.tarotari.www/tarotari: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.