Love Oracle — Tarot
REMOTE · WWW.LOVEORACLE.APP
Tarot card meanings for love, and answers to the most-asked love questions, in 22 languages.
Available components
Last scanned (7 hours ago)
Scores higher than 94% of remote servers
Reachable. Last reached 6 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 Usability74
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 721 tokens (~180/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
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.
- 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
- 5 Nov 26 0
- Stability: 0.97 → pass security
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 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
- 3 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 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
- 14 Aug 26 0
- Schema quality: 569 → 721 ▼ functional
- New tool “get_venus_sign” 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 6 Nov 2026 · Probed https://www.loveoracle.app/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.loveoracle.app | CN=YR1,O=Let's Encrypt,C=US | 1 Oct 2026 | 30 Dec 2026 | RSA 2048 | SHA256-RSA | 5f00bbeed0d2d4e0bc74029f304b6412c50 |
| SANs: *.loveoracle.app, loveoracle.app | ||||||
| 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 www.loveoracle.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| app. | DS published | 23684 | 8 | Verified |
| loveoracle.app. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' https://fonts.gstatic.com data:; img-src 'self' data: blob: https://*.google-analytics.com https://*.googletagmanager.com; connect-src 'self' https://*.supabase.co https://*.supabase.in wss://*.supabase.co https://kvwdcmdvxqwllkmeseyn.supabase.co wss://kvwdcmdvxqwllkmeseyn.supabase.co https://us.i.posthog.com https://eu.i.posthog.com https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; frame-src 'self'; frame-ancestors 'none'; object-src 'none'; base-uri 'self'; form-action 'self'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.loveoracle.app/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.loveoracle.app/api/mcp | HTTPS enforced | 308 | https://www.loveoracle.app/api/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 →
get_love_question_answer Answer to a common love question ~156
The long-form answer to one of the most-asked love-tarot questions ("will he come back", "does he miss me", …) and which cards speak to it. Call with no slug to list the available questions. Returns markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language for the answer, as an ISO code. One of: en, es, pt, fr, de, it, nl, da, no, fi, pl, hu, tr, ru, ja, ko, zh, zh-TW, th, vi, hi, id. Defaults to en. |
| slug | string | – | Question slug, e.g. "will-he-come-back". Omit to list every question. |
No output schema declared.
No examples provided.
get_tarot_card_love_meaning Card meaning in love ~149
What one tarot card means for love and relationships: upright, reversed, as someone’s feelings, in the context of an ex, plus its yes/no leaning and element. Returns markdown.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language for the answer, as an ISO code. One of: en, es, pt, fr, de, it, nl, da, no, fi, pl, hu, tr, ru, ja, ko, zh, zh-TW, th, vi, hi, id. Defaults to en. |
| slug | string | yes | Card slug, e.g. "the-lovers" or "two-of-cups". Always the English slug. |
No output schema declared.
No examples provided.
get_venus_sign Venus sign for a birth date ~152
Compute which zodiac sign Venus stood in on a given date — the placement that describes how somebody loves, as distinct from their Sun sign. Needs only a date. Says so explicitly when Venus changed sign that day and the hour decides. Nothing is stored.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | Date of birth as YYYY-MM-DD. Between 1700 and 2200. |
| language | string | – | Language for the answer, as an ISO code. One of: en, es, pt, fr, de, it, nl, da, no, fi, pl, hu, tr, ru, ja, ko, zh, zh-TW, th, vi, hi, id. Defaults to en. |
No output schema declared.
No examples provided.
search_tarot_cards Search the tarot deck ~147
Search the 78-card Rider–Waite–Smith deck by name and return matching cards with the slugs the other tools take. Use this first when you only have a card name.
| Name | Type | Req | Description |
|---|---|---|---|
| language | string | – | Language for the answer, as an ISO code. One of: en, es, pt, fr, de, it, nl, da, no, fi, pl, hu, tr, ru, ja, ko, zh, zh-TW, th, vi, hi, id. Defaults to en. |
| query | string | yes | Part of a card name in any supported language, e.g. "cups", "lovers", "恋人". |
No output schema declared.
No examples provided.
How do I install the Love Oracle — Tarot MCP server?
Love Oracle — Tarot is a hosted endpoint at https://www.loveoracle.app/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.loveoracle.app
claude mcp add --transport http app-loveoracle-tarot 'https://www.loveoracle.app/api/mcp'
What is the Love Oracle — Tarot MCP server?
Love Oracle — Tarot is an MCP server listed in the public MCP registry as app.loveoracle/tarot. Tarot card meanings for love, and answers to the most-asked love questions, in 22 languages. This page covers its hosted endpoint (https://www.loveoracle.app/api/mcp).
Is the Love Oracle — Tarot MCP server safe to use?
Love Oracle — Tarot scores 87 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 Love Oracle — Tarot MCP server expose?
Love Oracle — Tarot exposes 4 tools: search_tarot_cards, get_tarot_card_love_meaning, get_venus_sign, get_love_question_answer. Their descriptions and schemas cost roughly 604 tokens of context every time the server is loaded.
Does the Love Oracle — Tarot MCP server require authentication?
No. We connected to Love Oracle — Tarot without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Love Oracle — Tarot MCP server still maintained?
Love Oracle — Tarot is still listed as active in the MCP registry. We last reached this channel on 6 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 Love Oracle — Tarot MCP server?
VerifyMCP ran 13 checks on Love Oracle — Tarot, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.