Bea Gov
NPM · @PIPEWORX/MCP-BEA-GOV · 2 COMPONENTS
BEA — Bureau of Economic Analysis MCP.
Available components
Last scanned (16 hours ago)
Scores higher than 65% of npm servers
Category Data and Analytics
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-bea-gov). 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 790 tokens (~131/item across 6 items; 6 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 Coverage80
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 40% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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.
- 31 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −16
- Malware scan: pass → unverified ▼ security
- Schema quality: 118 → 131 ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 29 Oct 26 78
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-bea-gov@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-bea-gov |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-bea-gov/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3601416049 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:ae166fbe1e0dff9965c718a6f4ee7893e181c58114cd4fd4cfe70bcd68e8805ef27a76ebfee9ceb1faca0d95b8127acc15bc88942e85c5debaa7a549a |
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 →
dataset_list ~47
List all available BEA datasets (e.g. NIPA, Regional, MNE, FixedAssets, ITA, IIP); returns dataset names and descriptions to identify which dataset to query.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_data ~156
Fetch actual BEA economic data from the specified dataset (e.g. NIPA) using dataset-specific parameters; returns time series values such as GDP, PCE, regional income, and GDP by industry — US ONLY, and only when you already know the dataset-specific parameters (call parameter_list first). GDPbyIndustry additionally requires Industry and Frequency codes this tool cannot guess from a plain-English question. For "what share of GDP comes from <sector>" or "<country>'s agriculture share of GDP" trended over time, prefer worldbank's get_indicator (NV.AGR.TOTL.ZS for agriculture) — it needs only a country code and works for any country, not just the US.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
No output schema declared.
No examples provided.
outdoor_recreation_economy ~424
MARKET SIZE for outdoor recreation activities in US dollars, by activity and state — BEA's Outdoor Recreation Satellite Account (official government statistics, not analyst estimates). Use for "how big is the hunting industry", "fishing economy by state", "which states have the largest outdoor recreation economy", "value of the skiing industry". Activities include hunting, shooting, fishing, boating, hiking/camping, equestrian, skiing/snow, bicycling, RVing, motorcycling/ATV, golf/tennis, guided tours, and the overall total. Returns value added (the activity's contribution to GDP) per state for a year, ranked. IMPORTANT: birdwatching and wildlife WATCHING are not separate lines in this account — hunting and fishing are the only wildlife-related activities measured, so do not use this to size birding specifically. This tool wraps BEA table SAOACTVA so you do not have to know BEA table or line codes; for other BEA data use get_data.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | string | – | Activity to size. Friendly names accepted: "total", "hunting", "shooting", "fishing", "boating", "boating/fishing", "hiking" (climbing/hiking/camping), "equestrian", "bicycling", "skiing", "snow", "r… |
| limit | number | – | Max states to return when no state filter is given (default 51). |
| state | string | – | State name or 2-letter abbreviation (e.g. "Colorado" or "CO") to return just that state. Omit for all 50 states + DC, ranked largest first. |
| year | number | – | Data year (e.g. 2023). Defaults to the most recent published year. |
No output schema declared.
No examples provided.
parameter_list ~50
List all required and optional parameters for a specific BEA dataset (e.g. "NIPA"); returns parameter names, descriptions, data types, and whether they are required.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
No output schema declared.
No examples provided.
parameter_values ~28
Valid values for a parameter.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| parameter | string | yes | – |
No output schema declared.
No examples provided.
parameter_values_filtered ~29
Filter-aware valid values.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | – |
| target_parameter | string | yes | – |
No output schema declared.
No examples provided.
How do I install the Bea Gov MCP server?
Bea Gov runs locally as an npm package, launched with npx -y @pipeworx/mcp-bea-gov. 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-bea-gov
claude mcp add pipeworx-io-bea-gov -- npx -y @pipeworx/mcp-bea-gov
What is the Bea Gov MCP server?
Bea Gov is an MCP server listed in the public MCP registry as io.github.pipeworx-io/bea-gov. BEA, Bureau of Economic Analysis MCP. This page covers its npm package (@pipeworx/mcp-bea-gov).
Is the Bea Gov MCP server safe to use?
Bea Gov scores 80 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 Bea Gov MCP server expose?
Bea Gov exposes 6 tools: dataset_list, parameter_list, parameter_values, parameter_values_filtered, outdoor_recreation_economy, get_data. Their descriptions and schemas cost roughly 734 tokens of context every time the server is loaded.
Is the Bea Gov MCP server still maintained?
Bea Gov 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 Bea Gov MCP server under?
Bea Gov 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 Bea Gov MCP server?
VerifyMCP ran 16 checks on Bea Gov, 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.