Skip to content
AskSakina logo

AskSakina MCP server

Which MCP servers are AskSakina'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-20

← Back to AskSakina

Whose server it is
  • Registry namecom.asksakina/islamic-knowledgeverified in the MCP registry

The registry name sits under asksakina.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-20
  • Stateanswerschecked 2026-10-20
  • Tools4
  • Server calls itselfsakina-islamic-knowledge
  • Server version2.1.1
  • Protocol version2025-06-18

On 2026-10-20 the server answered initialize and tools/list without a sign-in. First answer in 230 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: Check prayer times for daily salah; Scan products to check whether they are halal.

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.

Measured dailydaily checks: 8, the first on 2026-10-20
  • INITE MCP score67 of 100answers 100 · does the job 0 · definitions 83 · context 100 · use 52 · connects 100
  • What an agent can do with it0 of 2 use cases
  • Use415 npm downloads a week
  • Answered100% of days8 of 8 daily checks
  • Median first answer266 ms
  • Space in an agent's context≈ 1,195 tokensthe definitions of all its tools (4), which an agent carries on every turn
  • Tool definitionsB · 83 of 100
  • Typed results4 of 4 toolsdeclared outputSchema: results come typed, read once
  • Not saying whether it only reads or can destroy: 4 of 4

What an agent can do with it

  • cannot · Check prayer times for daily salah
  • not sure · Read duas and adhkar for daily reflection
  • cannot · Scan products to check whether they are halal

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 →

Tools it offers4 tools · read 2026-10-20
  • get_quran_verse

    Returns one Quran verse by surah and ayah number: Tanzil Uthmani Arabic and Pickthall English, with citation. Quote the Arabic exactly; do not paraphrase either text.

  • get_dua

    Returns du'as from a curated du'a corpus for a life context (e.g. anxiety, travel, gratitude), with source and grading where recorded. Show any crisis_resource block verbatim.

  • get_name_of_allah

    Returns one of the 99 Names of Allah by number (1-99) or by name: Arabic, transliteration, meaning, reflection and Quranic references. Quote the Arabic exactly.

  • find_verses

    Searches AskSakina's thematic index for Quran verses by topic keyword. Returns reference, Tanzil Arabic and Pickthall English. Quote the Arabic exactly.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "islamic-knowledge": {
      "type": "http",
      "url": "https://sakina-mcp.fly.dev/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http asksakina https://sakina-mcp.fly.dev/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://sakina-mcp.fly.dev/mcp as a custom connector in the settings.

Also shipped through: npm

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.