Remote MCP · Endpoint

GovInbox MCP server

No. GovInbox answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://mcp.getgovinbox.com/plugin

The last check completed an MCP handshake.

Registry name
com.getgovinbox/govinbox
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
187 ms
Tools exposed
45 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Federal contract opportunities for government contractors. Set-aside coverage is the deepest part.
Listing
From the official MCP registry (active).
Recent checks of GovInbox
CheckedResultHandshake
4 hours agoHandshake completed187 ms
10 days agoHandshake completed188 ms
11 days agoHandshake completed303 ms
11 days agoHandshake completed181 ms
13 days agoHandshake completed179 ms
14 days agoHandshake completed176 ms
15 days agoHandshake completed189 ms
16 days agoHandshake completed182 ms
17 days agoHandshake completed208 ms
19 days agoHandshake completed189 ms
22 days agoHandshake completed176 ms
24 days agoHandshake completed182 ms
26 days agoHandshake completed187 ms
29 days agoHandshake completed236 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 responding of 16.

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