Remote MCP · Endpoint

GovContract Radar MCP server

Yes, as of 7 hours ago: the request timed out.

DownLast checked 7 hours ago

Server URL

https://gov.pixharvest.com/mcp

The last check failed: the request timed out.

Registry name
com.pixharvest/gov-contract-radar
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
5 tools
Uptime, last 30 days
0.0% from 13 checks
Described by its publisher as
US federal contracts: solicitations, set-asides, deadlines, awards, contractor profiles. Free.
Listing
From the official MCP registry (active).
Recent checks of GovContract Radar
CheckedResultHandshake
7 hours agoFailed - the request timed out—
4 days agoFailed - the request timed out—
14 days agoFailed - the request timed out—
15 days agoFailed - the request timed out—
15 days agoFailed - the request timed out—
17 days agoFailed - the request timed out—
18 days agoFailed - the request timed out—
19 days agoFailed - the request timed out—
20 days agoFailed - the request timed out—
21 days agoFailed - the request timed out—
23 days agoFailed - the request timed out—
26 days agoFailed - the request timed out—
28 days agoFailed - the request timed out—

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

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