Remote MCP · Endpoint

Gsa Elibrary MCP server

No. Gsa Elibrary answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://gateway.pipeworx.io/gsa-elibrary/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/gsa-elibrary
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
72 ms
Tools exposed
47 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
GSA eLibrary — Multiple Award Schedule (MAS) contract holders.
Listing
From the official MCP registry (active).
Recent checks of Gsa Elibrary
CheckedResultHandshake
17 minutes agoHandshake completed72 ms
9 days agoHandshake completed133 ms
9 days agoHandshake completed94 ms
11 days agoHandshake completed151 ms
12 days agoHandshake completed79 ms
13 days agoHandshake completed175 ms
14 days agoHandshake completed194 ms
15 days agoHandshake completed538 ms
16 days agoHandshake completed854 ms
19 days agoHandshake completed1.10 s
21 days agoFailed - the request timed out—
24 days agoHandshake completed2.18 s
26 days agoHandshake completed354 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 Gsa Elibrary and makes no claim about it beyond what these checks measured.