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.

AskSakina Islamic Knowledge

NPM · @ASKSAKINA/ISLAMIC-KNOWLEDGE-MCP · 2 COMPONENTS

Curated Islamic MCP: Quran (Arabic + Pickthall), 440 du'as, 99 Names, crisis-aware.

0 this week 87 Trust /100

Last scanned (14 hours ago)

Scores higher than 81% of npm servers

Category Education and Research

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security80
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 44 of 120 dependencies flagged as unhealthy (3 deprecated). View diagnostics → Partial
Provenance & Transparency84
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to yserrag/asksakina-mcp). View diagnostics → Pass
  • Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
  • Actively maintained (last published 17 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1403 tokens (~127/item across 11 items; 4 tools + 7 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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.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 6 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 (15)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • License in Provenance & TransparencyLicence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 20 Nov 26 0
    • Stability: 0.97 → pass security
  • 19 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Nov 26 0
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

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

  • 9 Nov 26 +6
    • Source repository: unverified → pass ▲ security
  • 8 Nov 26 −5
    • Provenance: pass → unverified ▼ security
  • 7 Nov 26 +1

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

  • 5 Nov 26 +1
    • CVE-2026-118764 no longer affects this package ▲ security
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 21 Nov 2026 · Analysed npm/@asksakina/islamic-knowledge-mcp@2.7.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo yserrag/asksakina-mcp
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/yserrag/asksakina-mcp/.github/workflows/publish.yml@refs/tags/v2.7.0
Rekor log index 3671749029
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:ac0ef962e561c63998b7ab49ffa27999bfcc3af7920076d6aa4b3c7c0732b76ee3653d06e1ed7999b1d06f1336da299b79ac82531ac6d2e5a4290048a

Background: How many MCP packages publish verified provenance →

Vulnerabilities 7 findings
ID CVE Severity Vector Fix available
GHSA-h3mg-xc3c-68pw CVE-2026-101911 medium yes
GHSA-j6r3-76f7-8jcv CVE-2026-101912 medium yes
GHSA-mwp4-54f8-5fhr CVE-2026-69192 high yes
GHSA-rpw4-54j3-4h4q CVE-2026-101913 medium yes
GHSA-rxp7-6hxx-x8q5 CVE-2026-111997 medium yes
GHSA-v2v4-37r5-5v8g CVE-2026-42338 medium yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 120 packages
Packages resolved 120
Deprecated 3
Stale 42
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~781 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
find_verses ~158

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

NameTypeReqDescription
audiencestring–Optional: curious, revert or practising, from the user's own self-description only. Teaching context attaches whenever an entry exists; omit when the audience is unknown.
limitinteger–Number of verses to return; default 5, max 10.
localestring–Selects the in-country crisis resources if one is needed; defaults to "en". Translations are Pickthall English.
querystringyesTopic or keyword, e.g. 'patience', 'grief', 'gratitude', 'hope'.
NameTypeReqDescription
_sakina_metaobjectyes–
content–yes–
crisis_resourceobject–Present this block exactly, before anything else, and add nothing religious when content_type is crisis_resource_only.

No examples provided.

get_dua ~291

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.

NameTypeReqDescription
audiencestring–Optional: curious, revert or practising, from the user's own self-description only. Teaching context attaches whenever an entry exists; omit when the audience is unknown.
contextstring–Life context to match against. Examples: 'anxiety', 'morning', 'travel', 'forgiveness', 'gratitude'. Send this or id, not both.
idstring–A du'a id taken from a related reference in an earlier response. Send this or context, not both.
limitinteger–Number of du'as to return for a context; default 3, max 10. The response says how many more exist. Ignored with id.
localestring–Locale; defaults to "en". Du'a records are English for every locale; a crisis resource is given in the request locale, or, with no locale or "en", in the language of the crisis words (Indonesian, Urd…
offsetinteger–Number of du'as to skip before the page, for paging with limit; default 0. Ignored with id, and on the bereaved set.
NameTypeReqDescription
_sakina_metaobjectyes–
content–yes–
crisis_resourceobject–Present this block exactly, before anything else, and add nothing religious when content_type is crisis_resource_only.

No examples provided.

get_name_of_allah ~162

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.

NameTypeReqDescription
audiencestring–Optional: curious, revert or practising, from the user's own self-description only. Teaching context attaches whenever an entry exists; omit when the audience is unknown.
localestring–Locale for meaning + reflection. Defaults to "en"; "tr" returns the English meaning and reflection.
namestring–Name input — Latin transliteration ('Al-Hakam'), Arabic ('الحكم'), or English meaning ('The Judge').
numberinteger–Number of the Name in the canonical list, 1-99.
NameTypeReqDescription
_sakina_metaobjectyes–
content–yes–
crisis_resourceobject–Present this block exactly, before anything else, and add nothing religious when content_type is crisis_resource_only.

No examples provided.

get_quran_verse ~170

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.

NameTypeReqDescription
audiencestring–Optional: curious, revert or practising, from the user's own self-description only. Teaching context attaches whenever an entry exists; omit when the audience is unknown.
ayahintegeryesAyah (verse) number within the surah
localestring–Translation locale; defaults to "en" (Pickthall). Urdu, Indonesian and Turkish translations are not yet available: "ur", "id" and "tr" return Pickthall English with a note.
surahintegeryesSurah number, 1-114
NameTypeReqDescription
_sakina_metaobjectyes–
content–yes–
crisis_resourceobject–Present this block exactly, before anything else, and add nothing religious when content_type is crisis_resource_only.

No examples provided.

Install

How do I install the AskSakina Islamic Knowledge MCP server?

AskSakina Islamic Knowledge runs locally as an npm package, launched with npx -y @asksakina/islamic-knowledge-mcp --stdio. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

npm · @asksakina/islamic-knowledge-mcp

# add to Claude Code
claude mcp add com-asksakina-islamic-knowledge -- npx -y @asksakina/islamic-knowledge-mcp --stdio
Common questions

What is the AskSakina Islamic Knowledge MCP server?

AskSakina Islamic Knowledge is an MCP server listed in the public MCP registry as com.asksakina/islamic-knowledge. Curated Islamic MCP: Quran (Arabic + Pickthall), 440 du'as, 99 Names, crisis-aware. This page covers its npm package (@asksakina/islamic-knowledge-mcp).

Is the AskSakina Islamic Knowledge MCP server safe to use?

AskSakina Islamic Knowledge scores 87 out of 100 on VerifyMCP. We recorded 7 known advisories against it as of 21 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 AskSakina Islamic Knowledge MCP server expose?

AskSakina Islamic Knowledge exposes 4 tools: get_quran_verse, get_dua, get_name_of_allah, find_verses. Their descriptions and schemas cost roughly 781 tokens of context every time the server is loaded.

Is the AskSakina Islamic Knowledge MCP server still maintained?

AskSakina Islamic Knowledge is still listed as active in the MCP registry. We last reached this channel on 21 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 AskSakina Islamic Knowledge MCP server?

VerifyMCP ran 15 checks on AskSakina Islamic Knowledge, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about AskSakina Islamic Knowledge: License. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.