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

iqamah-prayer-times

https://api.iqamah.net

Registry code: df909a6c8de516f9

api record

Prayer (salah) times from api.iqamah.net. get_prayer_times gives calculated or official azaan times for any point; find_mosques_near lists mosques near a point; get_mosque_times gives one mosque's own iqamah (congregation) and Jumu'ah times. Tools take coordinates: when the user names a place, use its latitude and longitude. Times are 24-hour local time in the returned time zone. Prefer a mosque's own times when the user asks about a specific mosque.

endpoint
https://api.iqamah.net/mcp
protocol
streamable-http ·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 iqamah-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 iqamah-prayer-times free to use?
Yes — the hub reached it with no key and no payment.
What tools does iqamah-prayer-times have?
3 tools: find_mosques_near, get_mosque_times, get_prayer_times.
Is iqamah-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 100%· all time 100%

latency
113ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ 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 3 tools
3 never probed 0 of 3 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.

  • find_mosques_near unknown 1h ago

    Mosques near a point, nearest first, with their ids for get_mosque_times. has_source says whether we can read the mosque's own times.

    mcp-tool

    {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "name": {
          "type": "string",
          "description": "Only mosques whose name contains this (case and accents ignored)."
        },
        "limit": {
          "type": "integer",
          "default": 10,
          "maximum": 50,
          "minimum": 1
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180
        },
        "radius_km": {
          "enum": [
            2,
            5,
            10,
            25,
            50
          ],
          "type": "integer",
          "default": 10
        }
      },
      "additionalProperties": false
    }
    arguments 41 lines
  • get_mosque_times unknown 1h ago

    One mosque's congregation (iqamah) and Jumu'ah times as the mosque publishes them, from today on, with the azaan times. status says whether they are fresh, stale (latest we have), queued (not read yet) or none.

    mcp-tool

    {
      "type": "object",
      "required": [
        "mosque_id"
      ],
      "properties": {
        "days": {
          "type": "integer",
          "default": 1,
          "maximum": 7,
          "minimum": 1
        },
        "mosque_id": {
          "type": "string",
          "description": "The id from find_mosques_near."
        }
      },
      "additionalProperties": false
    }
    arguments 19 lines
  • get_prayer_times unknown 1h ago

    Azaan (start) times for Fajr, sunrise, Dhuhr, Asr, Maghrib and Isha at a point, for one or more days. Uses the country's usual method unless one is given, and the official authority's timetable where we hold it (Malaysia, Indonesia, Singapore, Kazakhstan, Morocco). These are not a mosque's congregation (iqamah) times; for those use find_mosques_near and get_mosque_times.

    mcp-tool

    {
      "type": "object",
      "required": [
        "latitude",
        "longitude"
      ],
      "properties": {
        "asr": {
          "enum": [
            "standard",
            "hanafi"
          ],
          "type": "string",
          "description": "Asr: standard (Shafi'i, Maliki, Hanbali) or hanafi. Default: the country's or method's."
        },
        "date": {
          "type": "string",
          "description": "First day, YYYY-MM-DD. Default: today at the location."
        },
        "days": {
          "type": "integer",
          "default": 1,
          "maximum": 7,
          "minimum": 1
        },
        "method": {
          "enum": [
            "mwl",
            "isna",
            "egyptian",
            "karachi",
            "umm_al_qura",
            "dubai",
            "kuwait",
            "qatar",
            "singapore",
            "turkey",
            "tehran",
            "moonsighting",
            "jakim",
            "muis",
            "kemenag",
            "muftyat",
            "habous",
            "uz_board",
            "kg_muftiyat",
            "az_qmi",
            "ru_dumrf",
            "za_jamiat",
            "tn_ministry",
            "jo_iftaa",
            "lk_acju"
          ],
          "type": "string",
          "description": "Calculation method. Default: the country's usual one."
        },
        "latitude": {
          "type": "number",
          "maximum": 90,
          "minimum": -90
        },
        "longitude": {
          "type": "number",
          "maximum": 180,
          "minimum": -180
        }
      },
      "additionalProperties": false
    }
    arguments 69 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 df909a6c8de516f9.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/df909a6c8de516f9/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/df909a6c8de516f9/badge.svg)](https://brick.blue/agent/df909a6c8de516f9?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
70%

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.