Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fate & Stars Tarot Knowledge

REMOTE · FATEANDSTARS.COM

78 tarot card meanings, ranked topic search and nine spreads, with source links.

Available components

+4 this week 74 Trust /100

Last scanned (3 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Entertainment and Games

Trust breakdown (7 categories)

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 Security69
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 381 tokens (~127/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
  • Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage79
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
  • 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 3 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

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 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 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 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 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 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.

  • 30 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.

  • 28 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.

  • 26 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.

  • 23 Oct 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.

  • 21 Oct 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.

Diagnostics

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://fateandstars.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fateandstars.com CN=WE1,O=Google Trust Services,C=US 8 Oct 2026 6 Jan 2027 ECDSA 256 ECDSA-SHA256 29c7c8abe1a2c74b0e7ea4e349c7b938
SANs: fateandstars.com, *.fateandstars.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fateandstars.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
fateandstars.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
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fateandstars.com/mcp Verified 200
http (plaintext) http://fateandstars.com/mcp Inconclusive 405
MCP tools · 3 exposed · ~298 tokens

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 →

Tool Tokens
get_card_meaning ~151

Read authored meanings with source links. Accepts names, slugs, numeric names and Coins aliases. Use brief for bounded plain-text excerpts (orientation meanings by default); sections selects exact normalized section IDs. availableSections and missingSections report content coverage; truncation is explicit. Unknown names return isError with suggestions, never an automatic substitute.

NameTypeReqDescription
briefboolean–Return plain-text excerpts up to 360 characters per section and 320 for overview. Without sections, only orientation meanings are included.
cardstringyes–
orientationstring––
sectionsarray–Select sections; career replaces work. Orientation filters upright/reversed first. Missing sections are reported, not invented.
NameTypeReqDescription
availableSectionsarrayyes–
briefbooleanyes–
categorystringyes–
keywordsobjectyes–
missingSectionsarrayyes–
namestringyes–
noticestringyes–
orientationstringyes–
overviewstringyes–
reflectionstringyes–
sectionsarrayyes–
slugstringyes–
topicsarrayyes–
urlstringyes–

No examples provided.

get_tarot_spreads ~44

List educational one/three-card spread definitions, or inspect one spread. Returns positions and website guides; does not perform a reading.

NameTypeReqDescription
spreadstring––
NameTypeReqDescription
noticestringyes–
spreadsarrayyes–

No examples provided.

search_tarot_cards ~103

Rank English card names, curated topics, keyword synonyms, overview and guide text. Supports money/finances, love/relationships, career/jobs, new beginnings and hope/hopeful. All meaningful query terms must match. Exact names rank first, followed by themes and keywords. Returns match reasons and canonical source links. Empty query lists cards, optionally by family.

NameTypeReqDescription
categorystring––
limitinteger––
querystring––
NameTypeReqDescription
cardsarrayyes–
categorystringyes–
noticestringyes–
querystringyes–
totalintegeryes–
urlstringyes–

No examples provided.

Install

How do I install the Fate & Stars Tarot Knowledge MCP server?

Fate & Stars Tarot Knowledge is a hosted endpoint at https://fateandstars.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 · fateandstars.com

# add to Claude Code
claude mcp add --transport http com-fateandstars-tarot-knowledge 'https://fateandstars.com/mcp'
Common questions

What is the Fate & Stars Tarot Knowledge MCP server?

Fate & Stars Tarot Knowledge is an MCP server listed in the public MCP registry as com.fateandstars/tarot-knowledge. 78 tarot card meanings, ranked topic search and nine spreads, with source links. This page covers its hosted endpoint (https://fateandstars.com/mcp).

Is the Fate & Stars Tarot Knowledge MCP server safe to use?

Fate & Stars Tarot Knowledge scores 74 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 Fate & Stars Tarot Knowledge MCP server expose?

Fate & Stars Tarot Knowledge exposes 3 tools: get_card_meaning, search_tarot_cards, get_tarot_spreads. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.

Does the Fate & Stars Tarot Knowledge MCP server require authentication?

No. We connected to Fate & Stars Tarot Knowledge without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Fate & Stars Tarot Knowledge MCP server still maintained?

Fate & Stars Tarot Knowledge 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.