Remote MCP · Endpoint

Tx Medical Exclusions MCP server

No. Tx Medical Exclusions answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/tx-medical-exclusions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
109 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Texas HHSC Office of Inspector General (OIG) Medicaid Provider Exclusions Database screening…
Listing
From the official MCP registry (active).
Recent checks of Tx Medical Exclusions
CheckedResultHandshake
1 hour agoHandshake completed109 ms
22 hours agoHandshake completed274 ms
1 day agoHandshake completed138 ms
2 days agoHandshake completed840 ms
4 days agoHandshake completed139 ms
7 days agoHandshake completed595 ms
9 days agoHandshake completed135 ms
12 days agoHandshake completed954 ms
14 days agoHandshake completed1.03 s
16 days agoHandshake completed1.26 s
18 days agoHandshake completed988 ms
20 days agoHandshake completed1.26 s
22 days agoHandshake completed70 ms
24 days agoHandshake completed310 ms

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