Committee Releases
NPM · @PIPEWORX/MCP-COMMITTEE-RELEASES · 2 COMPONENTS
Committee Releases — documents congressional committees publish on their OWN websites: press…
Available components
Last scanned (2 hours ago)
Scores higher than 76% of npm servers
Category Documents and Files
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-committee-releases). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 555 tokens (~185/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
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.
- 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 +27
- Malware scan: unverified → pass ▲ security
- Known CVEs: unverified → pass ▲ security
- Dependency health: unverified → pass ▲ functional
- 31 Oct 26 −26
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Security disclosure: unverified → fail ▼ functional
- Dependency health: pass → unverified ▼ functional
- 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 80
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-committee-releases@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-committee-releases |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-committee-releases/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612192387 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:796fc7aa4eb33861f31136b2b77b605fbe63b954da2a875023af4bd00375d0b96a34e1e3daf7aa7cabca93b1f585d579725b8a5a0c58c58380685e647 |
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 →
get_committee_document ~108
Read a committee document page: its headline, publication date, the text the committee published, and the attached documents (usually PDFs — letters, transcripts, reports) with URLs and sizes. Pass a url from search_committee_documents. Note that PDF text is NOT extracted — attachments are returned as links, so quote the page text and cite the attachment URL rather than claiming to have read the PDF.
| Name | Type | Req | Description |
|---|---|---|---|
| url | string | yes | Full committee document URL, as returned by search_committee_documents |
No output schema declared.
No examples provided.
list_committee_document_types ~50
List the congressional committees covered here, which document types each one publishes on its website, and what this source does and does not cover. Call when unsure which committee or doc_type answers a question.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_committee_documents ~342
Find documents published by a congressional committee on its own website — press releases, oversight letters, staff reports, released interview transcripts, investigation files and hearing material. Covers the House Oversight Committee and the Senate Homeland Security and Governmental Affairs Committee (HSGAC). Use for "what has House Oversight said about X", "the Oversight Committee letter to Y", "HSGAC investigation into Z", "transcripts the committee released". This material appears within hours, unlike the official printed record which lags by months (use search_congressional_documents for that). IMPORTANT: matches the document headline/slug, not the text inside documents or their PDF attachments — an empty result means no headline matched rather than that the subject is absent.
| Name | Type | Req | Description |
|---|---|---|---|
| committee | string | – | Which committee: "house-oversight", "hsgac", or "all" (default). Also accepts loose names like "oversight" or "homeland security". |
| doc_type | string | – | What to search: "releases", "letters", "reports", "hearings", "markups", "documents" (attached files), "investigations", or "all". Omit for each committee's sensible default. Not every committee publ… |
| limit | number | – | Results to return (default 20, max 100) |
| query | string | – | Keywords matched against document headlines, all of which must appear, e.g. "subpoena FBI". Omit to list the most recent documents. |
| since | string | – | Only documents updated on or after this date, YYYY-MM-DD |
No output schema declared.
No examples provided.
How do I install the Committee Releases MCP server?
Committee Releases runs locally as an npm package, launched with npx -y @pipeworx/mcp-committee-releases. 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-committee-releases
claude mcp add pipeworx-io-committee-releases -- npx -y @pipeworx/mcp-committee-releases
What is the Committee Releases MCP server?
Committee Releases is an MCP server listed in the public MCP registry as io.github.pipeworx-io/committee-releases. Committee Releases, documents congressional committees publish on their OWN websites: press… This page covers its npm package (@pipeworx/mcp-committee-releases).
Is the Committee Releases MCP server safe to use?
Committee Releases scores 83 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 Committee Releases MCP server expose?
Committee Releases exposes 3 tools: search_committee_documents, get_committee_document, list_committee_document_types. Their descriptions and schemas cost roughly 500 tokens of context every time the server is loaded.
Is the Committee Releases MCP server still maintained?
Committee Releases 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 Committee Releases MCP server under?
Committee Releases declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.