Muslim Prayer Reminder MCP server
io.github.tareq7/muslim-prayer-mcptareq7streamable-httpv1.1.1Scanned
Production-ready Muslim prayer reminder MCP with astronomical precision and theological disclosure.
5 tools: 1 can delete or cancel things, 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- 1 finding
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here can delete or cancel things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Muslim Prayer Reminder MCP server can do
The Muslim Prayer Reminder MCP server is published by the GitHub account tareq7. It has 5 tools. It can delete or cancel things (1 tool: configure_prayer_preferences) and create or change data (1 tool: get_prayer_status). 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
The fixed checks matched 1 finding (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 20, 2026, version 1.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
5 tools
Deletes or cancels 1Claude Code: deny
configure_prayer_preferencesUpdates persistent prayer preferences, overwriting supplied settings while preserving omitted settings.No findings
Why it is in this group
- The description's first verb is "update": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: true
- openWorldHint: false
Changes things 1Claude Code: ask
get_prayer_statusChecks if a Muslim obligatory prayer (Fajr, Dhuhr, Asr, Maghrib, Isha) is currently due for the user location and returns active reminder details.1 finding
Why it is in this group
- The name "get_prayer_status" says "get": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
Findings
- Warn
The server marks "get_prayer_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_prayer_status" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
Only reads 3Show 3 read-only tools
get_next_prayerReturns the immediate next prayer name, scheduled time, authority calculation method, and remaining countdown in minutes.No findings
Why it is in this group
- The name "get_next_prayer" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_prayer_preferencesReturns the currently active calculation settings and preferences for a user.No findings
Why it is in this group
- The name "get_prayer_preferences" says "get": a word for reading.
Description, as the server wrote it Returns the currently active calculation settings and preferences for a user. Read-only operation.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_today_prayer_timesRetrieves today prayer timetable (Fajr, Sunrise, Dhuhr, Asr, Maghrib, Isha) in UTC and formatted local time.No findings
Why it is in this group
- The name "get_today_prayer_times" says "get": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:11 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 2
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 destructive, 1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://muslim-prayer-mcp.najetareqz.workers.dev/mcp: tools/list returned 5 tools to an anonymous client, including configure_prayer_preferences (destructive), get_prayer_status (write)
Findings
Matches of fixed checks, with the text they matched.
The server marks "get_prayer_status" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":false}; The name "get_prayer_status" says "get": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.1.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http muslim-prayer https://muslim-prayer-mcp.najetareqz.workers.dev/mcpclaude mcp add --transport http muslim-prayer https://muslim-prayer-mcp.najetareqz.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__muslim-prayer__get_today_prayer_times",
"mcp__muslim-prayer__get_next_prayer",
"mcp__muslim-prayer__get_prayer_preferences"
],
"ask": [
"mcp__muslim-prayer__get_prayer_status"
],
"deny": [
"mcp__muslim-prayer__configure_prayer_preferences"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as muslim-prayer. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.tareq7/muslim-prayer-mcp/verify?hash=6f29ea6bae2293c8e1b899f9d9618d00bcff62d956635e486dae7081da11a01a" | jq -e '.changed == false'Pinned hash 6f29ea6bae22, from Nov 20, 2026, 14:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.tareq7/muslim-prayer-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.tareq7/muslim-prayer-mcp)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:50 UTC.
Muslim Prayer Reminder MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Muslim Prayer Reminder MCP server safe?
- No scan can promise that. What its definitions show: 5 tools, 2 of which can change, send or delete something, and 1 finding from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Muslim Prayer Reminder MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: configure_prayer_preferences.
Can the Muslim Prayer Reminder MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Muslim Prayer Reminder MCP server have?
- 5 tools: 1 destructive, 1 write, 3 read. configure_prayer_preferences, get_prayer_status, get_today_prayer_times, get_next_prayer and get_prayer_preferences.
Does the Muslim Prayer Reminder MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Muslim Prayer Reminder MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Muslim Prayer Reminder MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 20, 2026.