Tarot
NPM · @PIPEWORX/MCP-TAROT · 2 COMPONENTS
Tarot MCP — Pipeworx original 78-card tarot deck (Rider–Waite–Smith tradition). Keyless, no…
Available components
Last scanned (10 hours ago)
Scores higher than 65% of npm servers
Category Entertainment and Games
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-tarot). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 884 tokens (~147/item across 6 items; 6 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- 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 package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
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.
- 4 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 80
First indexed and scored.
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 · Analysed npm/@pipeworx/mcp-tarot@1.1.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-tarot |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-tarot/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560370725 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:45e6a78ed8dffd5e90d4c039a00dddf4ab98cea296c67d7d0ee846a6c97a8857117ba991407edb87a6083d766cbe96993cea5eb53d768270df8421781 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 ~151
Draws a spread of 1–78 random cards from the Pipeworx original tarot deck (Rider–Waite–Smith tradition), each with its own orientation and traditional meaning for that orientation.
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | yes | Number of cards to draw (1–78). |
| reversals | boolean | – | Allow reversed orientation (50% chance per card). Default true; pass false to always draw upright. |
| seed | string | – | Reproduce a previous draw by passing back the seed it returned. Omit for fresh randomness. |
| session_id | string | – | Draw from an open tarot_shuffle session instead of a fresh single-call draw (hosted only; never repeats a card within the session). |
No output schema declared.
No examples provided.
get_card ~115
Looks up one card from the Pipeworx original tarot deck by its id (e.g. "major_00", "wands_01") or its exact name (e.g. "The Fool"). Returns both upright and reversed meanings as reference, plus keywords and the image description.
| Name | Type | Req | Description |
|---|---|---|---|
| name_short | string | yes | Card id ("major_00".."major_21", "wands_01".."pentacles_14") or exact card name (e.g. "The Fool", "Ace of Wands"). |
No output schema declared.
No examples provided.
random_card ~155
Draws one random card from the Pipeworx original 78-card tarot deck (Rider–Waite–Smith tradition). Returns the card, its orientation (upright or reversed, a coin-flip unless disabled), the traditional meaning for that orientation, and the seed used to reproduce the draw.
| Name | Type | Req | Description |
|---|---|---|---|
| reversals | boolean | – | Allow reversed orientation (50% chance per card). Default true; pass false to always draw upright. |
| seed | string | – | Reproduce a previous draw by passing back the seed it returned. Omit for fresh randomness. |
| session_id | string | – | Draw from an open tarot_shuffle session instead of a fresh single-call draw (hosted only; never repeats a card within the session). |
No output schema declared.
No examples provided.
search_cards ~69
Searches the Pipeworx original tarot deck by name, suit, or keyword — matches against card names, both orientations’ keywords and meanings, and suit.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Keyword or phrase to search for (e.g. "moon", "strength", "cups", "betrayal"). |
No output schema declared.
No examples provided.
tarot_shuffle ~115
Opens (or reshuffles) a stateful 78-card tarot session on the Pipeworx original deck, so later random_card/draw_cards/tarot_spread calls with the same session_id draw without repeating a card until the session is reshuffled or expires (24h). Hosted only — a standalone/npm build returns session_supported:false.
| Name | Type | Req | Description |
|---|---|---|---|
| seed | string | – | Deterministic shuffle order. Omit for fresh randomness. |
| session_id | string | – | Reshuffle this existing session instead of opening a new one. |
No output schema declared.
No examples provided.
tarot_spread ~227
Deals a named layout from the Pipeworx original tarot deck (Rider–Waite–Smith tradition): three_card, situation_obstacle_advice, celtic_cross, horseshoe, yes_no, or a custom set of positions. Each position gets its own card, orientation, and traditional meaning for that orientation. `question` is echoed back verbatim — this tool never interprets it.
| Name | Type | Req | Description |
|---|---|---|---|
| positions | array | – | Required when spread is "custom": the ordered list of position labels (max 20). |
| question | string | – | The question this spread is being read for. Echoed back verbatim, never interpreted. |
| reversals | boolean | – | Allow reversed orientation per card (50% chance). Default true. |
| seed | string | – | Reproduce a previous spread by passing back the seed it returned. Omit for fresh randomness. |
| session_id | string | – | Deal from an open tarot_shuffle session instead of a fresh deal (hosted only; never repeats a card within the session). |
| spread | string | yes | Which named layout to deal. |
No output schema declared.
No examples provided.
How do I install the Tarot MCP server?
Tarot runs locally as an npm package, launched with npx -y @pipeworx/mcp-tarot. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-tarot
claude mcp add pipeworx-io-tarot -- npx -y @pipeworx/mcp-tarot
What is the Tarot MCP server?
Tarot is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tarot. Tarot MCP, Pipeworx original 78-card tarot deck (Rider–Waite–Smith tradition). Keyless, no… This page covers its npm package (@pipeworx/mcp-tarot).
Is the Tarot MCP server safe to use?
Tarot scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Tarot MCP server expose?
Tarot exposes 6 tools: random_card, draw_cards, search_cards, get_card, tarot_spread, tarot_shuffle. Their descriptions and schemas cost roughly 832 tokens of context every time the server is loaded.
Is the Tarot MCP server still maintained?
Tarot 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.
What licence is the Tarot MCP server under?
Tarot declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the Tarot MCP server?
VerifyMCP ran 15 checks on Tarot, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about Tarot: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.