# Anahana Content MCP (remote · www.anahana.com)

38,846 wellness & angel-number articles in 24 languages, plus 6 agent-wellbeing protocols.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-19

## Components

- remote · `www.anahana.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-anahana-content-mcp/www.md), [page](https://verifymcp.io/servers/com-anahana-content-mcp/www)

## Channel facts

- Endpoint: `https://www.anahana.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-19.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 70/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 906 tokens (~302/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http com-anahana-content-mcp https://www.anahana.com/mcp
```

### Codex

```toml
[mcp_servers.com-anahana-content-mcp]
url = "https://www.anahana.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-anahana-content-mcp": {
      "type": "remote",
      "url": "https://www.anahana.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-anahana-content-mcp --url https://www.anahana.com/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-anahana-content-mcp:
    url: "https://www.anahana.com/mcp"
```

### Other

```json
{
  "mcpServers": {
    "com-anahana-content-mcp": {
      "type": "http",
      "url": "https://www.anahana.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-18 (score 66, +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.

### 2026-08-16 (score 65, +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.

### 2026-08-15 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-14 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-08-13 (score 63)

First indexed and scored.

## MCP tools (3)

### `search_content` (~296 tokens)

Search Anahana content

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.

Input parameters:

- `language` (string): 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…
- `query` (string, required): Search keywords, e.g. '111 angel number' or 'box breathing'.

### `get_article` (~314 tokens)

Get an Anahana article as markdown

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.

Input parameters:

- `language` (string): 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_slug` (string, required): Full URL, site-relative path, or bare slug, e.g. "111-angel-number".

### `lookup_angel_number` (~296 tokens)

Resolve an angel number to its article URL

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.

Input parameters:

- `language` (string): 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.
- `number` (string, required): The angel number as digits, e.g. "111" or "828".

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-anahana-content-mcp/www#diagnostics

## Score history

- 2026-08-19: 66
- 2026-08-18: 66
- 2026-08-17: 65
- 2026-08-16: 65
- 2026-08-15: 64
- 2026-08-14: 63
- 2026-08-13: 63

## Links

- Remote endpoint: https://www.anahana.com/mcp
- Website: https://www.anahana.com/en/ai-agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-anahana-content-mcp/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-anahana-content-mcp/www.json
- HTML version of this page: https://verifymcp.io/servers/com-anahana-content-mcp/www