com.dropwatchhq/govcon-recompete
REMOTE · RECOMPETE.DROPWATCHHQ.COM · SCANNED SEP 21
Predict federal contract recompetes: expiring contracts, likely competitors, win odds.
Available components
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 3 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability71
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 410 tokens (~136/item across 3 items; 3 tools + 0 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 Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 79% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
How do I install the com.dropwatchhq/govcon-recompete MCP server?
com.dropwatchhq/govcon-recompete is a hosted endpoint at https://recompete.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 · recompete.dropwatchhq.com
claude mcp add --transport http com-dropwatchhq-govcon-recompete 'https://recompete.dropwatchhq.com/mcp'
{
"mcpServers": {
"com-dropwatchhq-govcon-recompete": {
"url": "https://recompete.dropwatchhq.com/mcp"
}
}
} {
"servers": {
"com-dropwatchhq-govcon-recompete": {
"type": "http",
"url": "https://recompete.dropwatchhq.com/mcp"
}
}
} [mcp_servers.com-dropwatchhq-govcon-recompete] url = "https://recompete.dropwatchhq.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-dropwatchhq-govcon-recompete": {
"type": "remote",
"url": "https://recompete.dropwatchhq.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-dropwatchhq-govcon-recompete --url 'https://recompete.dropwatchhq.com/mcp' --transport streamable-http
mcp_servers:
com-dropwatchhq-govcon-recompete:
url: "https://recompete.dropwatchhq.com/mcp" {
"McpServers": {
"com-dropwatchhq-govcon-recompete": {
"Transport": "http",
"Url": "https://recompete.dropwatchhq.com/mcp"
}
}
} assistant mcp add com-dropwatchhq-govcon-recompete -t streamable-http -u 'https://recompete.dropwatchhq.com/mcp'
{
"mcpServers": {
"com-dropwatchhq-govcon-recompete": {
"type": "http",
"url": "https://recompete.dropwatchhq.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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 +1
- 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 +1
- Stability: 0.97 → pass security
- 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
- 30 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.
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://recompete.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 | f523b101d8872be90e10df9fcc8c8c6a |
| SANs: dropwatchhq.com, recompete.dropwatchhq.com, *.recompete.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 recompete.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://recompete.dropwatchhq.com/mcp | Verified | 200 | |
| http (plaintext) | http://recompete.dropwatchhq.com/mcp | Served over HTTP | 200 |
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 →
expiring_recompetes ~133
List federal contracts EXPIRING in a horizon window (period-of-performance end), with a winner prediction for each. Filter by NAICS and agency. This is the recompete pipeline feed.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | – |
| limit | number | – | Max contracts (default 20). |
| maxDays | number | – | Window ceiling in days (default 180). |
| minAmount | number | – | Minimum award $ (default 1,000,000). |
| minDays | number | – | Window floor in days (default 90). |
| naics | string | – | 6-digit NAICS. |
No output schema declared.
No examples provided.
lane_competitors ~76
Return the firms with the most recent award velocity in a NAICS (and optional agency) lane — i.e. the likely bidders on any recompete in that lane, ranked by recent wins and dollars.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | – |
| limit | number | – | Default 15. |
| naics | string | yes | – |
No output schema declared.
No examples provided.
predict_recompete ~201
Predict WHO will win an expiring federal contract recompete. Pass a contract identifier (USAspending generated_internal_id / award gid) OR a NAICS+incumbent pair. Returns the incumbent with an adjusted incumbent-advantage probability plus top likely competitors ranked by recent award velocity in the NAICS/agency lane, the BASE RATES used, sample size, and an honest confidence band. Probabilistic estimate from PUBLIC USAspending data — not insider info.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Awarding agency name (optional, sharpens the lane). |
| gid | string | – | USAspending generated_internal_id (award gid). Best input. |
| incumbent | string | – | Incumbent contractor name (required if no gid). |
| naics | string | – | 6-digit NAICS, used to build the competitor field (required if no gid). |
| topN | number | – | Number of competitors to return (default 5). |
No output schema declared.
No examples provided.
What is the com.dropwatchhq/govcon-recompete MCP server?
com.dropwatchhq/govcon-recompete is an MCP server listed in the public MCP registry as com.dropwatchhq/govcon-recompete. Predict federal contract recompetes: expiring contracts, likely competitors, win odds. This page covers its hosted endpoint (https://recompete.dropwatchhq.com/mcp).
Is the com.dropwatchhq/govcon-recompete MCP server safe to use?
com.dropwatchhq/govcon-recompete scores 69 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-recompete MCP server expose?
com.dropwatchhq/govcon-recompete exposes 3 tools: predict_recompete, expiring_recompetes, lane_competitors. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.
Does the com.dropwatchhq/govcon-recompete MCP server require authentication?
No. We connected to com.dropwatchhq/govcon-recompete without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the com.dropwatchhq/govcon-recompete MCP server still maintained?
com.dropwatchhq/govcon-recompete 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.