Remote MCP · Endpoint

Pa Medical Exclusions MCP server

No. Pa Medical Exclusions answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/pa-medical-exclusions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
80 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pennsylvania Department of Human Services (DHS) Medicheck Precluded Providers List screening…
Listing
From the official MCP registry (active).
Recent checks of Pa Medical Exclusions
CheckedResultHandshake
42 minutes agoHandshake completed80 ms
9 days agoHandshake completed133 ms
10 days agoHandshake completed135 ms
11 days agoHandshake completed104 ms
12 days agoHandshake completed77 ms
14 days agoHandshake completed96 ms
14 days agoHandshake completed178 ms
15 days agoHandshake completed118 ms
17 days agoHandshake completed224 ms
19 days agoHandshake completed237 ms
21 days agoHandshake completed83 ms
24 days agoHandshake completed91 ms
26 days agoHandshake completed70 ms
28 days agoHandshake completed78 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 Pa Medical Exclusions and makes no claim about it beyond what these checks measured.