io.github.imgproc-git/govbid-mcp-server
REMOTE · GOVBID-MCP-SERVER.GAIKOTSUIMAGEPROCESSING.WORKERS.DEV
U.S. federal contract opportunities from SAM.gov. Daily updates. Public Domain.
Available components
Last scanned (9 hours ago)
Scores higher than 64% of remote servers
Reachable. Last reached 5 Nov 2026.
Category CRM and Sales
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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 415 tokens (~103/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (11)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (2)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 22 Sept 26 0
- Stability: 0.97 → pass security
- 31 Aug 26 0
- Tool “search_opportunities” rewrote its description, which is the text the model reads security
- Schema quality: 87 → 103 ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “register_agent” functional
- “search_opportunities” reworded the description of “api_key” cosmetic
- 30 Aug 26 0
- Tool “get_api_info” rewrote its description, which is the text the model reads security
- Tool “get_opportunity_detail” rewrote its description, which is the text the model reads security
- Tool “search_opportunities” rewrote its description, which is the text the model reads security
- Schema quality: 34 → 87 ▼ functional
- Tool coverage: 0% → 100% ▲ functional
- Schema quality: good → excellent functional
- “get_opportunity_detail” reworded the description of “notice_id” cosmetic
- “search_opportunities” reworded the description of “api_key” cosmetic
- “search_opportunities” reworded the description of “days” cosmetic
- “search_opportunities” reworded the description of “department” cosmetic
- “search_opportunities” reworded the description of “limit” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 23 Aug 26 0
First indexed and scored.
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 5 Nov 2026 · Probed https://govbid-mcp-server.gaikotsuimageprocessing.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=gaikotsuimageprocessing.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 11 Sept 2026 | 10 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 5f8d9faf783d5bfab3acd1b739fc7f2a54a |
| SANs: *.gaikotsuimageprocessing.workers.dev, gaikotsuimageprocessing.workers.dev | ||||||
| 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 govbid-mcp-server.gaikotsuimageprocessing.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://govbid-mcp-server.gaikotsuimageprocessing.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://govbid-mcp-server.gaikotsuimageprocessing.workers.dev/mcp | Inconclusive | 405 |
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 →
get_api_info ~43
Get metadata about the GovBid Global API including version, data source, license information, and usage guidelines. Call this first to understand the service before making other tool calls.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_opportunity_detail ~69
Get the direct SAM.gov URL for a specific contract opportunity by its notice ID. Use this to provide users with a link to verify and view full details on SAM.gov.
| Name | Type | Req | Description |
|---|---|---|---|
| notice_id | string | yes | The unique notice ID of the opportunity (from the 'id' field in search results) |
No output schema declared.
No examples provided.
register_agent ~126
Register this agent with the GovBid Global API and receive an API key. Call this once if you don't already have an api_key, before calling search_opportunities. No human interaction (e.g. CAPTCHA) is required — this endpoint is designed for autonomous AI agent self-registration. The returned api_key is shown only once, so store it for reuse.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_name | string | yes | A name identifying this agent or application (e.g. 'research-assistant-v2') |
| string | yes | A contact email associated with this registration. One active key is allowed per email. |
No output schema declared.
No examples provided.
search_opportunities ~177
Search U.S. federal government contract opportunities from SAM.gov. Returns recent procurement notices with title, department, deadline, and source URL. Data is updated daily. License: Public Domain (SAM.gov). Requires an api_key — call register_agent first if you don't have one.
| Name | Type | Req | Description |
|---|---|---|---|
| api_key | string | yes | GovBid API key (X-API-Key). Required for authentication. If you don't have one, call register_agent first. |
| days | number | – | How many days back to search (1-365, default: 7) |
| department | string | – | Filter by agency/department name (partial match). Examples: 'DEFENSE', 'NAVY', 'ARMY', 'INTERIOR', 'HEALTH' |
| limit | number | – | Number of opportunities to return (1-100, default: 10) |
No output schema declared.
No examples provided.
How do I install the io.github.imgproc-git/govbid-mcp-server server?
io.github.imgproc-git/govbid-mcp-server is a hosted endpoint at https://govbid-mcp-server.gaikotsuimageprocessing.workers.dev/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 · govbid-mcp-server.gaikotsuimageprocessing.workers.dev
claude mcp add --transport http imgproc-git-govbid-mcp-server 'https://govbid-mcp-server.gaikotsuimageprocessing.workers.dev/mcp'
What is the io.github.imgproc-git/govbid-mcp-server server?
io.github.imgproc-git/govbid-mcp-server is listed in the public MCP registry as io.github.imgproc-git/govbid-mcp-server. U.S. federal contract opportunities from SAM.gov. Daily updates. Public Domain. This page covers its hosted endpoint (https://govbid-mcp-server.gaikotsuimageprocessing.workers.dev/mcp).
Is the io.github.imgproc-git/govbid-mcp-server server safe to use?
io.github.imgproc-git/govbid-mcp-server scores 75 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 io.github.imgproc-git/govbid-mcp-server server expose?
io.github.imgproc-git/govbid-mcp-server exposes 4 tools: register_agent, search_opportunities, get_opportunity_detail, get_api_info. Their descriptions and schemas cost roughly 415 tokens of context every time the server is loaded.
Does the io.github.imgproc-git/govbid-mcp-server server require authentication?
No. We connected to io.github.imgproc-git/govbid-mcp-server without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.imgproc-git/govbid-mcp-server server still maintained?
io.github.imgproc-git/govbid-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the io.github.imgproc-git/govbid-mcp-server server?
VerifyMCP ran 11 checks on io.github.imgproc-git/govbid-mcp-server, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about io.github.imgproc-git/govbid-mcp-server: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.