Remote MCP · Endpoint

NextBid — Government Bids for AI MCP server

No. NextBid — Government Bids for AI answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.nextbid.us/mcp

The last check completed an MCP handshake.

Registry name
us.nextbid/data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
250 ms
Tools exposed
14 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Search open U.S. federal, state and local government bids and read their documents. Paid; trial.
Listing
From the official MCP registry (active).
Recent checks of NextBid — Government Bids for AI
CheckedResultHandshake
1 hour agoHandshake completed250 ms
1 day agoHandshake completed212 ms
2 days agoHandshake completed224 ms
2 days agoHandshake completed212 ms
4 days agoHandshake completed209 ms
7 days agoHandshake completed208 ms
9 days agoHandshake completed213 ms
12 days agoFailed - the request timed out—
14 days agoHandshake completed261 ms
16 days agoHandshake completed215 ms
18 days agoHandshake completed215 ms
20 days agoHandshake completed212 ms
22 days agoHandshake completed217 ms
24 days agoHandshake completed213 ms

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

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 NextBid — Government Bids for AI and makes no claim about it beyond what these checks measured.