# Dod Contract Announcements (npm · @pipeworx/mcp-dod-contract-announcements)

DoD Contract Announcements MCP — the daily press-release feed of every US defense contract award…

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `gateway.pipeworx.io`: 72/100, [markdown](https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/dod-contract-announcements-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/dod-contract-announcements-mcp)
- npm · `@pipeworx/mcp-dod-contract-announcements`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/pipeworx-mcp-dod-contract-announcements.md), [page](https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/pipeworx-mcp-dod-contract-announcements)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-dod-contract-announcements`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-06.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-dod-contract-announcements).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 856 tokens (~214/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.

## Install

### How do I install the Dod Contract Announcements MCP server?

Dod Contract Announcements runs locally as an npm package, launched with npx -y @pipeworx/mcp-dod-contract-announcements. 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 pipeworx-io-dod-contract-announcements -- npx -y @pipeworx/mcp-dod-contract-announcements
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-dod-contract-announcements": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-dod-contract-announcements"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-dod-contract-announcements": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-dod-contract-announcements"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-dod-contract-announcements -- npx -y @pipeworx/mcp-dod-contract-announcements
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-dod-contract-announcements": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-dod-contract-announcements"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-dod-contract-announcements --command npx --arg -y --arg @pipeworx/mcp-dod-contract-announcements
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-dod-contract-announcements:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-dod-contract-announcements"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-dod-contract-announcements": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-dod-contract-announcements"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-dod-contract-announcements -t stdio -c npx -a -y @pipeworx/mcp-dod-contract-announcements
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-dod-contract-announcements": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-dod-contract-announcements"
      ]
    }
  }
}
```

## 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-06 (score 83, +1)

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

### 2026-11-04 (score 82, +1)

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

### 2026-11-02 (score 81, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-01 (score 80, +1)

- [functional regression] Security disclosure: fail → unverified
- [functional improvement] Stability: unverified → 0.10
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (4)

### `dod_awards_recent` (~302 tokens)

Most recent US Department of War (formerly Department of Defense) contract award announcements — Pentagon contracts today, this week, or over any recent window, newest first. Every contract of $7.5M or more is announced here on the business day it is signed, which is weeks ahead of the same award appearing in FPDS/USAspending. Filter by military service/agency (ARMY, NAVY, AIR FORCE, DEFENSE LOGISTICS AGENCY, U.S. TRANSPORTATION COMMAND, DEFENSE ADVANCED RESEARCH PROJECTS AGENCY, DEFENSE HEALTH AGENCY, U.S. SPECIAL OPERATIONS COMMAND, and others) and a minimum award amount. Answers "what defense contracts were announced today", "recent DoD/Pentagon contract awards", "who won a defense contract this week".

Input parameters:

- `days` (number|string): How many days back from today to include (default 7).
- `limit` (number|string): Max awards to return (1-100, default 25).
- `min_amount` (number|string): Only awards at or above this dollar amount. Note: on rows where shared_award is true, amount is the combined multi-contractor program value, not one contractor's share.
- `service` (string): Restrict to one branch/agency, e.g. "ARMY", "NAVY", "AIR FORCE", "DEFENSE LOGISTICS AGENCY". Matched case-insensitively.

### `dod_awards_search` (~226 tokens)

Search US Department of War (Pentagon) contract award announcements by contractor name or by keyword in the award description — "has Lockheed Martin won a defense contract", "defense contracts for hypersonic missiles", "Pentagon awards mentioning drone swarms". At least one of query or contractor is required. Optionally restrict to awards announced on or after a given date. This is the leading, weeks-ahead-of-USAspending record of an award; combine with the usaspending pack for the fully structured historical record.

Input parameters:

- `contractor` (string): Free-text match (case-insensitive) against the contractor name, e.g. "Lockheed Martin", "Raytheon".
- `limit` (number|string): Max awards to return (1-100, default 25).
- `query` (string): Free-text match (case-insensitive) against the award description paragraph, e.g. "hypersonic", "F-35 sustainment", "shipbuilding".
- `since` (string): Only awards announced on or after this date (YYYY-MM-DD).

### `dod_awards_top` (~198 tokens)

Ranks contractors or military services/agencies by total defense contract award value over a recent window — "who are the top defense contractors this month", "which service branch awarded the most this quarter". Ranks by money actually obligated. Two kinds of award are held out of that total and reported alongside it, because folding either one in yields a large, plausible-looking number that means nothing: shared_award rows (a multiple-award paragraph whose amount is the COMBINED program value across every winner, not one company's share) and ceiling/not-to-exceed awards (a lifetime maximum on a multi-year contract, not money awarded in this window).

Input parameters:

- `by` (string): Rank by "contractor" (default) or "service".
- `days` (number|string): Window size in days, ending today (default 30).
- `limit` (number|string): Max ranked entries to return (1-100, default 20).

### `dod_awards_coverage` (~73 tokens)

Reports what DoD/Pentagon contract announcement data is currently available: total row count, the earliest and latest announcement date on file, and a per-service breakdown of counts. Use to gauge coverage before relying on it for a historical range — "how far back does Pipeworx's Pentagon contract data go".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/pipeworx-mcp-dod-contract-announcements#diagnostics

## Score history

- 2026-11-06: 83
- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Dod Contract Announcements MCP server?

Dod Contract Announcements is an MCP server listed in the public MCP registry as io.github.pipeworx-io/dod-contract-announcements. DoD Contract Announcements MCP, the daily press-release feed of every US defense contract award… This page covers its npm package (@pipeworx/mcp-dod-contract-announcements).

### Is the Dod Contract Announcements MCP server safe to use?

Dod Contract Announcements scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 6 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Dod Contract Announcements MCP server expose?

Dod Contract Announcements exposes 4 tools: dod_awards_recent, dod_awards_search, dod_awards_top, dod_awards_coverage. Their descriptions and schemas cost roughly 799 tokens of context every time the server is loaded.

### Is the Dod Contract Announcements MCP server still maintained?

Dod Contract Announcements is still listed as active in the MCP registry. We last reached this channel on 6 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Dod Contract Announcements MCP server under?

Dod Contract Announcements declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Dod Contract Announcements MCP server?

VerifyMCP ran 16 checks on Dod Contract Announcements, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-dod-contract-announcements
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-dod-contract-announcements
- Repository: https://github.com/pipeworx-io/mcp-dod-contract-announcements
- Website: https://pipeworx.io/packs/dod-contract-announcements
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/pipeworx-mcp-dod-contract-announcements.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/pipeworx-mcp-dod-contract-announcements/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/pipeworx-mcp-dod-contract-announcements.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-dod-contract-announcements/pipeworx-mcp-dod-contract-announcements