Muslim Prayer Reminder MCP
NPM · MUSLIM-PRAYER-MCP · 2 COMPONENTS
Production-ready Muslim prayer reminder MCP with astronomical precision and theological disclosure.
Available components
Last scanned (3 hours ago)
Scores higher than 55% of npm servers
Category Productivity and Notes
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 Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 32 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability59
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1669 tokens (~333/item across 5 items; 5 tools + 0 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 Management67
- Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 5 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Security disclosure: unverified → pass ▲ functional
- 24 Oct 26 0
- Security disclosure: pass → unverified ▼ functional
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
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 5 Nov 2026 · Analysed npm/muslim-prayer-mcp@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
configure_prayer_preferences Configure User Prayer Preferences ~472
Updates persistent prayer preferences, overwriting supplied settings while preserving omitted settings. Setting fixedCity replaces stored fixedCoordinates and clears the stored timezone unless supplied; setting fixedCoordinates replaces stored fixedCity. Can disable reminders. Fixed mode requires a supported fixedCity or fixedCoordinates with timezone; new coordinates require timezone in the same request. clearFixedLocation removes saved location and timezone and defaults to auto_travel. Previous values are not retained for undo.
| Name | Type | Req | Description |
|---|---|---|---|
| calculationMethod | string | – | Islamic prayer calculation authority |
| clearFixedLocation | boolean | – | Remove stored fixedCity, fixedCoordinates and timezone. Switches to auto_travel unless locationMode is supplied. Cannot combine with a new fixed location/timezone. |
| enabled | boolean | – | Whether prayer reminders are enabled |
| exactWindowMinutes | integer | – | Duration in minutes for exact_window mode |
| fixedCity | string | – | Supported cities: makkah, madinah, riyadh, cairo, gaza, jerusalem, alquds, ramallah, hebron, nablus, rafah, khanyunis, dubai, abudhabi, kuwait, doha, amman, istanbul, london, paris, newyork, toronto,… |
| fixedCoordinates | object | – | Fixed geographical coordinates |
| highLatitudeRule | string | – | High latitude twilight adjustment rule |
| locale | string | – | Language for reminder text: en or ar |
| locationMode | string | – | Location strategy: auto_travel or fixed |
| madhab | string | – | Jurisprudential Asr shadow calculation: Shafi or Hanafi |
| minuteAdjustments | object | – | Custom per-prayer minute offsets (-60 to +60) |
| reminderMode | string | – | Reminder display policy: prayer_window, exact_window, persistent |
| timezone | string | – | IANA timezone identifier (e.g. Asia/Riyadh, Europe/London) |
| userId | string | yes | Nonblank user identifier; at most 256 UTF-8 bytes and 256 characters. Whitespace in nonblank identifiers is preserved. |
| Name | Type | Req | Description |
|---|---|---|---|
| preferences | object | yes | – |
| success | boolean | yes | Whether configuration succeeded |
No examples provided.
get_next_prayer Get Upcoming Prayer and Countdown ~309
Returns the immediate next prayer name, scheduled time, authority calculation method, and remaining countdown in minutes. MANDATORY: The LLM must always explicitly disclose to the user which calculation authority method was used and why it was selected (see authorityNotice in response).
| Name | Type | Req | Description |
|---|---|---|---|
| calculationMethod | string | – | Optional calculation authority override (auto-resolved from location by default) |
| city | string | – | Supported cities: makkah, madinah, riyadh, cairo, gaza, jerusalem, alquds, ramallah, hebron, nablus, rafah, khanyunis, dubai, abudhabi, kuwait, doha, amman, istanbul, london, paris, newyork, toronto,… |
| latitude | number | – | Optional explicit latitude override |
| longitude | number | – | Optional explicit longitude override |
| madhab | string | – | Optional Asr shadow jurisprudence override (Shafi or Hanafi) |
| timezone | string | – | IANA timezone; required in the same request when latitude/longitude are supplied. Explicit overrides select the display timezone. |
| userId | string | – | Nonblank user identifier; at most 256 UTF-8 bytes and 256 characters. Whitespace in nonblank identifiers is preserved. |
| Name | Type | Req | Description |
|---|---|---|---|
| authorityDescription | string | – | – |
| authorityNotice | object | – | – |
| calculationDetails | object | – | – |
| calculationMethod | string | yes | Active calculation authority |
| currentLocalDate | string | yes | Current local date YYYY-MM-DD |
| highLatitudeAdjustment | object | – | – |
| madhab | string | yes | Active Asr jurisprudence |
| minuteAdjustments | object | – | – |
| nextPrayer | string | yes | Name of the upcoming prayer |
| nextPrayerAtUtc | string | yes | UTC timestamp of the upcoming prayer |
| nextPrayerLocalTime | string | yes | Formatted local time HH:mm |
| remainingMinutes | integer | yes | Minutes remaining until prayer start |
| selectionReason | string | – | – |
| timezone | string | yes | Resolved IANA timezone |
No examples provided.
get_prayer_preferences Retrieve Stored Prayer Preferences ~60
Returns the currently active calculation settings and preferences for a user. Read-only operation.
| Name | Type | Req | Description |
|---|---|---|---|
| userId | string | yes | Nonblank user identifier; at most 256 UTF-8 bytes and 256 characters. Whitespace in nonblank identifiers is preserved. |
| Name | Type | Req | Description |
|---|---|---|---|
| calculationMethod | string | – | – |
| enabled | boolean | – | – |
| exactWindowMinutes | number | – | – |
| fixedCity | string | – | – |
| fixedCityConfigured | boolean | yes | – |
| fixedCoordinatesConfigured | boolean | yes | – |
| highLatitudeRule | string | – | – |
| locale | string | – | – |
| locationMode | string | – | – |
| madhab | string | – | – |
| message | string | – | – |
| minuteAdjustments | object | – | – |
| reminderMode | string | – | – |
| timezone | string | – | – |
| updatedAtUtc | string | – | – |
No examples provided.
get_prayer_status Check Muslim Prayer Due Status ~326
Checks if a Muslim obligatory prayer (Fajr, Dhuhr, Asr, Maghrib, Isha) is currently due for the user location and returns active reminder details. MANDATORY: The LLM must always explicitly disclose to the user which calculation authority method was used and why it was selected (see authorityNotice in response).
| Name | Type | Req | Description |
|---|---|---|---|
| calculationMethod | string | – | Optional calculation authority override (auto-resolved from location by default) |
| city | string | – | Supported cities: makkah, madinah, riyadh, cairo, gaza, jerusalem, alquds, ramallah, hebron, nablus, rafah, khanyunis, dubai, abudhabi, kuwait, doha, amman, istanbul, london, paris, newyork, toronto,… |
| latitude | number | – | Optional explicit latitude override |
| longitude | number | – | Optional explicit longitude override |
| madhab | string | – | Optional Asr shadow jurisprudence override (Shafi or Hanafi) |
| timezone | string | – | IANA timezone; required in the same request when latitude/longitude are supplied. Explicit overrides select the display timezone. |
| userId | string | – | Nonblank user identifier; at most 256 UTF-8 bytes and 256 characters. Whitespace in nonblank identifiers is preserved. |
| Name | Type | Req | Description |
|---|---|---|---|
| authorityDescription | string | – | Description of the calculation authority |
| authorityNotice | object | – | Mandatory theological transparency notice |
| calculationDetails | object | – | – |
| calculationMethod | string | yes | Active calculation authority |
| expiresAtUtc | string | – | UTC expiration time of the active prayer window |
| highLatitudeAdjustment | object | – | – |
| localDate | string | yes | Current local date in YYYY-MM-DD |
| madhab | string | yes | Active Asr jurisprudence |
| minuteAdjustments | object | – | Applied minute adjustments |
| nextPrayer | string | yes | The name of the next upcoming prayer |
| nextPrayerAtUtc | string | yes | UTC timestamp of the next upcoming prayer |
| nextPrayerCalculation | object | – | Adjustment disclosure for the actual schedule of the next event, including tomorrow |
| prayer | string | – | The name of the currently due prayer if applicable |
| prayerWindowExpiresAtUtc | string | – | End of the active prayer period; same boundary as legacy expiresAtUtc |
| reminderDue | boolean | yes | Whether a prayer is currently due for reminder |
| reminderText | string | – | Localized reminder message |
| reminderWindowExpiresAtUtc | string | – | Reminder eligibility end; exact_window is capped by the prayer period boundary. Fields appear when a reminder is emitted. |
| selectionReason | string | – | Reason for authority selection |
| startedAtUtc | string | – | UTC start time of the active prayer window |
| timezone | string | yes | Resolved IANA timezone |
No examples provided.
get_today_prayer_times Get Full Daily Prayer Timetable ~338
Retrieves today prayer timetable (Fajr, Sunrise, Dhuhr, Asr, Maghrib, Isha) in UTC and formatted local time. MANDATORY: The LLM must always explicitly disclose to the user which calculation authority method was used and why it was selected (see authorityNotice in response).
| Name | Type | Req | Description |
|---|---|---|---|
| calculationMethod | string | – | Optional calculation authority override (auto-resolved from location by default) |
| city | string | – | Supported cities: makkah, madinah, riyadh, cairo, gaza, jerusalem, alquds, ramallah, hebron, nablus, rafah, khanyunis, dubai, abudhabi, kuwait, doha, amman, istanbul, london, paris, newyork, toronto,… |
| date | string | – | Date in YYYY-MM-DD format (defaults to today) |
| latitude | number | – | Optional explicit latitude override |
| longitude | number | – | Optional explicit longitude override |
| madhab | string | – | Optional Asr shadow jurisprudence override (Shafi or Hanafi) |
| timezone | string | – | IANA timezone; required in the same request when latitude/longitude are supplied. Explicit overrides select the display timezone. |
| userId | string | – | Nonblank user identifier; at most 256 UTF-8 bytes and 256 characters. Whitespace in nonblank identifiers is preserved. |
| Name | Type | Req | Description |
|---|---|---|---|
| authorityDescription | string | – | – |
| authorityNotice | object | – | – |
| calculationDetails | object | – | – |
| calculationMethod | string | yes | Active calculation authority |
| highLatitudeAdjustment | object | – | – |
| localDate | string | yes | Local schedule date YYYY-MM-DD |
| madhab | string | yes | Active Asr jurisprudence |
| minuteAdjustments | object | – | – |
| selectionReason | string | – | – |
| timesLocal | object | yes | – |
| timesUtc | object | yes | – |
| timezone | string | yes | Resolved IANA timezone |
No examples provided.
How do I install the Muslim Prayer Reminder MCP server?
Muslim Prayer Reminder MCP runs locally as an npm package, launched with npx -y muslim-prayer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · muslim-prayer-mcp
claude mcp add tareq7-muslim-prayer-mcp -- npx -y muslim-prayer-mcp
What is the Muslim Prayer Reminder MCP server?
Muslim Prayer Reminder MCP is listed in the public MCP registry as io.github.tareq7/muslim-prayer-mcp. Production-ready Muslim prayer reminder MCP with astronomical precision and theological disclosure. This page covers its npm package (muslim-prayer-mcp).
Is the Muslim Prayer Reminder MCP server safe to use?
Muslim Prayer Reminder MCP scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Muslim Prayer Reminder MCP server expose?
Muslim Prayer Reminder MCP exposes 5 tools: get_prayer_status, get_today_prayer_times, get_next_prayer, configure_prayer_preferences, get_prayer_preferences. Their descriptions and schemas cost roughly 1,505 tokens of context every time the server is loaded.
Is the Muslim Prayer Reminder MCP server still maintained?
Muslim Prayer Reminder MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Muslim Prayer Reminder MCP server under?
Muslim Prayer Reminder MCP declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.