Budget Resolutions
NPM · @PIPEWORX/MCP-BUDGET-RESOLUTIONS · 2 COMPONENTS
budget-resolutions: adopted congressional budget-resolution targets (concurrent resolutions on the…
Available components
Last scanned (3 hours ago)
Scores higher than 72% of npm servers
Category Finance and Payments
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-budget-resolutions). 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 Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 834 tokens (~278/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 +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 +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 +15
- Malware scan: unverified → pass ▲ security
- 29 Oct 26 64
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-budget-resolutions@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-budget-resolutions |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-budget-resolutions/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606604433 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2e12bfc009223091724764c3d438a64c289625f559d5704ac337ded1ac22d2d98f40159b20737d1e168ad7b114db6eeb25a02f2e3c00e3dac6641140b |
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 →
budget_resolution_find ~166
Which congressional budget resolutions (concurrent resolutions on the budget, H.Con.Res. / S.Con.Res.) exist for a federal fiscal year, and how far each got: adopted by both chambers, passed one chamber, or only introduced. Use for "was a budget resolution adopted for FY2024?", "what budget resolutions were there for FY2027?". A year with no resolution returns found:false with a named reason, not an empty list. Covers fiscal years 1994 onward (bill text starts with the 103rd Congress). Source: U.S. Congress, as published by the U.S. Government Publishing Office.
| Name | Type | Req | Description |
|---|---|---|---|
| fiscal_year | number | yes | Federal fiscal year (Oct-Sep), e.g. 2025 = Oct 2024 through Sep 2025. |
No output schema declared.
No examples provided.
budget_resolution_targets ~364
The levels a congressional budget resolution sets for a fiscal year and the years after it: federal revenues, new budget authority, outlays, deficit and debt, plus new budget authority and outlays for each budget function (National Defense, Health, Medicare, Social Security, Net Interest, ...). Returns the adopted resolution; if none was adopted, the most advanced proposal that passed a chamber (clearly marked adopted:false), or found:false with a named reason. Includes a sum check: the function figures added up beside the resolution's stated totals. Use for "FY2025 budget resolution defense outlays", "what did the House budget plan for FY2027 assume for revenues?". Dollars are nominal US dollars. Optional filters narrow function and year. Source: U.S. Congress, as published by the U.S. Government Publishing Office.
| Name | Type | Req | Description |
|---|---|---|---|
| adopted_only | boolean | – | true: return only a resolution adopted by both chambers; otherwise a one-chamber-passed plan may be returned if none was adopted (marked adopted:false). |
| fiscal_year | number | yes | The budget year the resolution is for, e.g. 2025. Its levels also cover the later years in the resolution (typically nine more). |
| function | string | – | Budget function, case-insensitive substring ("Defense", "Medicare", "Net Interest") or the three-digit code ("050"). Omit for all functions. |
| package_id | string | – | Read a specific version, e.g. "BILLS-119hconres113pcs" (ids come from budget_resolution_find). |
| target_year | number | – | Limit the output to one fiscal year inside the resolution (e.g. 2027 within a resolution that runs 2027-2036). Omit for every year. |
No output schema declared.
No examples provided.
budget_vs_actual ~250
A fiscal year's congressional budget-resolution targets next to what the U.S. Treasury actually reported: revenues, total outlays, the implied deficit, and outlays by budget function, each with budget, actual and the difference. Totals are compared on the on-budget basis the resolutions use (Social Security's off-budget part excluded), with unified totals beside them. Actuals come from the Monthly Treasury Statement (net outlays, nominal dollars) and say whether the year is complete; the budget side says whether the resolution was adopted. A year with no resolution still returns the actuals plus a named reason for the missing budget side. Use for "how did FY2025 outlays compare to the budget resolution?", "defense spending vs budget plan". Sources: U.S. Congress (as published by the U.S. Government Publishing Office) and U.S. Treasury.
| Name | Type | Req | Description |
|---|---|---|---|
| adopted_only | boolean | – | true: compare only against a resolution adopted by both chambers. |
| fiscal_year | number | yes | Federal fiscal year (Oct-Sep) to compare, e.g. 2025. |
| function | string | – | Limit to one budget function (substring or three-digit code). Totals are always included. |
No output schema declared.
No examples provided.
How do I install the Budget Resolutions MCP server?
Budget Resolutions runs locally as an npm package, launched with npx -y @pipeworx/mcp-budget-resolutions. 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-budget-resolutions
claude mcp add pipeworx-io-budget-resolutions -- npx -y @pipeworx/mcp-budget-resolutions
What is the Budget Resolutions MCP server?
Budget Resolutions is an MCP server listed in the public MCP registry as io.github.pipeworx-io/budget-resolutions. budget-resolutions: adopted congressional budget-resolution targets (concurrent resolutions on the… This page covers its npm package (@pipeworx/mcp-budget-resolutions).
Is the Budget Resolutions MCP server safe to use?
Budget Resolutions 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 Budget Resolutions MCP server expose?
Budget Resolutions exposes 3 tools: budget_resolution_find, budget_resolution_targets, budget_vs_actual. Their descriptions and schemas cost roughly 780 tokens of context every time the server is loaded.
Is the Budget Resolutions MCP server still maintained?
Budget Resolutions 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 Budget Resolutions MCP server under?
Budget Resolutions declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.