Remote MCP · Endpoint

Mizan MCP server

No. Mizan answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://goodturn-mcp.pages.dev/mizan/mcp

The last check completed an MCP handshake.

Registry name
io.github.GoodTurnStudio/mizan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
84 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Shariah screening of US stocks under four standards, halal alternatives, purification and zakat.
Listing
From the official MCP registry (active).
Recent checks of Mizan
CheckedResultHandshake
35 minutes agoHandshake completed84 ms
9 days agoHandshake completed74 ms
10 days agoHandshake completed41 ms
11 days agoHandshake completed42 ms
12 days agoHandshake completed46 ms
14 days agoHandshake completed47 ms
14 days agoHandshake completed49 ms
15 days agoHandshake completed15 ms
17 days agoHandshake completed47 ms
19 days agoHandshake completed17 ms
22 days agoHandshake completed38 ms
24 days agoHandshake completed20 ms
26 days agoHandshake completed19 ms
28 days agoHandshake completed32 ms

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

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