AskSakina Islamic Knowledge MCP — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Follow-up value is specific to AskSakina curated Islamic knowledge with presentation contracts: Do structured review and presentation constraints preserve school attribution and the qualified-scholar limitation?

Reviewed Oct 5, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Structured Islamic reference records for Quran, du'a and Names of Allah with explicit presentation/disclaimer contracts.

What we know

Reference-library MCP whose responses include provenance/presentation metadata and educational disclaimers. The product explicitly positions itself as a record source rather than a religious advisor and says its specialist-AI review is not a substitute for a qualified scholar.

Maintenance / activity evidence

@asksakina/islamic-knowledge-mcp 2.0.0 published 2026-09-29T15:32:59.347Z

Tracking evidence observed Oct 5, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
Read-only reference-library access.
Authentication not yet verified.
Sensitive access: Religious questions can be sensitive personal context even though server data is public

Low technical authority; primary risk is misrepresenting religious reference material.

Full authority, access and evidence limits are available in Review context and Access & risk.

All limitations / Review context

Do structured review and presentation constraints preserve school attribution and the qualified-scholar limitation?

The bounded review of the publisher's documented AskSakina curated Islamic knowledge with presentation contracts and release notices identified no disclosed material condition preventing an accurately scoped public tracking entry. The resource's operational permissions remain uncertainty; this assessment does not certify installation safety.

Low technical authority; primary risk is misrepresenting religious reference material.
Read-only reference-library access.
Public/curated religious reference data; no user-account mutation.
Sensitive access: Religious questions can be sensitive personal context even though server data is public
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited.
Documented tool authority and any remote data handling must be checked before installation or use.
Tool inventory, client matrix and permissions completeness were not requirements for this Radar tracking review.
Not a substitute for a qualified scholar.
Responses include presentation constraints that the calling agent must honor.
Review methodology and religious interpretation remain domain-sensitive.
Source repository identity changed across earlier releases; current package links the maintained mirror/repo.
Preserve the explicit 'reference library, not advisor / not a substitute for qualified scholar' boundary.

Original activity observations

@asksakina/islamic-knowledge-mcp 2.0.0 published 2026-09-29T15:32:59.347Z

Technical identity

npm/@asksakina/islamic-knowledge-mcp

Exact implementation source: https://www.npmjs.com/package/@asksakina/islamic-knowledge-mcp ↗
Reviewed resource type: MCP Server
Repository identity: yserrag/asksakina-mcp
Package identity: npm:@asksakina/islamic-knowledge-mcp
Service endpoint: https://sakina-mcp.fly.dev/mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 5, 2026 · Latest source observation Oct 8, 2026

Package registry ↗
@asksakina/islamic-knowledge-mcp
Recorded package identity, distribution or download evidence.
Includes references whose attribution is not established.
Evidence source ↗
www.asksakina.com/mcp
Source material retained for this review.
Includes references whose attribution is not established.
GitHub repository ↗
yserrag/asksakina-mcp
Repository reference; implementation attribution is not established for every document.
Includes references whose attribution is not established.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented install or connect path; prerequisites and any extra host configuration remain required.
publisher install or stdio launch · retained baseline · Publisher instructions
npx -y @asksakina/islamic-knowledge-mcp --stdio
Configure / authenticate
MCP100 setup guide
Use `--stdio` when launched by Claude Desktop/Code/Cursor; without it package starts an HTTP server, NOT stdio. HTTP deployment uses POST /mcp and GET /health.
Previously reviewed client configuration / prerequisites: STDIO requires --stdio explicitly: npx -y @asksakina/islamic-knowledge-mcp --stdio. Without flag, package launches HTTP server, default port 3030; do not use that command as an stdio client entry.
Check connection
Suggested check
Verify `get_quran_verse` via client; HTTP GET /health is only liveness.
Remove / uninstall / revoke
MCP100 setup guide
If registered in Claude Code under the name `sakina`, remove the client entry with `claude mcp remove sakina`. For other MCP hosts remove the matching server/connector in that host’s MCP settings. Remove a globally installed software package separately if applicable; this does not delete data or revoke a service credential.
Client removal, software uninstall, persistent-data deletion and credential revocation are separate actions.
Remove client registration · Claude Code only · MCP100 composed guide
claude mcp remove sakina

Official Documentation & Sources

https://www.npmjs.com/package/@asksakina/islamic-knowledge-mcp ↗

What it does

Reference-library MCP whose responses include provenance/presentation metadata and educational disclaimers. The product explicitly positions itself as a record source rather than a religious advisor and says its specialist-AI review is not a substitute for a qualified scholar.

Capability: Files & Knowledge
Resource type: MCP Server
Industry: Education & Research
Best fit: Structured Islamic reference records for Quran, du'a and Names of Allah with explicit presentation/disclaimer contracts.

Representative uses

Look up Quranic verses
Retrieve curated/authenticated du'a records
Look up Names of Allah
Read canonical `sakina://about` directives/resource

Limitations

Not a substitute for a qualified scholar.
Responses include presentation constraints that the calling agent must honor.
Review methodology and religious interpretation remain domain-sensitive.
Source repository identity changed across earlier releases; current package links the maintained mirror/repo.
Preserve the explicit 'reference library, not advisor / not a substitute for qualified scholar' boundary.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Not documented in the reviewed sources
Permissions: Read-only reference-library access.
Data handling: Public/curated religious reference data; no user-account mutation.
Cost: free
Risk and cautions: Low technical authority; primary risk is misrepresenting religious reference material.

Access scope and cautions

Write actions: None in the reviewed inventory
Sensitive access: Religious questions can be sensitive personal context even though server data is public
Risk level: low

FAQ

Based on reviewed evidence as of 2026-10-08. Watchlist tracking is not a recommendation or a security certification.

Which tasks are documented for this implementation?

The reviewed tasks include: Look up Quranic verses; Retrieve curated/authenticated du'a records; Look up Names of Allah; Read canonical `sakina://about` directives/resource.

What setup and authentication are documented?

Recorded installation/entrypoint step: npx -y @asksakina/islamic-knowledge-mcp. Recorded endpoint: https://sakina-mcp.fly.dev/mcp. Recorded transport: stdio, streamable_http. Prerequisites: MCP client. These are the documented setup details, not a claim that installation or client compatibility was independently tested. Authentication: No API key required for documented public MCP paths.

Can it modify data or perform write operations?

The reviewed inventory lists no write actions. An empty inventory alone does not establish read-only authority. Recorded permission boundary: Read-only reference-library access.

What data-handling boundary should I consider?

Public/curated religious reference data; no user-account mutation. Recorded sensitive-access context: Religious questions can be sensitive personal context even though server data is public.

What limitations and risks should I check before use?

Low technical authority; primary risk is misrepresenting religious reference material. Not a substitute for a qualified scholar. Responses include presentation constraints that the calling agent must honor. Review methodology and religious interpretation remain domain-sensitive. Source repository identity changed across earlier releases; current package links the maintained mirror/repo. reference library, not advisor / not a substitute for qualified scholar. Runtime behavior, dependencies and undisclosed vulnerabilities were not independently audited. Documented tool authority and any remote data handling must be checked before installation or use.