Remote MCP · Endpoint

Oig Corporate Integrity MCP server

No. Oig Corporate Integrity answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/oig-corporate-integrity/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/oig-corporate-integrity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
376 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
HHS-OIG Corporate Integrity Agreements — does this healthcare company have a CIA, since when, what…
Listing
From the official MCP registry (active).
Recent checks of Oig Corporate Integrity
CheckedResultHandshake
1 hour agoHandshake completed376 ms
10 hours agoHandshake completed967 ms
2 days agoHandshake completed121 ms
4 days agoHandshake completed276 ms
7 days agoHandshake completed56 ms
9 days agoHandshake completed278 ms
12 days agoHandshake completed68 ms
14 days agoHandshake completed1.35 s
16 days agoHandshake completed1.47 s
18 days agoHandshake completed676 ms
20 days agoHandshake completed52 ms
22 days agoHandshake completed77 ms
23 days agoHandshake completed51 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 Oig Corporate Integrity and makes no claim about it beyond what these checks measured.