NextBid — Government Bids for AI
REMOTE · API.NEXTBID.US
Search open U.S. federal, state and local government bids and read their documents. Paid; trial.
Available components
Last scanned (19 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 4 Nov 2026.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1755 tokens (~125/item across 14 items; 14 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 41% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 27 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Oct 26 +1
- Authorization: unverified → fail ▼ security
- Injection markers: unverified → pass ▲ security
- HSTS header: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- Endpoint reachability: unreachable → reachable ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- Stability: unverified → 0.47 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- 24 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- Authorization: fail → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.40 → unverified ▼ security
- HSTS header: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 22 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://api.nextbid.us/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.nextbid.us | CN=YE1,O=Let's Encrypt,C=US | 28 Sept 2026 | 27 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 61f0fc93c319d33dd1a24566f3f9d9faac5 |
| SANs: api.nextbid.us | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.nextbid.us. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| us. | present | 59017 | 8 | Verified |
| nextbid.us. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains; preload |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.nextbid.us/mcp | Verified | 200 | |
| http (plaintext) | http://api.nextbid.us/mcp | HTTPS enforced | 308 | https://api.nextbid.us/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
corpus_stats ~136
The corpus numbers with their definitions: total_solicitations (distinct, duplicates excluded), open (listed open by the source with the deadline ahead or unstated, or deadline ahead with no status; passed deadlines and unknown status are separate: listed_open_past_deadline, status_unknown), due_30d (known deadline only), open_set_asides (distinct open solicitations designated under any supported program; each counts once; open competition excluded), open_set_aside_mentions (title language only), set_asides_by_program, unmapped_set_aside_values (for review), open by source, documents, as_of and replica_as_of.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_document_download ~70
A time-limited download link for one stored original document of an opportunity (sha256 from list_documents, where stored is true). One request; the file is served by NextBid's object store, not through the API.
| Name | Type | Req | Description |
|---|---|---|---|
| nb_id | string | yes | – |
| sha256 | string | yes | – |
No output schema declared.
No examples provided.
get_document_text ~79
The AnyDoc extracted text of one document (sha256 = the text sha256 or the original sha256 from get_evidence), verified against its indexed hash. Offsets in get_evidence index into this text. One request.
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | – |
| nb_id | string | yes | – |
| sha256 | string | yes | – |
No output schema declared.
No examples provided.
get_evidence ~132
The evidence for one opportunity: every indexed document (identity, version, hashes, whether the original is downloadable, whether the AnyDoc extracted text is verified) and the Graphify claims - each a GENERATED label with the SOURCE passage it cites (document, UTF-16 offsets, exact quoted text) and a verification status (RESOLVED = offsets match the hash-verified text and the graph quote). Gaps (pending custody, unavailable extraction, unresolved citations) are listed explicitly. One request.
| Name | Type | Req | Description |
|---|---|---|---|
| claims_limit | integer | – | – |
| claims_offset | integer | – | – |
| nb_id | string | yes | – |
No output schema declared.
No examples provided.
get_opportunity ~63
Full record for one opportunity by NextBid id (NB########): description, AI summary, buyer contacts (current and historical), amendments, filed documents. One request; counts as a delivered solicitation the first time this account receives it.
| Name | Type | Req | Description |
|---|---|---|---|
| nb_id | string | yes | – |
No output schema declared.
No examples provided.
list_documents ~81
The document set for one opportunity: source_documents (listed by the source engine: name, size, sha256, source url, whether NextBid stores the original) and nextbid_documents (the current Document 0 and normalized text, readable with read_file). Pipeline artifacts are counted, not listed. Names and metadata only.
| Name | Type | Req | Description |
|---|---|---|---|
| nb_id | string | yes | – |
No output schema declared.
No examples provided.
list_files ~78
The current stored documents for one opportunity: Document 0 markdown/json and normalized attachment markdown (class document0 / normalized_text). include="all" adds pipeline artifacts (case files, graphs, packets) and superseded Document 0 generations. Use read_file to fetch one.
| Name | Type | Req | Description |
|---|---|---|---|
| include | string | – | – |
| nb_id | string | yes | – |
No output schema declared.
No examples provided.
list_set_asides ~89
Set-aside and small-business programs NextBid recognizes (federal SBA programs, California SB/DVBE, open competition): id, name, level, what it means, official reference, aliases and today's counts split into open_designated (source-marked) and open_mentioned (title language only). Use an id or alias in search_opportunities.set_asides. Never an eligibility determination.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_tradelines ~54
The trade catalog: each trade id with its name, description, specialties and search aliases, plus today's open count. Use an id or any alias in search_opportunities. Specialties describe supported categories, not open bids.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
mark_pursuit ~71
Record that the customer is watching, pursuing, has submitted, won, lost or dropped an opportunity. Call it only when the customer says so; reading a bid is never a pursuit. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| nb_id | string | yes | – |
| note | string | – | – |
| status | string | yes | – |
No output schema declared.
No examples provided.
my_account ~45
The account's meter: plan, allowance used and remaining, period reset or trial expiry, keys, what counts as a call, how to upgrade, and the business profile. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
my_usage ~33
The account's meters: requests used and remaining, unique solicitations delivered and remaining, plan period or trial expiry. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
read_file ~60
Read one stored text artifact of an opportunity (path from list_files). Returns the text, truncated to max_chars (default 60,000).
| Name | Type | Req | Description |
|---|---|---|---|
| max_chars | integer | – | – |
| nb_id | string | yes | – |
| path | string | yes | – |
No output schema declared.
No examples provided.
search_opportunities ~764
Search open government solicitations (SAM.gov, DLA DIBBS, CalProcure, OpenGov, PlanetBids, PublicPurchase, Bonfire, and agency notices syndicated by InstantMarkets) in NextBid's normalized corpus. Returns one deduplicated record per opportunity with agency, deadline, codes, document status and a source link, plus total and facets. Metered on two account meters: one request per call, and each solicitation the first time it reaches the account (repeats are free on that meter). page_size 0 = counts and facets only. Trial: 100 requests and 250 solicitations per account, page_size up to 25. If the solicitation allowance runs out mid-page, delivery.truncated is true and delivery.withheld says how many were held back.
| Name | Type | Req | Description |
|---|---|---|---|
| agencies | array | – | Agency name fragments, e.g. ["Sacramento", "SMUD"]. |
| city | string | – | A city (needs states). Keeps only rows tied to it; each row says how in location_match: work_site (place of performance), named_in_title, service_area (needs county), mentioned_in_description (work s… |
| county | string | – | A county name without 'County' (needs states), e.g. "Riverside". Matches the record's service area or a county named in the title (service_area) or description (mentioned_in_description). |
| due_within_days | integer | – | Only opportunities closing within N days. |
| location_match | array | – | Keep only these location tiers (needs city or county). Default: all five. |
| open | boolean | – | Default true: only opportunities that are still open. false also returns closed and past-deadline solicitations. |
| page | integer | – | – |
| page_size | integer | – | Results per page (default 25). 0 = counts and facets only. Trial max 25, paid max 100; above the plan max is a 400. |
| q | string | – | Keywords (full-text over title and description). |
| set_asides | array | – | Set-aside programs from list_set_asides: small_business, 8a, hubzone, sdvosb, wosb, isbee, california_sb_dvbe, open, or any alias ("8(a)", "HUBZone", "DVBE"). Results carry set_aside_basis: designate… |
| sort | string | – | – |
| sources | array | – | Restrict to sources: sam.gov, dibbs, calprocure, opengov, planetbids, publicpurchase, bonfire, instantmarkets. |
| specialties | array | – | Your specialties, e.g. ["access control", "surveillance cameras", "fire alarm"]. Never filters: all matches stay; those naming a specialty in the title (2) or description (1) come first, each row lis… |
| states | array | – | Two-letter states, e.g. ["CA"]. Matched on the job location (place of performance, service area, buyer state, CalProcure=CA); each result carries a location object with its basis. |
| tradeline_match | string | – | validated (default): a trade matches only with NAICS/PSC or text evidence for that trade; loose: tag only (noisier). |
| tradelines | array | – | Trade ids or any alias from list_tradelines: e.g. lowvoltage, "access control", "badge readers", "structured cabling", roofing. Omit for all trades. |
No output schema declared.
No examples provided.
How do I install the NextBid — Government Bids for AI MCP server?
NextBid — Government Bids for AI is a hosted endpoint at https://api.nextbid.us/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.nextbid.us
claude mcp add --transport http us-nextbid-data 'https://api.nextbid.us/mcp'
What is the NextBid — Government Bids for AI MCP server?
NextBid — Government Bids for AI is an MCP server listed in the public MCP registry as us.nextbid/data. Search open U.S. federal, state and local government bids and read their documents. Paid; trial. This page covers its hosted endpoint (https://api.nextbid.us/mcp).
Is the NextBid — Government Bids for AI MCP server safe to use?
NextBid — Government Bids for AI scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the NextBid — Government Bids for AI MCP server expose?
NextBid — Government Bids for AI exposes 14 tools: search_opportunities, get_opportunity, list_documents, get_document_download, get_evidence, and 9 more. Their descriptions and schemas cost roughly 1,755 tokens of context every time the server is loaded.
Does the NextBid — Government Bids for AI MCP server require authentication?
Yes. NextBid — Government Bids for AI asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the NextBid — Government Bids for AI MCP server still maintained?
NextBid — Government Bids for AI is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.