
Fate & Stars MCP server
Which MCP servers are Fate & Stars's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.
read 2026-10-27
- Registry namecom.fateandstars/tarot-knowledgeverified in the MCP registry
The registry name sits under fateandstars.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.
- Stateanswerschecked 2026-10-27
- Tools3
- Server calls itselffate-and-stars-tarot-knowledge
- Server version1.0.1
- Protocol version2025-06-18
On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 297 ms.
- Whether its tools do the product's job has not been judged yet.
Once connected
- Parameters are untyped or undescribed in 3 of 3 tools: check arguments before calling.
Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.
- INITE MCP score95 of 100answers 100 · definitions 83 · context 100 · connects 100
- Answered100% of days9 of 9 daily checks
- Median first answer849 ms
- Space in an agent's context≈ 619 tokensthe definitions of all its tools (3), which an agent carries on every turn
- Tool definitionsB · 83 of 100
- Typed results3 of 3 toolsdeclared outputSchema: results come typed, read once
- Parameters without a description: in 3 of 3
What an agent can do with it
- not sure · weigh a career change against staying in a current job
- not sure · reflect on the dynamics of a relationship
- not sure · compare two options before making a decision
Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?
Worth a look
None of the five warning signs in these definitions.
A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →
get_card_meaningRead 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…
search_tarot_cardsRank 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…
get_tarot_spreadsList educational one/three-card spread definitions, or inspect one spread. Returns positions and website guides; does not perform a reading.
How to connect
Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:
{
"mcpServers": {
"tarot-knowledge": {
"type": "http",
"url": "https://fateandstars.com/mcp"
}
}
}Add it
Claude Code, in a terminal
claude mcp add --transport http fateandstars https://fateandstars.com/mcpclaude.ai, ChatGPT and other clients: add https://fateandstars.com/mcp as a custom connector in the settings.
Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.
Before we count this visit
Analytics and ad measurement tell us which pages and which of our ads do their job: Google Analytics and Google Ads, the Meta pixel, Yandex Metrica, and one first-party id of our own. Nothing is stored until you answer, and declining changes nothing about the site.