MCP Risk

Directory / server

com.asksakina/islamic-knowledge

This directory entry reports an automated security scan of com.asksakina/islamic-knowledge, scanned 2026-07-28. Trust grade C rates provenance, transport, known vulnerabilities and instruction integrity; capability risk is reported separately, not folded into the grade.

registry.modelcontextprotocol.io, scanned 2026-07-28, tool surface via package-source

C 76/100 permalink

Automated checks

StatusCheckPolicyResult
PASS Listed on the official MCP registry §1.1
Listed on registry.modelcontextprotocol.io as com.asksakina/islamic-knowledge. 1 finding
  • Registry entry: com.asksakina/islamic-knowledge ↗
FAIL Source repository is public and maintained §1.2

Claimed source repository does not exist (or is private).
WARN Published package is consistent and attested §1.3
Minor integrity gaps: no npm provenance attestation. 6 findings
  • Package: @asksakina/islamic-knowledge-mcp@1.3.0 ↗
  • Ecosystem: npm
  • Age: 79 days
  • Weekly downloads: 84
  • Repo field matches source repo: true
  • Build-provenance attestation: absent
PASS Tool surface is inspectable and proportionate §2.1–§2.4
Package source scanned. Capabilities detected: filesystem, network-egress. Reported as capability risk (§2.4); whether each is essential to the server's stated purpose is §2.3 and remains a manual judgement. 7 findings
  • filesystem (filesystem write/delete): dist/data/duas.js
  • filesystem (fs module import): dist/data/duas.js
  • network-egress (outbound network calls): dist/data/quran.js
  • filesystem (fs module import): dist/logging/request-logger.js
  • network-egress (outbound network calls): dist/server.js
  • network-egress (http module import): dist/server.js
  • Detected capabilities: filesystem, network-egress
PASS HTTPS-only endpoint §3.1
Endpoint uses HTTPS. 1 finding
  • Endpoint: https://sakina-mcp.fly.dev/sse
UNVERIFIABLE Authentication required §3.2

Endpoint unreachable: The operation was aborted
WARN OAuth protected-resource metadata published §3.3
No protected-resource metadata found - clients cannot discover the authorization server per spec. 1 finding
  • Checked: https://sakina-mcp.fly.dev/.well-known/oauth-protected-resource
PASS No known vulnerabilities (OSV.dev) §4.1

No advisories on record for @asksakina/islamic-knowledge-mcp @1.3.0 (npm).
PASS Server-supplied instructions free of poisoning indicators §5.1–§5.4

No poisoning indicators found across 13 server-supplied text item(s).
What this grade covers
  • Provenance & supply-chain integrity (§1)
  • Tool surface & capability risk (§2)
  • Transport & authentication (§3)
  • Known CVEs via OSV.dev (§4)
  • Instruction/tool poisoning patterns (§5)

Limitations: pattern-based only (no semantic injection detection), static npm analysis (live server instructions not retrieved for package-only scans), single-server scope (no cross-server toxic flow analysis). See the full policy.

Methodology: MCP Server Security Policy. Unfamiliar term? See the glossary.