Tarotap
REMOTE · TAROTAP.COM
Tarot spreads and card draws from a shuffled 78-card Rider-Waite-Smith deck, 23 languages, no key.
Available components
Last scanned (5 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Entertainment and Games
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 Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability39
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 465 tokens (~155/item across 3 items; 2 tools + 1 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 Management77
- Stability observed for 23 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 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.
- 23 Oct 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.
- 21 Oct 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.
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 5 Nov 2026 · Probed https://tarotap.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=tarotap.com | CN=YR1,O=Let's Encrypt,C=US | 3 Nov 2026 | 1 Feb 2027 | RSA 2048 | SHA256-RSA | 6312a387a6178b09c4bb5e40d9a05e57550 |
| SANs: tarotap.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of tarotap.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| tarotap.com. | absent | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://tarotap.com/mcp | Verified | 200 | |
| http (plaintext) | http://tarotap.com/mcp | HTTPS enforced | 308 | https://tarotap.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 →
draw_cards Draw Tarot Cards ~244
Shuffle a full 78-card Rider-Waite-Smith deck with server-side randomness and show it face-down in an interactive widget, where the user picks their cards by hand. Where the widget renders, the tool result does not contain the drawn cards: the widget sends the cards the user picked to the conversation once the last one is revealed. In a text-only host the cards are drawn server-side and returned in the result. Takes a spread_id from list_spreads to draw into that spread's positions, or a card_count (1-10) for a free-form draw such as a single card of the day. Card names, position names and the widget text follow locale.
| Name | Type | Req | Description |
|---|---|---|---|
| card_count | integer | – | Number of cards for a free-form draw without a spread. Defaults to 3. |
| locale | string | – | Language for spread names, position names, card names and widget text: the language the user is writing in, as a BCP-47 code (zh-CN = Simplified Chinese, zh-TW = Traditional Chinese). Defaults to en. |
| spread_id | string | – | Spread id from list_spreads. Takes precedence over card_count. |
| Name | Type | Req | Description |
|---|---|---|---|
| card_count | number | yes | – |
| cards | array | – | – |
| spread | object | – | – |
| status | string | yes | – |
No examples provided.
list_spreads List Tarot Spreads ~115
List the tarot spreads available for a reading, with each spread's id, name, tagline, number of cards, and position names, in the requested language. The ids are the values draw_cards accepts as spread_id and are the same in every language.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | string | – | Language for spread names, position names, card names and widget text: the language the user is writing in, as a BCP-47 code (zh-CN = Simplified Chinese, zh-TW = Traditional Chinese). Defaults to en. |
| Name | Type | Req | Description |
|---|---|---|---|
| spreads | array | yes | – |
No examples provided.
How do I install the Tarotap MCP server?
Tarotap is a hosted endpoint at https://tarotap.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 · tarotap.com
claude mcp add --transport http com-tarotap-tarot 'https://tarotap.com/mcp'
What is the Tarotap MCP server?
Tarotap is an MCP server listed in the public MCP registry as com.tarotap/tarot. Tarot spreads and card draws from a shuffled 78-card Rider-Waite-Smith deck, 23 languages, no key. This page covers its hosted endpoint (https://tarotap.com/mcp).
Is the Tarotap MCP server safe to use?
Tarotap scores 78 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 Tarotap MCP server expose?
Tarotap exposes 2 tools: list_spreads, draw_cards. Their descriptions and schemas cost roughly 359 tokens of context every time the server is loaded.
Does the Tarotap MCP server require authentication?
No. We connected to Tarotap without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Tarotap MCP server still maintained?
Tarotap is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.