Remote MCP · Endpoint

Barakah Halal Stock Screen MCP server

No. Barakah Halal Stock Screen answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.barakahprofits.com/mcp

The last check completed an MCP handshake.

Registry name
com.barakahprofits.app/halal-screen
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
93 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Check if a US stock is halal (Sharia-compliant), with the dates its verdict changed.
Listing
From the official MCP registry (active).
Recent checks of Barakah Halal Stock Screen
CheckedResultHandshake
1 hour agoHandshake completed93 ms
2 days agoHandshake completed413 ms
5 days agoHandshake completed104 ms
7 days agoHandshake completed102 ms
9 days agoHandshake completed124 ms
11 days agoHandshake completed115 ms
13 days agoHandshake completed123 ms
15 days agoHandshake completed117 ms
17 days agoHandshake completed90 ms
19 days agoHandshake completed97 ms
20 days agoHandshake completed142 ms
21 days agoHandshake completed91 ms
23 days agoHandshake completed98 ms

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

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 Barakah Halal Stock Screen and makes no claim about it beyond what these checks measured.