# Zovo Contract Awards (remote · contract-awards.zovo.one)

Federal award market reports

- Trust score: 79/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `contract-awards.zovo.one`: 79/100 (this document), [markdown](https://verifymcp.io/servers/theluckystrike-contract-awards/contract-awards.md), [page](https://verifymcp.io/servers/theluckystrike-contract-awards/contract-awards)

## Channel facts

- Endpoint: `https://contract-awards.zovo.one/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 69/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 833 tokens (~277/item across 3 items; 2 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the Zovo Contract Awards MCP server?

Zovo Contract Awards is a hosted endpoint at https://contract-awards.zovo.one/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.

### Claude

```bash
claude mcp add --transport http theluckystrike-contract-awards 'https://contract-awards.zovo.one/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "theluckystrike-contract-awards": {
      "url": "https://contract-awards.zovo.one/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "theluckystrike-contract-awards": {
      "type": "http",
      "url": "https://contract-awards.zovo.one/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.theluckystrike-contract-awards]
url = "https://contract-awards.zovo.one/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "theluckystrike-contract-awards": {
      "type": "remote",
      "url": "https://contract-awards.zovo.one/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add theluckystrike-contract-awards --url 'https://contract-awards.zovo.one/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  theluckystrike-contract-awards:
    url: "https://contract-awards.zovo.one/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "theluckystrike-contract-awards": {
      "Transport": "http",
      "Url": "https://contract-awards.zovo.one/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add theluckystrike-contract-awards -t streamable-http -u 'https://contract-awards.zovo.one/mcp'
```

### Other

```json
{
  "mcpServers": {
    "theluckystrike-contract-awards": {
      "type": "http",
      "url": "https://contract-awards.zovo.one/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 78, +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.

### 2026-10-31 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 75, +1)

- [security] Resource “contract-awards-widget” now points somewhere else: ui://widget/contract-awards-v6-1.0.0-a00a74b89ce2a5a79e8799b2e516432699b15bd1bb2e33ae622cace3ff237a2b.html → ui://widget/contract-awards-v6-1.0.0-753aca3f0e68bb32501780a7236d270a5af30a094adde50a0b27fb350c9aac76.html

### 2026-10-25 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-23 (score 73, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-22 (score 72)

First indexed and scored.

## MCP tools (2)

### `search_contract_awards` (~399 tokens)

Search contract awards

Use this when the user wants government contracts search, federal contract awards by NAICS code, contracts expiring soon or federal market research. Queries live public award records and makes a multi-sheet Excel report with recipient and agency totals. At least one search filter; up to 300 rows, dates from 2007-10-01 through today UTC, prime contracts or IDVs. Totals cover returned rows; period obligations are separate aggregates. Do not use for open solicitations, bids, subcontracts or classified awards.

Input parameters:

- `agencies` (array): Up to 5 values, each up to 150 characters. Example: ["VA"].
- `award_category` (string): Award group, default contracts. Example: idvs uses last date to order for the ending window.
- `end_date` (string): Last action date, no later than today UTC; default today UTC. Example: 2026-10-01.
- `keywords` (array): Up to 5 values, each up to 50 characters. Example: ["janitorial"].
- `max_results` (integer): Maximum award rows, 1 to 300, default 100. Example: 200.
- `naics_codes` (array): Up to 10 values, each up to 6 characters. Example: ["541512"].
- `psc_codes` (array): Up to 10 values, each up to 4 characters. Example: ["S201"].
- `recipients` (array): Up to 10 values, each up to 80 characters. Example: ["Booz Allen"].
- `start_date` (string): First action date, YYYY-MM-DD, from 2007-10-01. Default end minus 365 days. Example: 2025-10-01.
- `states` (array): Up to 10 values, each up to 2 characters. Example: ["TX"].

Output parameters:

- `agencies` (array)
- `awards` (array)
- `capped` (boolean|null)
- `competitors` (array)
- `downloads` (object)
- `ending` (array)
- `ending_count` (number)
- `matched`
- `mode` (string)
- `notes` (array)
- `period_agencies` (array)
- `period_recipients` (array)
- `recipients` (array)
- `returned` (number)
- `rows_without_amount` (number)
- `source` (string)
- `summary` (string)
- `total` (string): USD with two decimal places, for example $150.03 or -$40,013.22.

### `compare_competitor_awards` (~361 tokens)

Compare competitor awards

Use this when the user wants competitor contract awards, government contract award history or recompete research. Looks up live public federal awards for one to ten competitor names and makes an Excel comparison. Up to 25 returned awards per competitor; names match text and may include subsidiaries; dates from 2007-10-01 to today UTC. Failed items leave successful competitors available. Do not use for corporate identity verification, open solicitations or bids.

Input parameters:

- `agencies` (array): Up to 5 values, each up to 150 characters. Example: ["VA"].
- `award_category` (string): Award group, default contracts. Example: idvs uses last date to order for the ending window.
- `competitors` (array): Up to 10 values, each up to 80 characters. Example: ["Leidos", "SAIC"].
- `end_date` (string): Last action date, no later than today UTC; default today UTC. Example: 2026-10-01.
- `keywords` (array): Up to 5 values, each up to 50 characters. Example: ["janitorial"].
- `naics_codes` (array): Up to 10 values, each up to 6 characters. Example: ["541512"].
- `psc_codes` (array): Up to 10 values, each up to 4 characters. Example: ["S201"].
- `start_date` (string): First action date, YYYY-MM-DD, from 2007-10-01. Default end minus 365 days. Example: 2025-10-01.
- `states` (array): Up to 10 values, each up to 2 characters. Example: ["TX"].

Output parameters:

- `agencies` (array)
- `awards` (array)
- `capped` (boolean|null)
- `competitors` (array)
- `downloads` (object)
- `ending` (array)
- `ending_count` (number)
- `matched`
- `mode` (string)
- `notes` (array)
- `period_agencies` (array)
- `period_recipients` (array)
- `recipients` (array)
- `returned` (number)
- `rows_without_amount` (number)
- `source` (string)
- `summary` (string)
- `total` (string): USD with two decimal places, for example $150.03 or -$40,013.22.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/theluckystrike-contract-awards/contract-awards#diagnostics

## Score history

- 2026-11-05: 79
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 76
- 2026-10-29: 76
- 2026-10-28: 75
- 2026-10-27: 75
- 2026-10-26: 74
- 2026-10-25: 74
- 2026-10-24: 73
- 2026-10-23: 73
- 2026-10-22: 72

## Common questions

### What is the Zovo Contract Awards MCP server?

Zovo Contract Awards is an MCP server listed in the public MCP registry as io.github.theluckystrike/contract-awards. Federal award market reports. This page covers its hosted endpoint (https://contract-awards.zovo.one/mcp).

### Is the Zovo Contract Awards MCP server safe to use?

Zovo Contract Awards scores 79 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 Zovo Contract Awards MCP server expose?

Zovo Contract Awards exposes 2 tools: search_contract_awards, compare_competitor_awards. Their descriptions and schemas cost roughly 760 tokens of context every time the server is loaded.

### Does the Zovo Contract Awards MCP server require authentication?

No. We connected to Zovo Contract Awards without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Zovo Contract Awards MCP server still maintained?

Zovo Contract Awards 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.

## Links

- Remote endpoint: https://contract-awards.zovo.one/mcp
- Website: https://contract-awards.zovo.one/
- Changelog RSS feed: https://verifymcp.io/servers/theluckystrike-contract-awards/contract-awards.xml
- Changelog JSON feed: https://verifymcp.io/servers/theluckystrike-contract-awards/contract-awards.json
- HTML version of this page: https://verifymcp.io/servers/theluckystrike-contract-awards/contract-awards