Muslim Prayer Reminder MCP
REMOTE · MUSLIM-PRAYER-MCP.NAJETAREQZ.WORKERS.DEV · 2 COMPONENTS
Production-ready Muslim prayer reminder MCP with astronomical precision and theological disclosure.
Available components
Last scanned (23 hours ago)
Scores higher than 62% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Productivity and Notes
Recent critical change
Authorization (3 Oct 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (configure_prayer_preferences). See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- 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 1842 tokens (~307/item across 6 items; 5 tools + 1 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 19 Oct 26 +3
- Schema quality: 362 → 307 ▲ functional
- The server now declares the “prompts” capability functional
- The server now declares the “resources” capability functional
- First check of Schema quality: 100 functional
- Schema quality: excellent → good functional
- New prompt “check_prayer_times_with_disclosure” functional
- New resource “prayer-calculation-guide” functional
- Server version: 1.1.2 → 1.1.3 functional
- 10 Oct 26 −1
- Tool “configure_prayer_preferences” rewrote its description, which is the text the model reads security
- “configure_prayer_preferences” reworded the description of “minuteAdjustments” cosmetic
- 7 Oct 26 +11
- Judged manipulation: unverified → pass ▲ security
- Schema quality: unverified → excellent ▲ functional
- 4 Oct 26 −11
- Judged manipulation: pass → unverified ▼ security
- Stability: 0.97 → pass security
- Tool “configure_prayer_preferences” rewrote its description, which is the text the model reads security
- Schema quality: 220 → 348 ▼ functional
- Schema quality: excellent → unverified ▼ functional
- Server version: 1.1.0 → 1.1.2 functional
- “configure_prayer_preferences” added an optional parameter “clearFixedLocation” cosmetic
- “get_next_prayer” reworded the description of “city” cosmetic
- “get_next_prayer” reworded the description of “timezone” cosmetic
- “get_next_prayer” reworded the description of “userId” cosmetic
- “get_prayer_preferences” reworded the description of “userId” cosmetic
- “get_prayer_status” reworded the description of “city” cosmetic
- “get_prayer_status” reworded the description of “timezone” cosmetic
- “get_prayer_status” reworded the description of “userId” cosmetic
- “get_today_prayer_times” reworded the description of “city” cosmetic
- “get_today_prayer_times” reworded the description of “timezone” cosmetic
- “get_today_prayer_times” reworded the description of “userId” cosmetic
- “configure_prayer_preferences” reworded the description of “exactWindowMinutes” cosmetic
- “configure_prayer_preferences” reworded the description of “fixedCity” cosmetic
- “configure_prayer_preferences” reworded the description of “locationMode” cosmetic
- “configure_prayer_preferences” reworded the description of “userId” cosmetic
- 3 Oct 26 +4
- Authorization: partial → fail ▼ critical
- Judged manipulation: fail → pass ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “configure_prayer_preferences” rewrote its description, which is the text the model reads security
- Tool “configure_prayer_preferences” is now declared destructive security
- Schema quality: 191 → 220 ▼ functional
- Schema quality: poor → excellent functional
- Server version: 1.0.1 → 1.1.0 functional
- “get_next_prayer” added an optional parameter “city” cosmetic
- “get_prayer_status” added an optional parameter “city” cosmetic
- “get_today_prayer_times” added an optional parameter “city” cosmetic
- 2 Oct 26 −10
- Judged manipulation: pass → fail ▼ security
- Schema quality: good → poor functional
- Server version: 1.0.0 → 1.0.1 functional
- “get_today_prayer_times” added an optional parameter “userId” cosmetic
- “get_next_prayer” added an optional parameter “userId” cosmetic
- “get_prayer_status” added an optional parameter “userId” cosmetic
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 4 Nov 2026 · Probed https://muslim-prayer-mcp.najetareqz.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=najetareqz.workers.dev | CN=WE1,O=Google Trust Services,C=US | 10 Oct 2026 | 8 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 8990e0541dd2c920e65a2fb5474b580 |
| SANs: najetareqz.workers.dev, *.najetareqz.workers.dev | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of muslim-prayer-mcp.najetareqz.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://muslim-prayer-mcp.najetareqz.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://muslim-prayer-mcp.najetareqz.workers.dev/mcp | Inconclusive | 406 |
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 ~594
Updates persistent prayer preferences, overwriting supplied settings while preserving omitted settings. Setting fixedCity replaces stored fixedCoordinates and stores the canonical city timezone; contradictory timezones are rejected; 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. Combined fixed-location calculation settings are validated for the current and next local day before saving. Invalid combinations preserve the previous preferences. Auto-travel chronology is checked when a query supplies its location. 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. Omitted updates preserve the saved value; if unset, the service default is 20 minutes unless the operator overrides it. |
| 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: fixed uses saved location; auto_travel requires the caller to supply current city or coordinates/timezone on each query and never uses IP geolocation. |
| madhab | string | – | Jurisprudential Asr shadow calculation: Shafi or Hanafi |
| minuteAdjustments | object | – | Custom per-prayer minute offsets (-60 to +60). For fixed locations, combined settings must preserve timetable chronology for the current and next local day before saving; auto-travel offsets are vali… |
| 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 ~316
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. Must agree with the city or be compatible with the coordinate timezone lookup. |
| 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 ~333
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. Must agree with the city or be compatible with the coordinate timezone lookup. |
| 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 | yes | Mandatory theological transparency notice; detailed provenance is at top level |
| 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 ~345
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. Must agree with the city or be compatible with the coordinate timezone lookup. |
| 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 is a hosted endpoint at https://muslim-prayer-mcp.najetareqz.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · muslim-prayer-mcp.najetareqz.workers.dev
claude mcp add --transport http tareq7-muslim-prayer-mcp 'https://muslim-prayer-mcp.najetareqz.workers.dev/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 hosted endpoint (https://muslim-prayer-mcp.najetareqz.workers.dev/mcp).
Is the Muslim Prayer Reminder MCP server safe to use?
Muslim Prayer Reminder MCP scores 74 out of 100 on VerifyMCP. 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,648 tokens of context every time the server is loaded.
Does the Muslim Prayer Reminder MCP server require authentication?
No. We connected to Muslim Prayer Reminder MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.