_ registry / mcp http-sse · checked 1h ago

prayer-times

https://time.quranmajeed.com

Registry code: ae14dd53ffa207d4

api record

Prayer times (Fajr, Sunrise, Dhuhr, Asr, Maghrib, Isha) for any city, from quranmajeed.com/prayer-times, by the makers of Quran Majeed.

Times come from official published timetables where one exists (London Central Mosque, Jordan's Ministry of Awqaf, UAE, Oman, Malaysia, Indonesia, Morocco, ...) or are calculated for the city's coordinates with the method the Prayer Times app applies for that country. Daylight saving is included; times are in the city's local time.

endpoint
https://time.quranmajeed.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is prayer-times live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is prayer-times free to use?
Yes — the hub reached it with no key and no payment.
What tools does prayer-times have?
2 tools: get_prayer_times, search_city.
Is prayer-times safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 99.3%· all time 99.3%

latency
92ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 278 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • get prayer times for a city
  • find a city for prayer times lookup
takes → gives
text → data
tools
2 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_prayer_times reads unknown 23h ago

    Prayer times (Fajr, Sunrise, Dhuhr, Asr, Maghrib, Isha) for a city on a date. Give either `city` (name or site slug such as "london", "new-york", "london-ca" for London, Ontario) or `place_id` (GeoNames id from search_city). `date` is YYYY-MM-DD in the city's local calendar (default: today there). Set `month` true for every day of that month. Returns local times, the UTC offset, the Hijri date, the calculation method or official timetable, and the page URL to cite.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "properties": {
        "city": {
          "type": "string",
          "maxLength": 80,
          "minLength": 1,
          "description": "City name or slug, e.g. \"Karachi\", \"kuala lumpur\", \"london-ca\""
        },
        "date": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "YYYY-MM-DD; default today in that city"
        },
        "month": {
          "type": "boolean",
          "description": "true: every day of the month of `date`"
        },
        "place_id": {
          "type": "integer",
          "maximum": 9007199254740991,
          "description": "GeoNames id from search_city (exact place)",
          "exclusiveMinimum": 0
        }
      }
    }
    arguments 27 lines
  • search_city reads unknown 23h ago

    Search cities and towns by name (any spelling, e.g. "Makkah" or "Mecca"). Returns candidates with their country, region, coordinates, time zone and GeoNames id; pass the id as place_id to get_prayer_times. Optional two-letter country code to narrow the search.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "query"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 20,
          "minimum": 1,
          "description": "Max results, default 8"
        },
        "query": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "City name, at least two characters"
        },
        "country": {
          "type": "string",
          "maxLength": 2,
          "minLength": 2,
          "description": "ISO 3166-1 alpha-2 country code, e.g. PK"
        }
      }
    }
    arguments 27 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id ae14dd53ffa207d4.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/ae14dd53ffa207d4/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/ae14dd53ffa207d4/badge.svg)](https://brick.blue/agent/ae14dd53ffa207d4?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.