# Muslim Prayer Reminder MCP (remote · muslim-prayer-mcp.najetareqz.workers.dev)

Production-ready Muslim prayer reminder MCP with astronomical precision and theological disclosure.

- Trust score: 73/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- remote · `muslim-prayer-mcp.najetareqz.workers.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/tareq7-muslim-prayer-mcp/muslim-prayer-mcp.md), [page](https://verifymcp.io/servers/tareq7-muslim-prayer-mcp/muslim-prayer-mcp)
- npm · `muslim-prayer-mcp`: 39/100, [markdown](https://verifymcp.io/servers/tareq7-muslim-prayer-mcp/muslim-prayer-mcp-2.md), [page](https://verifymcp.io/servers/tareq7-muslim-prayer-mcp/muslim-prayer-mcp-2)

## Channel facts

- Endpoint: `https://muslim-prayer-mcp.najetareqz.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 879 tokens (~175/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 53/100
  - Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http tareq7-muslim-prayer-mcp 'https://muslim-prayer-mcp.najetareqz.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "tareq7-muslim-prayer-mcp": {
      "url": "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "tareq7-muslim-prayer-mcp": {
      "type": "http",
      "url": "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.tareq7-muslim-prayer-mcp]
url = "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "tareq7-muslim-prayer-mcp": {
      "type": "remote",
      "url": "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add tareq7-muslim-prayer-mcp --url 'https://muslim-prayer-mcp.najetareqz.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  tareq7-muslim-prayer-mcp:
    url: "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "tareq7-muslim-prayer-mcp": {
      "Transport": "http",
      "Url": "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add tareq7-muslim-prayer-mcp -t streamable-http -u 'https://muslim-prayer-mcp.najetareqz.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "tareq7-muslim-prayer-mcp": {
      "type": "http",
      "url": "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 73, +11)

- [security improvement] Judged manipulation: unverified → pass
- [functional improvement] Schema quality: unverified → good

### 2026-09-19 (score 62, −10)

- [security regression] Judged manipulation: pass → unverified
- [functional regression] Schema quality: good → unverified
- [cosmetic] “get_next_prayer” dropped the optional parameter “userId”
- [cosmetic] “get_prayer_status” dropped the optional parameter “userId”
- [cosmetic] “get_today_prayer_times” dropped the optional parameter “userId”

### 2026-09-18 (score 72, +1)

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

### 2026-09-16 (score 71, +1)

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

### 2026-09-14 (score 70, +1)

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

### 2026-09-12 (score 69, +1)

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

### 2026-09-09 (score 68, +1)

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

### 2026-09-07 (score 67, +1)

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

## MCP tools (5)

### `get_prayer_status` (~162 tokens)

Check Muslim Prayer Due Status

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).

Input parameters:

- `calculationMethod` (string): Optional calculation authority override (auto-resolved from location by default)
- `latitude` (number): Optional explicit latitude override
- `longitude` (number): Optional explicit longitude override
- `madhab` (string): Optional Asr shadow jurisprudence override (Shafi or Hanafi)
- `timezone` (string): Optional IANA timezone override (e.g. Asia/Riyadh)

Output parameters:

- `authorityDescription` (string): Description of the calculation authority
- `authorityNotice` (object): Mandatory theological transparency notice
- `calculationMethod` (string): Active calculation authority
- `expiresAtUtc` (string): UTC expiration time of the active prayer window
- `localDate` (string): Current local date in YYYY-MM-DD
- `madhab` (string): Active Asr jurisprudence
- `minuteAdjustments` (object): Applied minute adjustments
- `nextPrayer` (string): The name of the next upcoming prayer
- `nextPrayerAtUtc` (string): UTC timestamp of the next upcoming prayer
- `prayer` (string): The name of the currently due prayer if applicable
- `reminderDue` (boolean): Whether a prayer is currently due for reminder
- `reminderText` (string): Localized reminder message
- `selectionReason` (string): Reason for authority selection
- `startedAtUtc` (string): UTC start time of the active prayer window
- `timezone` (string): Resolved IANA timezone

### `get_today_prayer_times` (~166 tokens)

Get Full Daily Prayer Timetable

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).

Input parameters:

- `calculationMethod` (string): Optional calculation authority override (auto-resolved from location by default)
- `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): Optional IANA timezone override

Output parameters:

- `authorityDescription` (string)
- `authorityNotice` (object)
- `calculationMethod` (string): Active calculation authority
- `localDate` (string): Local schedule date YYYY-MM-DD
- `madhab` (string): Active Asr jurisprudence
- `minuteAdjustments` (object)
- `selectionReason` (string)
- `timesLocal` (object)
- `timesUtc` (object)
- `timezone` (string): Resolved IANA timezone

### `get_next_prayer` (~137 tokens)

Get Upcoming Prayer and Countdown

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).

Input parameters:

- `calculationMethod` (string): Optional calculation authority override (auto-resolved from location by default)
- `latitude` (number): Optional explicit latitude override
- `longitude` (number): Optional explicit longitude override
- `madhab` (string): Optional Asr shadow jurisprudence override (Shafi or Hanafi)
- `timezone` (string): Optional IANA timezone override

Output parameters:

- `authorityDescription` (string)
- `authorityNotice` (object)
- `calculationMethod` (string): Active calculation authority
- `currentLocalDate` (string): Current local date YYYY-MM-DD
- `madhab` (string): Active Asr jurisprudence
- `minuteAdjustments` (object)
- `nextPrayer` (string): Name of the upcoming prayer
- `nextPrayerAtUtc` (string): UTC timestamp of the upcoming prayer
- `nextPrayerLocalTime` (string): Formatted local time HH:mm
- `remainingMinutes` (integer): Minutes remaining until prayer start
- `selectionReason` (string)
- `timezone` (string): Resolved IANA timezone

### `configure_prayer_preferences` (~252 tokens)

Configure User Prayer Preferences

Configures prayer calculation parameters, location behavior (fixed or auto_travel), madhab, reminder mode, and notification language in persistent storage.

Input parameters:

- `calculationMethod` (string): Islamic prayer calculation authority
- `enabled` (boolean): Whether prayer reminders are enabled
- `exactWindowMinutes` (integer): Duration in minutes for exact_window mode
- `fixedCity` (string): Predefined city name for fixed location (e.g. Riyadh, London)
- `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, required): Unique user identifier

Output parameters:

- `preferences` (object)
- `success` (boolean): Whether configuration succeeded

### `get_prayer_preferences` (~37 tokens)

Retrieve Stored Prayer Preferences

Returns the currently active calculation settings and preferences for a user. Read-only operation.

Input parameters:

- `userId` (string, required): Unique user identifier

Output parameters:

- `calculationMethod` (string)
- `enabled` (boolean)
- `exactWindowMinutes` (number)
- `fixedCity` (string)
- `fixedCoordinates` (object)
- `highLatitudeRule` (string)
- `locale` (string)
- `locationMode` (string)
- `madhab` (string)
- `message` (string)
- `minuteAdjustments` (object)
- `reminderMode` (string)
- `timezone` (string)
- `updatedAtUtc` (string)
- `userId` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/tareq7-muslim-prayer-mcp/muslim-prayer-mcp#diagnostics

## Score history

- 2026-09-20: 73
- 2026-09-19: 62
- 2026-09-18: 72
- 2026-09-17: 71
- 2026-09-16: 71
- 2026-09-15: 70
- 2026-09-14: 70
- 2026-09-13: 69
- 2026-09-12: 69
- 2026-09-11: 68
- 2026-09-10: 68
- 2026-09-09: 68
- 2026-09-08: 67
- 2026-09-07: 67
- 2026-09-06: 66
- 2026-09-05: 66
- 2026-09-04: 65

## Common questions

### 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 73 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 754 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://muslim-prayer-mcp.najetareqz.workers.dev/mcp
- Repository: https://github.com/tareq7/muslim-prayer-mcp
- Changelog RSS feed: https://verifymcp.io/servers/tareq7-muslim-prayer-mcp/muslim-prayer-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/tareq7-muslim-prayer-mcp/muslim-prayer-mcp.json
- HTML version of this page: https://verifymcp.io/servers/tareq7-muslim-prayer-mcp/muslim-prayer-mcp