Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Muslim Prayer Reminder MCP

REMOTE · MUSLIM-PRAYER-MCP.NAJETAREQZ.WORKERS.DEV · 2 COMPONENTS · SCANNED SEP 20

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

+4 this week 73 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management53
  • Stability observed for 16 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
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.

remote · muslim-prayer-mcp.najetareqz.workers.dev

# add to Claude Code
claude mcp add --transport http tareq7-muslim-prayer-mcp 'https://muslim-prayer-mcp.najetareqz.workers.dev/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "tareq7-muslim-prayer-mcp": {
      "url": "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "tareq7-muslim-prayer-mcp": {
      "type": "http",
      "url": "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add tareq7-muslim-prayer-mcp --url 'https://muslim-prayer-mcp.najetareqz.workers.dev/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  tareq7-muslim-prayer-mcp:
    url: "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "tareq7-muslim-prayer-mcp": {
      "Transport": "http",
      "Url": "https://muslim-prayer-mcp.najetareqz.workers.dev/mcp"
    }
  }
}
# add to Vellum
assistant mcp add tareq7-muslim-prayer-mcp -t streamable-http -u 'https://muslim-prayer-mcp.najetareqz.workers.dev/mcp'
// mcp.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 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.

  • 20 Sept 26 +11
    • Judged manipulation: unverified → pass security
    • Schema quality: unverified → good functional
  • 19 Sept 26 −10
    • Judged manipulation: pass → unverified security
    • Schema quality: good → unverified functional
    • “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” cosmetic
  • 18 Sept 26 +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.

  • 16 Sept 26 +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.

  • 14 Sept 26 +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.

  • 12 Sept 26 +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.

  • 9 Sept 26 +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.

  • 7 Sept 26 +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.

Diagnostics

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 20 Sept 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 12 Aug 2026 10 Nov 2026 ECDSA 256 ECDSA-SHA256 709724b27d59821c13f60ef6c47a12a7
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
MCP tools · 5 exposed · ~754 tokens

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 →

Tool Tokens
configure_prayer_preferences ~252

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

NameTypeReqDescription
calculationMethodstringIslamic prayer calculation authority
enabledbooleanWhether prayer reminders are enabled
exactWindowMinutesintegerDuration in minutes for exact_window mode
fixedCitystringPredefined city name for fixed location (e.g. Riyadh, London)
fixedCoordinatesobjectFixed geographical coordinates
highLatitudeRulestringHigh latitude twilight adjustment rule
localestringLanguage for reminder text: en or ar
locationModestringLocation strategy: auto_travel or fixed
madhabstringJurisprudential Asr shadow calculation: Shafi or Hanafi
minuteAdjustmentsobjectCustom per-prayer minute offsets (-60 to +60)
reminderModestringReminder display policy: prayer_window, exact_window, persistent
timezonestringIANA timezone identifier (e.g. Asia/Riyadh, Europe/London)
userIdstringyesUnique user identifier
NameTypeReqDescription
preferencesobjectyes
successbooleanyesWhether configuration succeeded

No examples provided.

get_next_prayer ~137

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

NameTypeReqDescription
calculationMethodstringOptional calculation authority override (auto-resolved from location by default)
latitudenumberOptional explicit latitude override
longitudenumberOptional explicit longitude override
madhabstringOptional Asr shadow jurisprudence override (Shafi or Hanafi)
timezonestringOptional IANA timezone override
NameTypeReqDescription
authorityDescriptionstring
authorityNoticeobject
calculationMethodstringyesActive calculation authority
currentLocalDatestringyesCurrent local date YYYY-MM-DD
madhabstringyesActive Asr jurisprudence
minuteAdjustmentsobject
nextPrayerstringyesName of the upcoming prayer
nextPrayerAtUtcstringyesUTC timestamp of the upcoming prayer
nextPrayerLocalTimestringyesFormatted local time HH:mm
remainingMinutesintegeryesMinutes remaining until prayer start
selectionReasonstring
timezonestringyesResolved IANA timezone

No examples provided.

get_prayer_preferences ~37

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

NameTypeReqDescription
userIdstringyesUnique user identifier
NameTypeReqDescription
calculationMethodstring
enabledboolean
exactWindowMinutesnumber
fixedCitystring
fixedCoordinatesobject
highLatitudeRulestring
localestring
locationModestring
madhabstring
messagestring
minuteAdjustmentsobject
reminderModestring
timezonestring
updatedAtUtcstring
userIdstring

No examples provided.

get_prayer_status ~162

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

NameTypeReqDescription
calculationMethodstringOptional calculation authority override (auto-resolved from location by default)
latitudenumberOptional explicit latitude override
longitudenumberOptional explicit longitude override
madhabstringOptional Asr shadow jurisprudence override (Shafi or Hanafi)
timezonestringOptional IANA timezone override (e.g. Asia/Riyadh)
NameTypeReqDescription
authorityDescriptionstringDescription of the calculation authority
authorityNoticeobjectMandatory theological transparency notice
calculationMethodstringyesActive calculation authority
expiresAtUtcstringUTC expiration time of the active prayer window
localDatestringyesCurrent local date in YYYY-MM-DD
madhabstringyesActive Asr jurisprudence
minuteAdjustmentsobjectApplied minute adjustments
nextPrayerstringyesThe name of the next upcoming prayer
nextPrayerAtUtcstringyesUTC timestamp of the next upcoming prayer
prayerstringThe name of the currently due prayer if applicable
reminderDuebooleanyesWhether a prayer is currently due for reminder
reminderTextstringLocalized reminder message
selectionReasonstringReason for authority selection
startedAtUtcstringUTC start time of the active prayer window
timezonestringyesResolved IANA timezone

No examples provided.

get_today_prayer_times ~166

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

NameTypeReqDescription
calculationMethodstringOptional calculation authority override (auto-resolved from location by default)
datestringDate in YYYY-MM-DD format (defaults to today)
latitudenumberOptional explicit latitude override
longitudenumberOptional explicit longitude override
madhabstringOptional Asr shadow jurisprudence override (Shafi or Hanafi)
timezonestringOptional IANA timezone override
NameTypeReqDescription
authorityDescriptionstring
authorityNoticeobject
calculationMethodstringyesActive calculation authority
localDatestringyesLocal schedule date YYYY-MM-DD
madhabstringyesActive Asr jurisprudence
minuteAdjustmentsobject
selectionReasonstring
timesLocalobjectyes
timesUtcobjectyes
timezonestringyesResolved IANA timezone

No examples provided.

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.