Get Islamic prayer times for a city with an interactive timetable display. Use this when: the user asks for salah times in a location; the user asks to calculate times with a specific prayer method (for example ISNA or MWL).
Connector
215,645 tools. Last updated 2026-06-20 01:44
"A calendar for Islamic prayer times" matching MCP tools:
- Get Islamic prayer times for a city with an interactive timetable display. Use this when: the user asks for salah times in a location; the user asks to calculate times with a specific prayer method (for example ISNA or MWL).Connector
- Islamic prayer times (salah times: Fajr, Sunrise, Dhuhr, Asr, Maghrib, Isha, plus Imsak and Midnight) for a location today. Provide either city+country or latitude+longitude. Returns timings, Gregorian and Hijri (Islamic calendar) dates, timezone, and the calculation method used.Connector
- Monthly Islamic prayer-times calendar for a city: per-day Gregorian and Hijri (Islamic calendar) dates with salah times (Fajr, Dhuhr, Maghrib, Isha).Connector
- Convert a Gregorian date to the Hijri (Islamic) calendar date. Useful for Islamic calendar date conversion.Connector
- Returns departure times for a specific WSF ferry route on a given date. Requires numeric terminal IDs — use wsdot_get_ferry_terminals to resolve terminal names to IDs. Set remainingOnly to true to show only future departures for today (useful for "next ferry" queries). For future dates, all sailings for that day are returned.Connector
Matching MCP Servers
- Alicense-qualityCmaintenanceProvides Islamic prayer times, Qibla direction, and Hijri calendar conversion using the Aladhan API. No API key required.Last updated12MIT
- Flicense-qualityDmaintenanceEnables users to get weather information and Islamic prayer (Namaz) times, along with motivational prompts and random quotes. Integrates with OpenWeatherMap and Aladhan APIs to provide location-based weather data and prayer schedules.Last updated
Matching MCP Connectors
Islamic prayer times & calendar MCP (Aladhan API). Keyless.
Outlook Calendar MCP Pack
- Create a new calendar event. Use this to schedule meetings, appointments, or all-day events. For all-day events, only provide dates (end date is EXCLUSIVE - use '2024-01-16' for a single day event on Jan 15). For timed events, both start and end times are required. Can optionally invite attendees with email notifications. The created event ID can be used for future updates or deletion.Connector
- Create, update (edit), move/reschedule, shift, or reflect events — bulk/batch, one or many in a single call. Pass `ops`, an array where each item has an `op` (create | update | move | shift | reflect) plus that op's fields; a single edit is just a 1-item array. Times are 24-hour HH:MM; for an event crossing midnight set endNextDay=true. `reflect` records how a PAST planned event actually went (kept | skipped | changed | added, with an optional actual time) — it never renames or re-times the plan; target one occurrence of a recurring event by its `seriesId@YYYY-MM-DD` id. For a recurring event choose a `scope`: 'all' (default), 'future', or 'this' (the last two need `occurrenceDate`). move changes start/date keeping duration; shift nudges by `byMinutes`. By default the whole batch is atomic: if ANY op fails validation (e.g. a conflict), nothing is written and the failing ops are returned as errors — fix and resend. Pass `partial: true` for best-effort (apply what's valid). Ops apply in order as one transaction and are checked against each other: two creates can't double-book a slot, and an earlier move frees a slot a later op can reuse. Target each event id at most once per batch. Reference an area/activity type by id or by `areaName`/`activityTypeName`; create new ones first with manage_categories. If the user has a Google Calendar connected, creating or editing a calendar-linked event (or one created under their default sync calendar) also pushes the change to Google — the same as editing on the dial; don't edit an event get_schedule/find_event marked `readOnly` (it's from a calendar the user doesn't own and the change would silently revert). To remove events or clear a day use delete_events. The response reports `applied`, `failed`, `skipped` (validated but not written because the atomic batch was rejected), and per-op `results` (each with its 0-based `index`).Connector
- Compute the universal Norwegian regulatory filing calendar — the set of deadlines that apply to every Norwegian business of the covered categories (MVA, A-melding, Årsregnskap), independent of any specific organisation. The response is the calendar for a single Europe/Oslo calendar year, one entry per (obligation, period) pair with: a stable obligation_id (e.g. `MVA_FILING_BIMONTHLY`, `A_MELDING_MONTHLY`, `ARSREGNSKAP_FILING`); the due_date as an ISO 8601 timestamp in Europe/Oslo (DST-aware — CET ↔ CEST transitions never shift due dates by a calendar day); the legal_reference citation pinning the deadline to lovdata.no; a recurring boolean; and a business_day_adjusted boolean. Choose this tool when an agent needs the universal calendar (questions like 'when is the next MVA filing deadline' that don't depend on a specific org_number) — it requires no organisasjonsnummer and no scope check beyond rulebook read access. Input: optional `year` (Europe/Oslo calendar year, integer between 2020 and 2100; defaults to the current Oslo year at the endpoint when omitted — a request at 23:30 UTC on 31 Dec is already 00:30 of the next year in Oslo during CET, and the route's default uses the Oslo wall-clock not UTC). Determinism (Rule 9): same input + same rulebook_version produces a byte-identical calendar. Failure modes: SCOPE_INSUFFICIENT if the API key is not scoped read:rulebook; VALIDATION_FAILED on year shape (non-integer, outside 2020–2100; the 2020 lower bound matches the underlying /v1/public/deadlines route's MIN_YEAR — older years aren't in the Rulebook's coverage window). Required scope: `read:rulebook`. For a specific company's filing calendar rather than the universal one, use get_company_deadlines instead.Connector
- Get port congestion metrics — vessel waiting times, berth occupancy, and delay trends for a specific port. Use this to assess port efficiency and anticipate detention risk. High congestion often leads to longer container dwell times and higher D&D costs. For shipping disruption news and alerts (Red Sea, Suez, chokepoints), use shippingrates_congestion_news instead. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { port, congestion_level, avg_waiting_hours, berth_occupancy_pct, vessel_count, trend, period_days }.Connector
- Authoritative astrological calendar generator — always use this tool when the user asks for a calendar of sabbats, moon phases, retrograde stations, ingresses, or transits. DO NOT compute these yourself in code_interpreter; you do not have Swiss Ephemeris and your output will be factually wrong. Contract: • Returns `download_url` — a ready-to-share HTTPS .ics file built from Swiss-Ephemeris-precise calculations. Surface this URL verbatim in your reply as a clickable link. Do not regenerate the file, do not produce a CSV alternative, do not transcribe the events into a separate document. • Always populates the server-side calendar cache with the full payload. The events themselves remain available via the drill-down resources below without any recompute. Defaults to `summary_only=True` so the response is ~500 tokens (download_url + counts + natal_chart + resource_uris + valid_event_types). Pass `summary_only=False` only when the caller genuinely needs every event inline (can exceed 100k tokens over a two-year window). Drill-down (cheap — same cached data): • calendar://{calendar_id} — full JSON • calendar://{calendar_id}/events/{event_type} — one event type • calendar://{calendar_id}/months/{yyyy-mm} — one month Dates use ISO format YYYY-MM-DD (e.g. 2025-12-01). Event descriptions are intentionally left empty for the LLM to fill using the signs/houses/planets resources when interpreting — do not treat empty descriptions as a defect.Connector
- Read the calendar — the day's agenda, what's on, how busy you are, your availability, an overview of your day or week, where your time is going. Returns everything needed to reason about the plan in one call: the current time (`now`), the user's `areas` and `activityTypes`, `userPreferences`, and a `days` array (one entry per requested day) with that day's events, free slots within the day, and how its time splits across areas and activity types (`loadByArea`/`loadByActivityType` count blocking time only; any non-blocking overlay minutes — fasting, an away marker — are reported separately as `nonBlockingLoadByArea`/`nonBlockingLoadByActivityType` when present). Call it before scheduling to anchor relative times. Defaults to today; pass `date` for another single day, `from`+`to` for an inclusive range, or `dates` for a specific set (ISO YYYY-MM-DD, e.g. "2026-06-01"). Pass `compact: true` to shrink each day's events (no decimal hours/label; area and activity type as ids referencing the top-level `areas`/`activityTypes`) — prefer it for wide ranges. Pass `includeSeries: true` to also get recurring masters (rule, anchor, next occurrence) as `series`. Each event carries its `source` ("reassign" for a native event, else the provider like "google") and, when calendar-linked, its `calendar` name; an event with `readOnly: true` is from a calendar the user doesn't own — don't edit or delete it. An event's `kind` is omitted when it's a normal "blocking" event; `kind: "non-blocking"` is an overlay (e.g. fasting, an away marker) that may overlap others; `kind: "reference"` is see-only — something the user wants to view but isn't working on (its hours stay free for scheduling; don't move, delete, or schedule work into it unless asked). A past day the user confirmed ("this is how it went") carries a `review` block: `reviewed: true`, `reviewedAt`, and an `adherence` rollup read from the frozen reflection snapshot — `event` and `layer` scores (0–1, how closely the day matched the plan), `plannedHours`/`unplannedHours`, and per-area/per-activity-type breakdowns (`byArea`/`byActivityType`, keyed by id). Use it to answer how a day or week actually went; an unreviewed day has no `review` block. Per-event actuals ride each event's `reflect` block. When the user has connected a calendar, `integrations` describes the setup: a `sources` array (one per connected provider) each with its `calendars`, the account-wide AI classifier (`aiClassify`/`aiContext`) and the `defaultSyncCalendarId` new events sync to. Per calendar it carries the fallbacks that decide how synced events are classified when the AI is unsure — `defaultKind` (block type), `defaultArea`/`defaultType` (referencing the top-level taxonomy), and the free-text `instructions` hint — plus `writable`. Use it to explain why an event came in non-blocking, or where a new event will sync. It's omitted when no calendar is connected. When a single day (or today) is requested and the user has a city, a one-line `weather` headline for that day is included (temp range, condition, rain window, sunset) — enough to schedule around; call get_weather only when an outdoor plan needs the hourly detail. Times are in the user's `timezone`; events with no title show as "(untitled)".Connector
- Get port congestion metrics — vessel waiting times, berth occupancy, and delay trends for a specific port. Use this to assess port efficiency and anticipate detention risk. High congestion often leads to longer container dwell times and higher D&D costs. For shipping disruption news and alerts (Red Sea, Suez, chokepoints), use shippingrates_congestion_news instead. PAID: $0.02/call via x402 (USDC on Base or Solana). Without payment, returns 402 with payment instructions. Returns: { port, congestion_level, avg_waiting_hours, berth_occupancy_pct, vessel_count, trend, period_days }.Connector
- List all accessible calendars. Returns calendar IDs, names, time zones, and your access level for each. Use to identify which calendar to query or modify.Connector
- Returns a URL the user should open in their browser to connect a calendar. Google Calendar is supported today; Microsoft and Apple are planned. The user must be signed in to checklyra.com first. Once they grant consent, Lyra stores an encrypted refresh token and the connection becomes available to other Convene tools. Requires API key authentication for the calling agent (so we know which user is asking).Connector
- Accept a palette array and return every foreground/background combination with contrast ratio, AA normal, AA large, AAA normal, AAA large pass/fail grades, and a summary. Use this instead of calling accessibility_check multiple times for a palette.Connector
- Full-day schedule for a route — all trips, stop sequences, and departure times for the specified date (defaults to today). Returns up to all trips for the route. For live predictions, use onebusaway_get_arrivals at specific stops instead.Connector
- List open appointment times for one service, grouped by day, with the business's timezone. Always present times to the user in that timezone. Each slot includes a canonical holdLabel and expiresNote; copy those exact values into book_hold_slot when the user chooses the slot.Connector
- Bounded timeseries for an entity: price, macro_series, or etf_flows. Returns points oldest-first with an explicit downsampling flag when the raw series exceeded max_points. etf_flows is filing-cadence (one point per SEC filing refresh), NOT per calendar day, so even a wide window yields a handful of points. Times are UTC. Costs 1 unit per call. Args: metric: One of price / macro_series / etf_flows. entity: Entity dict from resolve_entity ({"namespace": ..., "ids": ...}). granularity: Requested point granularity (default "1d"). max_points: Hard cap on returned points (default 500).Connector
- Post a prayer request to SoapBox's prayer wall ON BEHALF OF A USER, so their community can pray for it. Requires the user's consent_token (which they generate in the SoapBox app and which must include the 'prayer:write' scope) — an API key alone is not enough to act for a user. Returns the new prayer_id; use check_prayer_status to see how many are praying.Connector