Us Gov Contracts
NPM · @PIPEWORX/MCP-US-GOV-CONTRACTS · 2 COMPONENTS
US Government Contracts MCP — awarded state & local government contracts, normalized across…
Available components
Last scanned (7 hours ago)
Scores higher than 72% 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-us-gov-contracts). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 677 tokens (~225/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 Management23
- Stability observed for 7 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 3 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
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.
- 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.
- 1 Nov 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.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-us-gov-contracts@0.5.0
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-us-gov-contracts |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-us-gov-contracts/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560850235 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:b92e37e93212567a63ebbe603281dd44fe5d5b48dca79a71ba5bdb1227358a9e85f5382503879446ea6823369473dde7afb48b62ec56fff72089d035c |
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 →
gov_contracts_jurisdictions ~73
List the US state & local jurisdictions covered by this pack, split into contract-award jurisdictions (gov_contracts_search) and spending/checkbook jurisdictions (gov_spending_search), with each one's key, level (state/county/city), data platform, source dataset URL, and live record count.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
gov_contracts_search ~294
Search AWARDED US state & local government contracts, normalized across jurisdictions (keyless open data). Filter by vendor (winning supplier), keyword (contract title/description), awarding agency, and minimum dollar amount. Covers state and county contract registries — pass a `jurisdiction` key (see gov_contracts_jurisdictions) to target one, or omit it to search all covered jurisdictions at once. Returns each contract with its ID, vendor, title, agency, amount, and dates. This is STATE/LOCAL award data (for federal contracts use USAspending/SAM tools).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Awarding agency/department to match (case-insensitive substring). Not all jurisdictions carry an agency field. |
| jurisdiction | string | – | Jurisdiction key to target (e.g. "tx", "wa", "king-county-wa"). Omit to search all covered jurisdictions. Use gov_contracts_jurisdictions to list keys. |
| keyword | string | – | Match against contract title/description (case-insensitive substring), e.g. "software", "road". |
| limit | number|string | – | Max contracts per jurisdiction (default 20, max 100). |
| min_amount | number|string | – | Only contracts whose value is at least this many dollars. |
| vendor | string | – | Winning vendor/supplier name to match (case-insensitive substring), e.g. "Microsoft". |
No output schema declared.
No examples provided.
gov_spending_search ~252
Search US STATE government spending / vendor payments — the 'checkbook' data of what an agency actually PAID a vendor (distinct from an awarded contract's value). Keyless. Filter by vendor, awarding agency, spending category keyword, and minimum amount. Pass a `jurisdiction` key (see gov_contracts_jurisdictions) to target one state, or omit it to search all covered states. Returns vendor, agency, amount, category, and fiscal year. Use gov_contracts_search for awarded contracts; use this for actual payments/expenditures.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Paying agency/department to match (case-insensitive substring). |
| jurisdiction | string | – | State key to target (e.g. "nj", "vt", "or", "md", "mo"). Omit to search all covered states. |
| keyword | string | – | Match against the spending category/description (case-insensitive substring). |
| limit | number|string | – | Max records per state (default 20, max 100). |
| min_amount | number|string | – | Only payments of at least this many dollars. |
| vendor | string | – | Vendor/payee name to match (case-insensitive substring). |
No output schema declared.
No examples provided.
How do I install the Us Gov Contracts MCP server?
Us Gov Contracts runs locally as an npm package, launched with npx -y @pipeworx/mcp-us-gov-contracts. 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-us-gov-contracts
claude mcp add pipeworx-io-us-gov-contracts -- npx -y @pipeworx/mcp-us-gov-contracts
What is the Us Gov Contracts MCP server?
Us Gov Contracts is an MCP server listed in the public MCP registry as io.github.pipeworx-io/us-gov-contracts. US Government Contracts MCP, awarded state & local government contracts, normalized across… This page covers its npm package (@pipeworx/mcp-us-gov-contracts).
Is the Us Gov Contracts MCP server safe to use?
Us Gov Contracts scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 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 Us Gov Contracts MCP server expose?
Us Gov Contracts exposes 3 tools: gov_contracts_search, gov_spending_search, gov_contracts_jurisdictions. Their descriptions and schemas cost roughly 619 tokens of context every time the server is loaded.
Is the Us Gov Contracts MCP server still maintained?
Us Gov Contracts is still listed as active in the MCP registry. We last reached this channel on 5 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 Us Gov Contracts MCP server under?
Us Gov Contracts 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 Us Gov Contracts MCP server?
VerifyMCP ran 16 checks on Us Gov Contracts, 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.