Remote MCP · Endpoint

Nj Medical Exclusions MCP server

No. Nj Medical Exclusions answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/nj-medical-exclusions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
95 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
New Jersey Department of the Treasury Ineligible Provider List (Medical category) screening…
Listing
From the official MCP registry (active).
Recent checks of Nj Medical Exclusions
CheckedResultHandshake
17 minutes agoHandshake completed95 ms
9 days agoHandshake completed167 ms
9 days agoHandshake completed1.16 s
11 days agoHandshake completed90 ms
12 days agoHandshake completed1.33 s
13 days agoHandshake completed1.40 s
14 days agoHandshake completed710 ms
15 days agoHandshake completed367 ms
16 days agoHandshake completed107 ms
19 days agoHandshake completed109 ms
21 days agoHandshake completed588 ms
24 days agoHandshake completed305 ms
26 days agoHandshake completed65 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 Nj Medical Exclusions and makes no claim about it beyond what these checks measured.