Congressional Documents
NPM · @PIPEWORX/MCP-CONGRESSIONAL-DOCUMENTS · 2 COMPONENTS
Congressional Documents — full-text search and retrieval over the official record of Congress…
Available components
Last scanned (8 hours ago)
Scores higher than 72% 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-congressional-documents). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 701 tokens (~233/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
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 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 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 +15
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- 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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-congressional-documents@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-congressional-documents |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-congressional-documents/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3612229299 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7dd6cff57706b64c6a40bbb7dc96895a6e2e856199deb2b380138d75ccbad6e31ddfcbcafba94658af26e7b66899df1fe344363f39175b4e5680ba941 |
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_congressional_document_text ~260
Read the actual text of a congressional document — the full transcript, report or Congressional Record entry — so an answer can quote the source instead of paraphrasing from memory. Pass the package_id (and granule_id where the search returned one) from search_congressional_documents. Returns the document text, its official citation, the page range where the source prints one, and the govinfo.gov URL. Hearing transcripts run to hundreds of pages, so text is truncated by default — raise max_chars or use the offset to page through it.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | data.gov API key (free at api.data.gov/signup) |
| granule_id | string | – | Optional granule id for one item within a package, e.g. "CREC-2025-09-10-pt1-PgS6557-4" |
| max_chars | number | – | Characters of text to return (default 20000, max 200000) |
| offset | number | – | Character offset to start from, for paging long transcripts |
| package_id | string | yes | GovInfo package id, e.g. "CHRG-116shrg42133" or "CREC-2025-09-10" |
No output schema declared.
No examples provided.
list_congressional_document_types ~66
List the kinds of congressional documents that can be searched (hearings, committee reports, committee prints, House/Senate documents, Congressional Record), what each contains, and what this source does and does not cover. Call this when unsure which doc_type answers a question.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_congressional_documents ~319
Search the full text of official U.S. congressional documents — hearing transcripts, committee reports, committee prints, House/Senate documents, and the Congressional Record. Use for "what was said in the congressional hearing about X", "the committee report on Y", "congressional testimony on Z", "what did Congress publish about ...". Returns matching documents with their official citation, date, congress number and a govinfo.gov link; pass the returned ids to get_congressional_document_text to read the actual wording. Searches PUBLISHED documents only — a hearing transcript appears months after the hearing. Note that a person named in a document is not thereby accused of anything.
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | data.gov API key (free at api.data.gov/signup) |
| congress | number | – | Congress number, e.g. 118 for 2023-2024 |
| date_from | string | – | Earliest publication date, YYYY-MM-DD |
| date_to | string | – | Latest publication date, YYYY-MM-DD |
| doc_type | string | – | Which record to search: "hearings" (transcripts), "reports" (committee reports), "prints", "documents" (House/Senate documents), "record" (Congressional Record), or "all" (default). |
| limit | number | – | Results to return (default 10, max 50) |
| query | string | yes | Free-text search over document full text, e.g. "opioid settlement" or "FTX collapse" |
No output schema declared.
No examples provided.
How do I install the Congressional Documents MCP server?
Congressional Documents runs locally as an npm package, launched with npx -y @pipeworx/mcp-congressional-documents. 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-congressional-documents
claude mcp add pipeworx-io-congressional-documents -- npx -y @pipeworx/mcp-congressional-documents
What is the Congressional Documents MCP server?
Congressional Documents is an MCP server listed in the public MCP registry as io.github.pipeworx-io/congressional-documents. Congressional Documents, full-text search and retrieval over the official record of Congress… This page covers its npm package (@pipeworx/mcp-congressional-documents).
Is the Congressional Documents MCP server safe to use?
Congressional Documents scores 82 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 Congressional Documents MCP server expose?
Congressional Documents exposes 3 tools: search_congressional_documents, get_congressional_document_text, list_congressional_document_types. Their descriptions and schemas cost roughly 645 tokens of context every time the server is loaded.
Is the Congressional Documents MCP server still maintained?
Congressional Documents 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 Congressional Documents MCP server under?
Congressional Documents 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 Congressional Documents MCP server?
VerifyMCP ran 16 checks on Congressional Documents, 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.