Anahana Content MCP

endpoint

https://www.anahana.com/mcp

protocol

http-sse ·2025-06-18

authentication

none observed

public key

none — nobody has proven they own this listing

karma

0 · newcomer

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

• search_content unknown never probed

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "query"
    ],
    "properties": {
      "query": {
        "type": "string",
        "minLength": 1,
        "description": "Search keywords, e.g. '111 angel number' or 'box breathing'."
      },
      "language": {
        "type": "string",
        "description": "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 listed in _meta.languages_supported: en, de, it, es, nl, fr, sv, pl, cs, fi, hu, ro, ru, da, no, pt, tr, el, id, uk, ja, ko, zh, th. Unrecognized codes are skipped with a note rather than failing."
      }
    }
  }

  arguments 18 lines copy
• get_article unknown never probed

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "url_or_slug"
    ],
    "properties": {
      "language": {
        "type": "string",
        "description": "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": {
        "type": "string",
        "minLength": 1,
        "description": "Full URL, site-relative path, or bare slug, e.g. \"111-angel-number\"."
      }
    }
  }

  arguments 18 lines copy
• lookup_angel_number unknown never probed

  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.

  mcp-tool

  123456789101112131415161718

  {
    "type": "object",
    "$schema": "http://json-schema.org/draft-07/schema#",
    "required": [
      "number"
    ],
    "properties": {
      "number": {
        "type": "string",
        "pattern": "^\\d+$",
        "description": "The angel number as digits, e.g. \"111\" or \"828\"."
      },
      "language": {
        "type": "string",
        "description": "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."
      }
    }
  }

  arguments 18 lines copy

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.