Remote MCP · Endpoint

Mi Medical Exclusions MCP server

No. Mi Medical Exclusions answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://gateway.pipeworx.io/mi-medical-exclusions/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/mi-medical-exclusions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
101 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Michigan Medicaid provider sanctions screening: the Michigan Department of Health and Human…
Listing
From the official MCP registry (active).
Recent checks of Mi Medical Exclusions
CheckedResultHandshake
35 minutes agoHandshake completed101 ms
3 days agoHandshake completed107 ms
13 days agoHandshake completed152 ms
14 days agoHandshake completed185 ms
15 days agoHandshake completed94 ms
16 days agoHandshake completed91 ms
17 days agoHandshake completed148 ms
18 days agoHandshake completed279 ms
19 days agoHandshake completed71 ms
20 days agoHandshake completed194 ms
23 days agoHandshake completed69 ms
25 days agoHandshake completed69 ms
28 days agoHandshake completed96 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 Mi Medical Exclusions and makes no claim about it beyond what these checks measured.