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.

com.dropwatchhq/govcon-feed

REMOTE · GOVCON.DROPWATCHHQ.COM · SCANNED SEP 21

Track US federal contract changes: what changed, deltas, competitor award watch, award search.

0 this week 66 Trust /100
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 Security46
Transport & Reachability100
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 474 tokens (~118/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 Coverage77
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 31% 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 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
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the com.dropwatchhq/govcon-feed MCP server?

com.dropwatchhq/govcon-feed is a hosted endpoint at https://govcon.dropwatchhq.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 · govcon.dropwatchhq.com

# add to Claude Code
claude mcp add --transport http com-dropwatchhq-govcon-feed 'https://govcon.dropwatchhq.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-dropwatchhq-govcon-feed": {
      "url": "https://govcon.dropwatchhq.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-dropwatchhq-govcon-feed": {
      "type": "http",
      "url": "https://govcon.dropwatchhq.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-dropwatchhq-govcon-feed]
url = "https://govcon.dropwatchhq.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-dropwatchhq-govcon-feed": {
      "type": "remote",
      "url": "https://govcon.dropwatchhq.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-dropwatchhq-govcon-feed --url 'https://govcon.dropwatchhq.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-dropwatchhq-govcon-feed:
    url: "https://govcon.dropwatchhq.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-dropwatchhq-govcon-feed": {
      "Transport": "http",
      "Url": "https://govcon.dropwatchhq.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-dropwatchhq-govcon-feed -t streamable-http -u 'https://govcon.dropwatchhq.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-dropwatchhq-govcon-feed": {
      "type": "http",
      "url": "https://govcon.dropwatchhq.com/mcp"
    }
  }
}

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

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.

  • 26 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 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
  • 31 Jul 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
  • 27 Jul 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
  • 26 Jul 26 0

    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 21 Sept 2026 · Probed https://govcon.dropwatchhq.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=dropwatchhq.com CN=WE1,O=Google Trust Services,C=US 19 Aug 2026 17 Nov 2026 ECDSA 256 ECDSA-SHA256 ffa96d37178b42890ed8b9560fedc78e
SANs: dropwatchhq.com, govcon.dropwatchhq.com, *.govcon.dropwatchhq.com
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 govcon.dropwatchhq.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
dropwatchhq.com. 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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://govcon.dropwatchhq.com/mcp Verified 200
http (plaintext) http://govcon.dropwatchhq.com/mcp Served over HTTP 200
MCP tools · 4 exposed · ~474 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
competitor_watch ~47

Given a contractor name, return their recent federal awards (last 180d live) plus any win/lose/modify events the feed has accrued over time.

NameTypeReqDescription
contractorstringyes

No output schema declared.

No examples provided.

delta_digest ~127

Weekly delta digest for a filter: new awards, modifications, and contracts EXPIRING in the next N days (recompete opportunities). Best signal for BD teams.

NameTypeReqDescription
agencystring
daysnumberLookback days for new/modified (default 7).
expiringDaysnumberExpiry horizon, 90 or 180 (default 90).
keywordstring
maxAmountnumber
minAmountnumber
naicsarray
recipientstring

No output schema declared.

No examples provided.

search_awards ~120

Direct live search of US federal awards (USAspending.gov) by NAICS, agency, recipient, keyword, date range, and $ range. Use for ad-hoc lookups.

NameTypeReqDescription
agencystring
endstring
keywordstring
limitnumberDefault 50, max 200.
maxAmountnumber
minAmountnumber
naicsarray
recipientstring
startstring

No output schema declared.

No examples provided.

whats_changed_since ~180

Return federal contract awards that are NEW or MODIFIED since a cursor token. Pass the cursor from a prior call to get only changes since then (cursor = your bookmark). Filter by NAICS, awarding agency, recipient/contractor, keyword, and $ range. This is the GovCon delta feed's core lock-in primitive.

NameTypeReqDescription
agencystringAwarding agency name substring, e.g. 'Defense'.
cursorstringOpaque cursor from a previous response; omit for first call.
keywordstring
limitnumberMax changes to return (default 100).
maxAmountnumber
minAmountnumber
naicsarrayNAICS code prefixes, e.g. ['5415'].
recipientstringContractor name substring.

No output schema declared.

No examples provided.

Common questions

What is the com.dropwatchhq/govcon-feed MCP server?

com.dropwatchhq/govcon-feed is an MCP server listed in the public MCP registry as com.dropwatchhq/govcon-feed. Track US federal contract changes: what changed, deltas, competitor award watch, award search. This page covers its hosted endpoint (https://govcon.dropwatchhq.com/mcp).

Is the com.dropwatchhq/govcon-feed MCP server safe to use?

com.dropwatchhq/govcon-feed scores 66 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 com.dropwatchhq/govcon-feed MCP server expose?

com.dropwatchhq/govcon-feed exposes 4 tools: whats_changed_since, delta_digest, competitor_watch, search_awards. Their descriptions and schemas cost roughly 474 tokens of context every time the server is loaded.

Does the com.dropwatchhq/govcon-feed MCP server require authentication?

No. We connected to com.dropwatchhq/govcon-feed without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.dropwatchhq/govcon-feed MCP server still maintained?

com.dropwatchhq/govcon-feed is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.