Remote MCP · Endpoint

Pbgc MCP server

No. Pbgc answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://gateway.pipeworx.io/pbgc/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/pbgc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
277 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
PBGC MCP — pension plan terminations and premium filings.
Listing
From the official MCP registry (active).
Recent checks of Pbgc
CheckedResultHandshake
16 minutes agoHandshake completed277 ms
8 days agoHandshake completed242 ms
9 days agoHandshake completed93 ms
11 days agoHandshake completed126 ms
12 days agoHandshake completed236 ms
13 days agoHandshake completed168 ms
14 days agoHandshake completed57 ms
15 days agoHandshake completed121 ms
16 days agoHandshake completed164 ms
19 days agoHandshake completed761 ms
21 days agoHandshake completed1.74 s
24 days agoHandshake completed663 ms
26 days agoHandshake completed984 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 Pbgc and makes no claim about it beyond what these checks measured.