Remote MCP · Endpoint

Oig Self Disclosure Settlements MCP server

No. Oig Self Disclosure Settlements answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://gateway.pipeworx.io/oig-self-disclosure-settlements/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/oig-self-disclosure-settlements
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.06 s
Tools exposed
46 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
HHS-OIG Self-Disclosure Protocol settlements — fleet #3274.
Listing
From the official MCP registry (active).
Recent checks of Oig Self Disclosure Settlements
CheckedResultHandshake
16 minutes agoHandshake completed1.06 s
8 days agoHandshake completed230 ms
9 days agoHandshake completed76 ms
11 days agoHandshake completed125 ms
12 days agoHandshake completed446 ms
13 days agoHandshake completed192 ms
14 days agoHandshake completed100 ms
15 days agoHandshake completed119 ms
16 days agoHandshake completed128 ms
19 days agoHandshake completed954 ms
21 days agoHandshake completed1.73 s
24 days agoHandshake completed810 ms
26 days agoHandshake completed2.68 s

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 Self Disclosure Settlements and makes no claim about it beyond what these checks measured.