Crs Reports
NPM · @PIPEWORX/MCP-CRS-REPORTS · 2 COMPONENTS
Congressional Research Service reports — Congress's own nonpartisan analysis, searchable and…
Available components
Last scanned (12 hours ago)
Scores higher than 75% of npm servers
Category Education and Research
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-crs-reports). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 6 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. 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 +6
- Source repository: unverified → pass ▲ security
- 5 Nov 26 −5
- Provenance: pass → unverified ▼ security
- 3 Nov 26 +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.
- 1 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 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 6 Nov 2026 · Analysed npm/@pipeworx/mcp-crs-reports@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-crs-reports |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-crs-reports/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612304545 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:76edd79d34fbee6c0210cb069ce2ac7f8a508d00c1b90ab163fdc691156a99c6946194b38331db9a7cf5f24fc0c3f1741e04a31cd3f84cd802087d348 |
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 →
crs_recent ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
crs_report ~216
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | CRS report number, e.g. 'R43255' or 'IF13006'. Case-insensitive. |
No output schema declared.
No examples provided.
crs_search ~312
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
crs_topics ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| facet | string | – | Which vocabulary to list. Default topics. |
| limit | number | – | Values to return, 1–500. Default 100. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-crs-reports
claude mcp add pipeworx-io-crs-reports -- npx -y @pipeworx/mcp-crs-reports
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.