# Crs Reports (npm · @pipeworx/mcp-crs-reports)

Congressional Research Service reports — Congress's own nonpartisan analysis, searchable and…

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-crs-reports`
- 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-crs-reports).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 6 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 833 tokens (~208/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 Crs Reports MCP server?

Crs Reports runs locally as an npm package, launched with npx -y @pipeworx/mcp-crs-reports. 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-crs-reports -- npx -y @pipeworx/mcp-crs-reports
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-crs-reports -- npx -y @pipeworx/mcp-crs-reports
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-crs-reports --command npx --arg -y --arg @pipeworx/mcp-crs-reports
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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, +6)

- [security improvement] Source repository: unverified → pass

### 2026-11-05 (score 77, −5)

- [security regression] Provenance: pass → unverified

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

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

### 2026-11-01 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 65, −15)

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

### 2026-10-30 (score 80, +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.

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

First indexed and scored.

## MCP tools (4)

### `crs_search` (~312 tokens)

Find Congressional Research Service (CRS) reports on a policy topic, statute or programme and get their titles, summaries, topics, authors, publication dates and report numbers. CRS is the nonpartisan research service that writes explanatory analysis for Congress: what a law does, how a federal programme works, what the policy options are, what a proposal would cost. Covers 14,000+ current reports back to 2018 across every subject Congress legislates on — trade, health, immigration, defense, tax, energy, housing. Ranks titles and CRS summaries; use crs_report to read a report in full.

Input parameters:

- `author` (string): A CRS analyst, exactly as CRS credits them.
- `limit` (number): Results to return, 1–50. Default 10.
- `product_class` (string): CRS product family: Reports (long R/RL/RS reports), Resources (two-page In Focus), Posts (Insight and Legal Sidebar), Infographics, Testimony.
- `published_before` (string): Latest publication date, YYYY-MM-DD.
- `published_since` (string): Earliest publication date, YYYY-MM-DD.
- `query` (string): What to search for. Supports quoted phrases and a leading minus to exclude: "section 232" tariffs -steel
- `topic` (string): One of CRS's own subject terms, e.g. 'U.S. Trade Policy'. Exact match — call crs_topics to see the vocabulary and pick a real one.

### `crs_report` (~216 tokens)

Read one Congressional Research Service report in full by its report number (R43255, IF13006, LSB10123, IN12304). Returns the complete text of the current version, plus its authors, CRS subject topics, publication date, the bills and public laws it cites, how old the text is, and a statement that CRS analysis is persuasive rather than binding. Use it after crs_search, or directly when a report number is already known.

Input parameters:

- `include_text` (boolean): Return the report text. Default true; false gives metadata only.
- `max_chars` (number): Truncate the text at this many characters and say so. Default 120000, which holds all but the longest reports whole. Values below 1000 are raised to 1000 — a 200-character slice of a report is not a…
- `report_id` (string, required): CRS report number, e.g. 'R43255' or 'IF13006'. Case-insensitive.

### `crs_recent` (~140 tokens)

What the Congressional Research Service has published or revised lately — the newest CRS reports and updates, newest first, with their topics and summaries. Answers "what is CRS saying about current legislation right now" and tracks the analysis that follows a bill, a rule or a crisis. Filter by CRS topic or product family.

Input parameters:

- `days` (number): How far back to look, in days. Default 14, max 365.
- `limit` (number): Results to return, 1–50. Default 20.
- `product_class` (string): CRS product family.
- `topic` (string): A CRS subject term — see crs_topics.

### `crs_topics` (~109 tokens)

The Congressional Research Service's own subject taxonomy, with how many reports carry each term — the legal filter values for crs_search and crs_recent. Also lists CRS analysts by output, and the product families. Call this before filtering by topic: CRS writes 'U.S. Trade Policy', and a guessed 'Trade' matches nothing.

Input parameters:

- `facet` (string): Which vocabulary to list. Default topics.
- `limit` (number): Values to return, 1–500. Default 100.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Crs Reports MCP server?

Crs Reports is an MCP server listed in the public MCP registry as io.github.pipeworx-io/crs-reports. Congressional Research Service reports, Congress's own nonpartisan analysis, searchable and… This page covers its npm package (@pipeworx/mcp-crs-reports).

### Is the Crs Reports MCP server safe to use?

Crs Reports 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 Crs Reports MCP server expose?

Crs Reports exposes 4 tools: crs_search, crs_report, crs_recent, crs_topics. Their descriptions and schemas cost roughly 777 tokens of context every time the server is loaded.

### Is the Crs Reports MCP server still maintained?

Crs Reports 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 Crs Reports MCP server under?

Crs Reports 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 Crs Reports MCP server?

VerifyMCP ran 16 checks on Crs Reports, 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-crs-reports
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-crs-reports
- Repository: https://github.com/pipeworx-io/mcp-crs-reports
- Website: https://pipeworx.io/packs/crs-reports
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-crs-reports/pipeworx-mcp-crs-reports.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-crs-reports/pipeworx-mcp-crs-reports/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-crs-reports/pipeworx-mcp-crs-reports.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-crs-reports/pipeworx-mcp-crs-reports