Skip to content

Prayer times and sun times MCP server

dev.workers.mnpi.prayer-times/prayer-timesprayer-times.mnpi.workers.devstreamable-httpv1.1.0Scanned

Islamic prayer times (20+ methods) and sunrise/sunset for 34,000 towns or coordinates, local time.

3 tools: 3 change things.

Tools: 0 delete, 0 irreversible, 3 write, 0 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

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 Prayer times and sun times MCP server can do

The Prayer times and sun times MCP server is published by prayer-times.mnpi.workers.dev, a domain the MCP Registry verified. It has 3 tools. It can create or change data (3 tools: prayer_times, sun_times and prayer_methods), but cannot delete data. None of its tools only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 19, 2026, version 1.1.0.

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.

3 tools

Changes things 3Claude Code: ask
  • prayer_methodsThe calculation methods available (fajr and isha angles), and the countries where each is the default.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The calculation methods available (fajr and isha angles), and the countries where each is the default.

    Annotations the server declares

    • title: Methods
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • prayer_timesPrayer times (imsak, fajr, sunrise, dhuhr, asr, maghrib, isha, midnight) for a town, city or coordinates, in local time, for one day or a timetable of up to 31 days.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Prayer times (imsak, fajr, sunrise, dhuhr, asr, maghrib, isha, midnight) for a town, city or coordinates, in local time, for one day or a timetable of up to 31 days. Covers 34,000 towns worldwide (names in English or Arabic). Calculation method defaults to the usual one for the country (Umm al-Qura in Saudi Arabia, Egyptian in Egypt, Karachi in Pakistan, ISNA in North America, MWL elsewhere) and is always stated; asr standard or hanafi.

    Annotations the server declares

    • title: Prayer times
    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • sun_timesSunrise, sunset, solar noon, day length, and civil, nautical and astronomical dawn and dusk for a town, city or coordinates on a date, in local time.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    Sunrise, sunset, solar noon, day length, and civil, nautical and astronomical dawn and dusk for a town, city or coordinates on a date, in local time.

    Annotations the server declares

    • title: Sun times
    • readOnlyHint: true
    • 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.

Tools listed without sign-in

Looked at Nov 19, 2026, 17:24 UTC, unchanged since Nov 19, 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
3
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
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 3 tools that change things (3 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://prayer-times.at01.io/mcp: tools/list returned 3 tools to an anonymous client, including prayer_times (write), sun_times (write), prayer_methods (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

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.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http prayer-times https://prayer-times.at01.io/mcp
claude mcp add --transport http prayer-times https://prayer-times.at01.io/mcp

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

.claude/settings.json
{
  "permissions": {
    "allow": [],
    "ask": [
      "mcp__prayer-times__prayer_times",
      "mcp__prayer-times__sun_times",
      "mcp__prayer-times__prayer_methods"
    ],
    "deny": []
  }
}

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 prayer-times. 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/dev.workers.mnpi.prayer-times/prayer-times/verify?hash=fafee1c8eafa8c2a24f40b2bbc0be8d392c4fbf25673a4b1364c9836b1511804" | jq -e '.changed == false'

Pinned hash fafee1c8eafa, from Nov 19, 2026, 12:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/dev.workers.mnpi.prayer-times/prayer-times/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for dev.workers.mnpi.prayer-times/prayer-times
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.workers.mnpi.prayer-times/prayer-times.svg)](https://radar.anlyon.com/servers/dev.workers.mnpi.prayer-times/prayer-times)

Source: MCP Registry. Synced Nov 19, 2026, 12:17 UTC.

Prayer times and sun times MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the Prayer times and sun times MCP server safe?

No scan can promise that. What its definitions show: 3 tools, 3 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Prayer times and sun times MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Prayer times and sun times 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 Prayer times and sun times MCP server have?

3 tools: 3 write. prayer_times, sun_times and prayer_methods.

Does the Prayer times and sun times MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Prayer times and sun times MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Prayer times and sun times MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.