Ny Procurement
NPM · @PIPEWORX/MCP-NY-PROCUREMENT · 2 COMPONENTS
New York State Procurement MCP — State contract awards & procurement (keyless).
Available components
Last scanned (17 hours ago)
Scores higher than 69% 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-ny-procurement). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability59
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 688 tokens (~344/item across 2 items; 2 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 2 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
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 +16
- Malware scan: unverified → pass ▲ security
- 3 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 +1
- Security disclosure: fail → unverified ▼ functional
- 29 Oct 26 78
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-ny-procurement@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-ny-procurement |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-ny-procurement/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3679517602 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:5f5e5287975e0c92e84a4bf1908b4644a6ae1f3cf2fbb6262d487436f27556b41d6f313bb90777d4b82502a6529a46ba6fad9b335c66583323a197971 |
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 →
ny_procurement_awards ~454
Search NEW YORK STATE government contract awards & procurement from the official Procurement Report for State Authorities on data.ny.gov (the §2800 Public Authorities Law filings collected by the NY Authorities Budget Office). Each result is a procurement contract awarded by a New York State authority (the awarding agency) with the winning vendor, the contract dollar amount, the procurement type, the award/solicitation process, the description of goods/services, and award/begin dates. Filter by vendor, awarding agency/authority, keyword, procurement type, fiscal year, and/or a minimum amount; results are ranked by contract amount (biggest awards first) by default. Use this for questions like "who won the biggest New York State contracts", "top vendors to the Metropolitan Transportation Authority", or "NY state software contracts". This is NEW YORK STATE data (not federal, not New York City).
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | – | Awarding NY State authority / agency name (case-insensitive substring), e.g. "Metropolitan Transportation Authority", "Power Authority", "Dormitory Authority". |
| fiscal_year | number|string | – | Reporting fiscal year (calendar year of the fiscal-year-end date), e.g. 2022. Matches contracts whose fiscal_year_end_date falls in that year. |
| keyword | string | – | Case-insensitive substring to match against the procurement description, e.g. "software", "construction", "consulting". |
| limit | number|string | – | Max records to return (default 20, max 100). |
| min_amount | number|string | – | Only return awards whose contract amount is at least this many dollars, e.g. 1000000. |
| offset | number|string | – | Number of records to skip for pagination (default 0). |
| procurement_type | string | – | Procurement type substring, e.g. "Technology - Software", "Construction", "Consulting Services", "Commodities/Supplies". |
| sort | string | – | Sort order: "amount" = largest contract first (default), "date" = most recent award date first. |
| vendor | string | – | Winning vendor name to match (case-insensitive substring), e.g. "IBM", "Turner Construction". |
No output schema declared.
No examples provided.
ny_procurement_vendor ~177
Aggregate a vendor's NEW YORK STATE contract awards from the Procurement Report for State Authorities on data.ny.gov: total dollars awarded, number of contracts, and a breakdown by awarding agency/authority and by fiscal year. Matches the vendor name as a case-insensitive substring, so it also surfaces name variants (e.g. "IBM CORP" vs "IBM LC LODGING"). Use this to size up a single vendor's business with New York State authorities. This is NEW YORK STATE data (not federal, not New York City).
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year | number|string | – | Optional: restrict to one reporting fiscal year (calendar year of the fiscal-year-end date), e.g. 2022. |
| vendor | string | yes | Vendor name to aggregate (case-insensitive substring), e.g. "Deloitte", "IBM". |
No output schema declared.
No examples provided.
How do I install the Ny Procurement MCP server?
Ny Procurement runs locally as an npm package, launched with npx -y @pipeworx/mcp-ny-procurement. 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-ny-procurement
claude mcp add pipeworx-io-ny-procurement -- npx -y @pipeworx/mcp-ny-procurement
What is the Ny Procurement MCP server?
Ny Procurement is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ny-procurement. New York State Procurement MCP, State contract awards & procurement (keyless). This page covers its npm package (@pipeworx/mcp-ny-procurement).
Is the Ny Procurement MCP server safe to use?
Ny Procurement scores 81 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 Ny Procurement MCP server expose?
Ny Procurement exposes 2 tools: ny_procurement_awards, ny_procurement_vendor. Their descriptions and schemas cost roughly 631 tokens of context every time the server is loaded.
Is the Ny Procurement MCP server still maintained?
Ny Procurement 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 Ny Procurement MCP server under?
Ny Procurement 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 Ny Procurement MCP server?
VerifyMCP ran 16 checks on Ny Procurement, 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.