Dod Contract Announcements
NPM · @PIPEWORX/MCP-DOD-CONTRACT-ANNOUNCEMENTS · 2 COMPONENTS
DoD Contract Announcements MCP — the daily press-release feed of every US defense contract award…
Available components
Last scanned (6 hours ago)
Scores higher than 75% of npm servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-dod-contract-announcements). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability64
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 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
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 5 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 +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.
- 4 Nov 26 +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.
- 2 Nov 26 +1
- Security disclosure: unverified → fail ▼ functional
- 1 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-dod-contract-announcements@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-dod-contract-announcements |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-dod-contract-announcements/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617553420 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d80af7532b26a80727ee94714bb4d2c38f54aec135a71442fd7c6bc7e8d4a6fffbc55bf09fb15c40364bd686ac3ed5146c3483731052bcec4b18c6bb7 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
dod_awards_coverage ~73
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".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dod_awards_recent ~302
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
dod_awards_search ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
dod_awards_top ~198
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-dod-contract-announcements
claude mcp add pipeworx-io-dod-contract-announcements -- npx -y @pipeworx/mcp-dod-contract-announcements
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.