Remote MCP · Endpoint

Quran Gallery MCP MCP server

No. Quran Gallery MCP answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://qurangallery.com/mcp/shamela

The last check completed an MCP handshake.

Registry name
com.qurangallery/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
145 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Classical Islamic library (Shamela, 8,594 books): verbatim Arabic cited by volume and page. No key.
Listing
From the official MCP registry (active).
Recent checks of Quran Gallery MCP
CheckedResultHandshake
1 day agoHandshake completed145 ms
1 day agoHandshake completed305 ms
2 days agoHandshake completed62 ms
4 days agoHandshake completed66 ms
5 days agoHandshake completed157 ms
6 days agoHandshake completed147 ms
7 days agoHandshake completed77 ms
7 days agoHandshake completed87 ms
9 days agoHandshake completed490 ms
12 days agoHandshake completed145 ms
14 days agoHandshake completed379 ms
17 days agoHandshake completed66 ms
19 days agoHandshake completed121 ms
21 days agoHandshake completed153 ms
23 days agoHandshake completed143 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Quran Gallery MCP and makes no claim about it beyond what these checks measured.