Remote MCP · Endpoint

io.github.Maha-Strategies/mps-preflight MCP server

No. io.github.Maha-Strategies/mps-preflight answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.mahastrategies.com/api/mcp/mps-preflight

The last check completed an MCP handshake.

Registry name
io.github.Maha-Strategies/mps-preflight
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
232 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Claim-level provenance preflight for sanitized nonfiction passages; automated triage only.
Listing
From the official MCP registry (active).
Recent checks of io.github.Maha-Strategies/mps-preflight
CheckedResultHandshake
1 hour agoHandshake completed232 ms
1 day agoHandshake completed173 ms
2 days agoHandshake completed107 ms
3 days agoHandshake completed252 ms
4 days agoHandshake completed133 ms
5 days agoHandshake completed132 ms
6 days agoHandshake completed107 ms
9 days agoHandshake completed103 ms
11 days agoHandshake completed157 ms
14 days agoHandshake completed130 ms
16 days agoHandshake completed125 ms
18 days agoHandshake completed482 ms
20 days agoHandshake completed142 ms
22 days agoHandshake completed132 ms
24 days agoHandshake completed144 ms
26 days agoHandshake completed195 ms
27 days agoHandshake completed213 ms
29 days agoHandshake completed119 ms

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

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 io.github.Maha-Strategies/mps-preflight and makes no claim about it beyond what these checks measured.