GovContract Radar
REMOTE · GOV.PIXHARVEST.COM
US federal contracts: solicitations, set-asides, deadlines, awards, contractor profiles. Free.
Available components
Last scanned (2 days ago)
Scores higher than 0% of remote servers
Unreachable for 7 days in a row. Last reached 9 Oct 2026.
Category CRM and Sales
Dead
Every channel of this server has been unreachable for long enough to be marked dead. Its trust score is pinned to 0 and does not recover automatically: even once the server responds again it stays dead until it is manually reinstated.
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 Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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.
- 16 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 15 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 14 Oct 26 −14
The score moved with no change recorded against any check. We would rather say so than guess.
- 13 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 12 Oct 26 −13
The score moved with no change recorded against any check. We would rather say so than guess.
- 10 Oct 26 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Stability: 0.17 → unverified ▼ security
- Transport: pass → fail ▼ security
- HTTPS: unverified → pass ▲ security
- Capabilities: fail → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 9 Oct 26 +1
- Schema quality: 227 → 192 ▲ functional
- 6 Oct 26 0
- Schema quality: 147 → 227 ▼ functional
- Stability: unverified → 0.07 ▲ functional
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 16 Oct 2026 · Probed https://gov.pixharvest.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pixharvest.com | CN=YE2,O=Let's Encrypt,C=US | 22 Sept 2026 | 21 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6c0ba988f814b3ac669355f273bb08b64b9 |
| SANs: *.pixharvest.com, pixharvest.com | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 gov.pixharvest.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| pixharvest.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://gov.pixharvest.com/mcp | Unreachable | ||
| http (plaintext) | http://gov.pixharvest.com/mcp | HTTPS enforced |
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 →
gov.awards ~126
Who actually won recent federal contracts in an industry: recent award records (recipient, amount, agency, start/end date, description, award ID) filtered by NAICS code, from public USAspending data. Use this to see the incumbents in a market, benchmark competitor wins, or research who holds contracts in a NAICS. Complements gov.search (open opportunities) with awarded contracts.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max award records (default 10, max 20). |
| naics | string | yes | NAICS code, e.g. '541511'. Required. |
No output schema declared.
No examples provided.
gov.company ~103
Federal contractor profile for a company: recent award count, total award amount, primary buyer agency, last signed date and sample award IDs, from public USAspending data. Search by full or partial company name (e.g. 'Cellentia', 'Lockheed'). Use this for competitor intelligence - who wins in your market and how much.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Company name (full or partial), e.g. 'CELLENTIA' or 'Alliance Global Tech'. |
No output schema declared.
No examples provided.
gov.digest ~121
Daily briefing for one NAICS code: a compact, chronological list of the most recently posted opportunities (title, agency, type, deadline, posting time) for routine monitoring of your market. Unlike gov.search, it takes only a NAICS code and returns a short digest - no keyword/type filters, no full descriptions. Use this as the routine morning check on what is new for your industry.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max digest items (default 5). |
| naics | string | yes | NAICS code, e.g. '541511'. Required. |
No output schema declared.
No examples provided.
gov.near_expiry ~103
Deadline-driven urgency triage: opportunities that close within N days, sorted by urgency (closest deadline first), each with daysLeft until close. Unlike gov.search or gov.digest, this ignores keywords and freshness - it is purely a time-window scan for last-minute bidding, bid deadline reminders and pipeline management.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | Closing within how many days (default 7). |
| naics | string | – | Optional NAICS filter to narrow the window. |
No output schema declared.
No examples provided.
gov.search ~221
Explore and answer questions about federal contract opportunities. Combine any filters - NAICS code, free-text keyword, set-aside type, posting window - and get full fields (title, agency, type, NAICS, set-aside, deadline, official posting date (postedDate) plus exact time (postedAt) where available, SAM.gov link). Use this when you need to research a specific market, match a capability, or compare opportunities. Data synced hourly via GovConAPI (latency ≤60 min); SAM fallback every 6h.
| Name | Type | Req | Description |
|---|---|---|---|
| days | number | – | How many days back to search (default 7). |
| keyword | string | – | Free-text keyword in the title, e.g. 'IT services'. Optional. |
| naics | string | – | NAICS code to filter by, e.g. '541511'. Optional - omit for all. |
| setAside | string | – | Set-aside filter: 8(a), WOSB, HUBZone, SDVOSB, SBA, or empty for all. Optional. |
No output schema declared.
No examples provided.
How do I install the GovContract Radar MCP server?
GovContract Radar is a hosted endpoint at https://gov.pixharvest.com/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 · gov.pixharvest.com
claude mcp add --transport http com-pixharvest-gov-contract-radar 'https://gov.pixharvest.com/mcp'
What is the GovContract Radar MCP server?
GovContract Radar is an MCP server listed in the public MCP registry as com.pixharvest/gov-contract-radar. US federal contracts: solicitations, set-asides, deadlines, awards, contractor profiles. Free. This page covers its hosted endpoint (https://gov.pixharvest.com/mcp).
Is the GovContract Radar MCP server safe to use?
GovContract Radar scores 0 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 GovContract Radar MCP server expose?
GovContract Radar exposes 5 tools: gov.search, gov.digest, gov.near_expiry, gov.awards, gov.company. Their descriptions and schemas cost roughly 674 tokens of context every time the server is loaded.
Does the GovContract Radar MCP server require authentication?
Its publisher declares no required credentials for GovContract Radar. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the GovContract Radar MCP server still maintained?
GovContract Radar has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 9 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.