Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Zovo Contract Awards

REMOTE · CONTRACT-AWARDS.ZOVO.ONE

Federal award market reports

+3 this week 78 Trust /100

Last scanned (21 hours ago)

Scores higher than 76% of remote servers

Reachable. Last reached 4 Nov 2026.

Category CRM and Sales

Trust breakdown (7 categories)

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 Security80
Transport & Reachability100
Schema Quality & AI Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management43
  • Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 2 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Changelog

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.

  • 2 Nov 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.

  • 31 Oct 26 +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.

  • 29 Oct 26 +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.

  • 27 Oct 26 +1
    • 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 security
  • 25 Oct 26 +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.

  • 23 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 22 Oct 26 72

    First indexed and scored.

Diagnostics

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://contract-awards.zovo.one/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=zovo.one CN=WE1,O=Google Trust Services,C=US 21 Oct 2026 19 Jan 2027 ECDSA 256 ECDSA-SHA256 24e34912c9c2e020e808a4e66efb37b
SANs: zovo.one, contract-awards.zovo.one, *.contract-awards.zovo.one
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of contract-awards.zovo.one. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
one. present 64939 8 Verified
zovo.one. absent 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
Header Value
strict-transport-security max-age=15552000; includeSubDomains; preload
x-content-type-options nosniff

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://contract-awards.zovo.one/mcp Verified 200
http (plaintext) http://contract-awards.zovo.one/mcp HTTPS enforced 301 https://contract-awards.zovo.one/mcp
MCP tools · 2 exposed · ~760 tokens

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 →

Tool Tokens
compare_competitor_awards ~361

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.

NameTypeReqDescription
agenciesarray–Up to 5 values, each up to 150 characters. Example: ["VA"].
award_categorystring–Award group, default contracts. Example: idvs uses last date to order for the ending window.
competitorsarray–Up to 10 values, each up to 80 characters. Example: ["Leidos", "SAIC"].
end_datestring–Last action date, no later than today UTC; default today UTC. Example: 2026-10-01.
keywordsarray–Up to 5 values, each up to 50 characters. Example: ["janitorial"].
naics_codesarray–Up to 10 values, each up to 6 characters. Example: ["541512"].
psc_codesarray–Up to 10 values, each up to 4 characters. Example: ["S201"].
start_datestring–First action date, YYYY-MM-DD, from 2007-10-01. Default end minus 365 days. Example: 2025-10-01.
statesarray–Up to 10 values, each up to 2 characters. Example: ["TX"].
NameTypeReqDescription
agenciesarrayyes–
awardsarrayyes–
cappedboolean|nullyes–
competitorsarrayyes–
downloadsobjectyes–
endingarrayyes–
ending_countnumberyes–
matched–yes–
modestringyes–
notesarrayyes–
period_agenciesarrayyes–
period_recipientsarrayyes–
recipientsarrayyes–
returnednumberyes–
rows_without_amountnumberyes–
sourcestringyes–
summarystringyes–
totalstringyesUSD with two decimal places, for example $150.03 or -$40,013.22.

No examples provided.

search_contract_awards ~399

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.

NameTypeReqDescription
agenciesarray–Up to 5 values, each up to 150 characters. Example: ["VA"].
award_categorystring–Award group, default contracts. Example: idvs uses last date to order for the ending window.
end_datestring–Last action date, no later than today UTC; default today UTC. Example: 2026-10-01.
keywordsarray–Up to 5 values, each up to 50 characters. Example: ["janitorial"].
max_resultsinteger–Maximum award rows, 1 to 300, default 100. Example: 200.
naics_codesarray–Up to 10 values, each up to 6 characters. Example: ["541512"].
psc_codesarray–Up to 10 values, each up to 4 characters. Example: ["S201"].
recipientsarray–Up to 10 values, each up to 80 characters. Example: ["Booz Allen"].
start_datestring–First action date, YYYY-MM-DD, from 2007-10-01. Default end minus 365 days. Example: 2025-10-01.
statesarray–Up to 10 values, each up to 2 characters. Example: ["TX"].
NameTypeReqDescription
agenciesarrayyes–
awardsarrayyes–
cappedboolean|nullyes–
competitorsarrayyes–
downloadsobjectyes–
endingarrayyes–
ending_countnumberyes–
matched–yes–
modestringyes–
notesarrayyes–
period_agenciesarrayyes–
period_recipientsarrayyes–
recipientsarrayyes–
returnednumberyes–
rows_without_amountnumberyes–
sourcestringyes–
summarystringyes–
totalstringyesUSD with two decimal places, for example $150.03 or -$40,013.22.

No examples provided.

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.

remote · contract-awards.zovo.one

# add to Claude Code
claude mcp add --transport http theluckystrike-contract-awards 'https://contract-awards.zovo.one/mcp'
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 78 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 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.