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.

Anahana Content MCP

REMOTE · WWW.ANAHANA.COM

Wellness and angel-number articles in 24 languages, plus Nema products with prices and page links.

Available components

0 this week 85 Trust /100

Last scanned (9 hours ago)

Scores higher than 91% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Health and Science

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 Security77
  • 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
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability70
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1230 tokens (~246/item across 5 items; 5 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 5 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

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 →

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 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 25 Oct 26 0
    • Authorization: unverified → partial ▲ security
    • Injection markers: unverified → pass ▲ security
    • Stability: unverified → pass ▲ security
    • Endpoint reachability: unreachable → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 24 Oct 26 0
    • Endpoint reachability: reachable → unreachable ▼ security
    • Stability: pass → unverified ▼ security
    • Tool safety: pass → unverified ▼ security
    • Authorization: partial → unverified ▼ security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 28 Sept 26 0
    • Authorization: unverified → partial ▲ security
    • Schema quality: 302 → 246 ▲ functional
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
    • Server version: 1.2.1 → 1.3.0 functional
    • New tool “get_product” functional
    • New tool “list_products” 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
  • 12 Sept 26 0
    • Stability: 0.97 → pass security
  • 31 Aug 26 0
    • Server version: 1.2.0 → 1.2.1 functional
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://www.anahana.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=www.anahana.com CN=WE1,O=Google Trust Services,C=US 25 Sept 2026 24 Dec 2026 ECDSA 256 ECDSA-SHA256 6a9dee9e2d7ddcf40e7404157b9f8f15
SANs: www.anahana.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 secure

Validation of www.anahana.com. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
anahana.com. DS published 2371 13 Verified
www.anahana.com. Verified address RRset verified with the apex keys
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://www.anahana.com/mcp Verified 200
http (plaintext) http://www.anahana.com/mcp HTTPS enforced 301 https://www.anahana.com/mcp
MCP tools · 5 exposed · ~1,230 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_article ~314

Fetch a specific Anahana article as markdown, given its full URL, site-relative path (e.g. "/en/angel-numbers/111-angel-number/"), or a bare slug from search_content results (e.g. "111-angel-number"). Tries two fetch modes against the live site in order: (1) content negotiation — GET the article URL with `Accept: text/markdown`; (2) the path-based markdown mirror at `<article-url>index.md`. Both are live. Page chrome (skip link, table of contents with dead anchors, back-to-top anchor, analytics pixel) is stripped, so what you get back is the article body. If both modes fail, returns a clear error naming the canonical HTML URL instead of silently failing. Works in all 24 languages: a full URL or a site-relative path already names its language, and a bare slug is resolved in the language given by `language` (English by default). Article slugs are identical across languages — only the title and body are translated — so the same slug plus a different `language` gives you the same article in that language.

NameTypeReqDescription
languagestring–Language for a BARE SLUG, e.g. "ja". Ignored when url_or_slug is a full URL or a site-relative path, since those already carry their language prefix. Defaults to "en".
url_or_slugstringyesFull URL, site-relative path, or bare slug, e.g. "111-angel-number".

No output schema declared.

No examples provided.

get_product ~142

Get one Nema by Anahana product by its sku from list_products (e.g. "complete-guide-en"): name, type, language, list price, currency, and url — the product's page on anahana.com, the only place to buy it. Paid products carry checkout_note: "buyers outside the US see a converted price with a 4% conversion fee at checkout". A sku that is in the catalog but not on sale returns available: false, a definitive answer; do not retry it. Read-only: no checkout, no payment link.

NameTypeReqDescription
skustringyesThe product sku from list_products, e.g. "complete-guide-en".

No output schema declared.

No examples provided.

list_products ~182

List the Nema by Anahana digital products on sale right now (for example angel-number guides and a personalized natal chart report). Each product has its sku, name, type (free_lead_magnet, one_time or bundle), language, list price and currency (e.g. "11.11" and "USD"), and url: the product's page on anahana.com, the only place to buy it. Paid products also carry checkout_note. Read-only: this server has no checkout or payment tool and never returns a payment link. The list is the site's own catalog, regenerated on every site deploy. Use get_product for one product.

NameTypeReqDescription
languagestring–Only products in this language, e.g. "en". One code, a comma-separated list, or "all". Omit to list every product on sale, in every language.

No output schema declared.

No examples provided.

lookup_angel_number ~296

Resolve a specific angel number (e.g. "111", "1234", "22") to its Anahana article URL, in any of 24 languages. Slugs are English-stable across every language — most numbers are "<number>-angel-number"; the single digits 1-9, the master numbers 11/22/.../99, and the outlier 828 use "angel-number-<number>" — so only the title and body differ between languages. COVERAGE, however, is not uniform: en/de/es/ru publish 568 distinct numbers, the other 20 languages publish 519, so a number can exist in English and genuinely not exist in Japanese. Existence is therefore always answered against the language you asked for, from an index the site regenerates on every deploy. A well-formed number with no article in that language is a successful result with `exists: false`, a definitive message, `also_published_in` naming the languages that DO have it, and the nearest numbers published in your language — not an error. Do not retry it.

NameTypeReqDescription
languagestring–Language to resolve in, e.g. "ja". Defaults to "en", which is the pre-1.2.0 behavior. Supported codes are listed in _meta.languages_supported.
numberstringyesThe angel number as digits, e.g. "111" or "828".

No output schema declared.

No examples provided.

search_content ~296

Search Anahana's wellness content — angel numbers, astrology, zodiac, tarot, crystals, yoga, meditation, breathing exercises, mental and physical health, and more — in any of 24 languages. Returns matching articles with title, url, section, language, and a short summary. Matching is KEYWORD/SUBSTRING over title, description, section and slug; it is NOT semantic search, in any language. For zh, ja and th the query is not word-segmented, so it is matched as one substring. The index is regenerated on every site deploy; exact live per-language document counts are in each response's _meta and at https://www.anahana.com/content-index/manifest.json.

NameTypeReqDescription
languagestring–Language to search. Omit for English (the default and the pre-1.2.0 behavior). One code ("de"), a comma-separated list ("de,fr,ja"), or "all" to search every indexed language. Supported codes are lis…
querystringyesSearch keywords, e.g. '111 angel number' or 'box breathing'.

No output schema declared.

No examples provided.

Install

How do I install the Anahana Content MCP server?

Anahana Content MCP is a hosted endpoint at https://www.anahana.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 · www.anahana.com

# add to Claude Code
claude mcp add --transport http com-anahana-content-mcp 'https://www.anahana.com/mcp'
Common questions

What is the Anahana Content MCP server?

Anahana Content MCP is listed in the public MCP registry as com.anahana/content-mcp. Wellness and angel-number articles in 24 languages, plus Nema products with prices and page links. This page covers its hosted endpoint (https://www.anahana.com/mcp).

Is the Anahana Content MCP server safe to use?

Anahana Content MCP scores 85 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 Anahana Content MCP server expose?

Anahana Content MCP exposes 5 tools: search_content, get_article, lookup_angel_number, list_products, get_product. Their descriptions and schemas cost roughly 1,230 tokens of context every time the server is loaded.

Does the Anahana Content MCP server require authentication?

No. We connected to Anahana Content MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Anahana Content MCP server still maintained?

Anahana Content MCP 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 did VerifyMCP test on the Anahana Content MCP server?

VerifyMCP ran 13 checks on Anahana Content MCP, 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.