Us Code
NPM · @PIPEWORX/MCP-US-CODE · 2 COMPONENTS
US Code — the text of federal statutes, by citation.
Available components
Last scanned (5 hours ago)
Scores higher than 81% 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-us-code). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability72
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 428 tokens (~142/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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +3
- Stability: unverified → 0.17 ▲ functional
- 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-us-code@0.2.0
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-us-code |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-us-code/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3560840253 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:339e1517dca9e691672b66dd44bf48f399e083e010fa90016cdfcd312e400d645ab8c54e352db9d84ededd67280f2ddb22dc059a8de2e01a676d9265b |
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 →
usc_search ~125
Search the United States Code by subject to find which statutes are relevant — "wire fraud", "endangered species take". Returns matching section headings and their titles; call usc_section for the text. Needs a data.gov API key, which Pipeworx fronts; pass _apiKey to use your own. For a citation you already have, usc_section is keyless and more direct.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum results (1-50, default 10). |
| query | string | yes | Subject matter, e.g. "wire fraud" or "clean water discharge permit". |
No output schema declared.
No examples provided.
usc_section ~184
Get the FULL TEXT of a section of the United States Code — federal statutes — by citation. "18 U.S.C. 1343" is title 18, section 1343. Returns the statutory text, its title and chapter, and the edition it came from. Keyless. Use for "what does the wire fraud statute say", "what is the text of 42 USC 1983", or to check what a statute a case relies on actually provides.
| Name | Type | Req | Description |
|---|---|---|---|
| section | string | yes | Section number as cited, e.g. "1343" or "1983". Subsections like "1343(a)" are not separate documents — pass the section. |
| title | string | yes | US Code title number, 1-54. E.g. "18" for crimes, "26" for tax, "42" for public health and welfare. |
No output schema declared.
No examples provided.
usc_titles ~67
List the 54 titles of the United States Code with their subject names — title 18 is Crimes and Criminal Procedure, title 26 is the Internal Revenue Code, and so on. Keyless. Use when you know the subject area but not which title governs it, before calling usc_section.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Us Code MCP server?
Us Code runs locally as an npm package, launched with npx -y @pipeworx/mcp-us-code. 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-us-code
claude mcp add pipeworx-io-us-code -- npx -y @pipeworx/mcp-us-code
What is the Us Code MCP server?
Us Code is an MCP server listed in the public MCP registry as io.github.pipeworx-io/us-code. US Code, the text of federal statutes, by citation. This page covers its npm package (@pipeworx/mcp-us-code).
Is the Us Code MCP server safe to use?
Us Code scores 84 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 Us Code MCP server expose?
Us Code exposes 3 tools: usc_section, usc_titles, usc_search. Their descriptions and schemas cost roughly 376 tokens of context every time the server is loaded.
Is the Us Code MCP server still maintained?
Us Code 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 Us Code MCP server under?
Us Code declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.