Remote MCP · Endpoint

Maha Context Review MCP server

No. Maha Context Review answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://www.mahastrategies.com/api/mcp/context-review?channel=registry

The last check completed an MCP handshake.

Registry name
com.mahastrategies/context-review
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
186 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Reduce supplied context and check caller-declared, source-specific exact evidence retention.
Listing
From the official MCP registry (active).
Recent checks of Maha Context Review
CheckedResultHandshake
2 hours agoHandshake completed186 ms
2 days agoHandshake completed1.11 s
4 days agoHandshake completed1.48 s
7 days agoHandshake completed1.38 s
9 days agoHandshake completed115 ms
11 days agoHandshake completed99 ms
13 days agoHandshake completed1.09 s
15 days agoHandshake completed120 ms
16 days agoHandshake completed335 ms
18 days agoHandshake completed283 ms
19 days agoHandshake completed120 ms
20 days agoHandshake completed172 ms
23 days agoHandshake completed148 ms
24 days agoHandshake completed1.21 s

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

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