# Tx Procurement (npm · @pipeworx/mcp-tx-procurement)

Texas State Procurement MCP — State cooperative-contract awards & vendor sales (keyless).

- Trust score: 67/100 (medium)
- Change this week: −11
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-06

## Components

- remote · `gateway.pipeworx.io`: 84/100, [markdown](https://verifymcp.io/servers/pipeworx-io-tx-procurement/tx-procurement-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-tx-procurement/tx-procurement-mcp)
- npm · `@pipeworx/mcp-tx-procurement`: 67/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-tx-procurement/pipeworx-mcp-tx-procurement.md), [page](https://verifymcp.io/servers/pipeworx-io-tx-procurement/pipeworx-mcp-tx-procurement)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-tx-procurement`
- 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**: 50/100
  - Malware scan not yet available for this package.
  - 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-tx-procurement).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 701 tokens (~350/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Tx Procurement MCP server?

Tx Procurement runs locally as an npm package, launched with npx -y @pipeworx/mcp-tx-procurement. 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-tx-procurement -- npx -y @pipeworx/mcp-tx-procurement
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-tx-procurement -- npx -y @pipeworx/mcp-tx-procurement
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-tx-procurement --command npx --arg -y --arg @pipeworx/mcp-tx-procurement
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-tx-procurement:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-tx-procurement"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add pipeworx-io-tx-procurement -t stdio -c npx -a -y @pipeworx/mcp-tx-procurement
```

### Other

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

## 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 67, −11)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.27
- [functional] Package version: 0.2.0 → 0.2.1

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (2)

### `tx_procurement_awards` (~471 tokens)

Search TEXAS STATE government contract awards & purchases from the official Texas Department of Information Resources (DIR) Cooperative Contract Sales data on data.texas.gov. Each result is a purchase a Texas public entity made against a DIR statewide cooperative contract: the awarding/purchasing customer (agency, university, city, county, or school district), the winning vendor (supplier), the dollar amount, the DIR contract number, the RFO/product description, brand, quantity, and order dates. Filter by vendor, agency/customer, keyword, fiscal year, contract number, and/or a minimum amount; results are ranked by dollar amount (biggest purchases first) by default. Use this for questions like "who won Texas state IT contracts", "biggest vendors to the Texas Health and Human Services Commission", or "Texas state cooperative-contract purchases for Oracle". This is TEXAS STATE data (not federal).

Input parameters:

- `agency` (string): Awarding/purchasing customer name — the buying agency, university, city, county or district (case-insensitive substring), e.g. "Health and Human Services", "Department of Criminal Justice", "Universi…
- `contract_number` (string): DIR contract number to match (case-insensitive substring), e.g. "DIR-TSO-2539", "DIR-CPO-5165".
- `fiscal_year` (number|string): Exact Texas fiscal year, e.g. 2024 (available: 2010 through 2025).
- `keyword` (string): Case-insensitive substring to match against the RFO/product description or brand name, e.g. "cloud", "laptop", "cybersecurity".
- `limit` (number|string): Max records to return (default 20, max 100).
- `min_amount` (number|string): Only return purchases whose amount is at least this many dollars, e.g. 100000.
- `offset` (number|string): Number of records to skip for pagination (default 0).
- `sort` (string): Sort order: "amount" = largest purchase first (default), "date" = most recent order date first.
- `vendor` (string): Winning vendor / supplier name to match (case-insensitive substring), e.g. "Dell", "Oracle", "AT&T".

### `tx_procurement_vendor` (~173 tokens)

Aggregate a vendor's TEXAS STATE cooperative-contract sales from the DIR Vendor Sales Report data on data.texas.gov: total dollars sold, number of purchase records, and a breakdown by awarding/purchasing agency (customer), by DIR contract, and by fiscal year. Matches the vendor name as a case-insensitive substring, so it also surfaces name variants (e.g. "Dell" matches "Dell Marketing LP"). Use this to size up a single vendor's business with the State of Texas. This is TEXAS STATE data (not federal).

Input parameters:

- `fiscal_year` (number|string): Optional: restrict to one fiscal year, e.g. 2024.
- `vendor` (string, required): Vendor / supplier name to aggregate (case-insensitive substring), e.g. "Dell", "Oracle", "AT&T".

## Diagnostics

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

## Score history

- 2026-11-06: 67
- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 78
- 2026-11-01: 78
- 2026-10-31: 78
- 2026-10-30: 78
- 2026-10-29: 78

## Common questions

### What is the Tx Procurement MCP server?

Tx Procurement is an MCP server listed in the public MCP registry as io.github.pipeworx-io/tx-procurement. Texas State Procurement MCP, State cooperative-contract awards & vendor sales (keyless). This page covers its npm package (@pipeworx/mcp-tx-procurement).

### Is the Tx Procurement MCP server safe to use?

Tx Procurement scores 67 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 Tx Procurement MCP server expose?

Tx Procurement exposes 2 tools: tx_procurement_awards, tx_procurement_vendor. Their descriptions and schemas cost roughly 644 tokens of context every time the server is loaded.

### Is the Tx Procurement MCP server still maintained?

Tx Procurement 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 Tx Procurement MCP server under?

Tx 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 Tx Procurement MCP server?

VerifyMCP ran 15 checks on Tx Procurement, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Tx Procurement: Malware scan. 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-tx-procurement
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-tx-procurement
- Repository: https://github.com/pipeworx-io/mcp-tx-procurement
- Website: https://pipeworx.io/packs/tx-procurement
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-tx-procurement/pipeworx-mcp-tx-procurement.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-tx-procurement/pipeworx-mcp-tx-procurement/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-tx-procurement/pipeworx-mcp-tx-procurement.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-tx-procurement/pipeworx-mcp-tx-procurement