U.S. Government Open Data
NPM · US-GOV-OPEN-DATA-MCP
Open data from 40+ U.S. government APIs: economy, spending, Congress, health, energy, disasters
Available components
Last scanned (1 hour ago)
Scores higher than 31% 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 Security98
- 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
- 64 of 196 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to lzinga/us-gov-open-data-mcp). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 27 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: the captured schema was too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge it on a partial copy.Unverified
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage0
- Tool coverage not yet verified: the captured tool definitions were too large for us to store in full, or the server stopped listing its tools part-way, so we will not judge them on a partial copy.Unverified
Tool Safety0
- Tool safety not yet verified: the captured tool definitions were too large for us to store in full (the trim removes the very descriptions this category reads), or the server stopped listing its tools part-way.Unverified
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 3 categories
Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
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 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 3 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
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/us-gov-open-data-mcp@2026.10.8
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 | lzinga/us-gov-open-data-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/lzinga/us-gov-open-data-mcp/.github/workflows/publish.yml@refs/tags/v2026.10.8 |
| Rekor log index | 3149491748 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:9b7777d9eff4b25282726d4d8f70e332afc1efd9e0a22c723a8456c85834e259f5a65e53d9f3ad67a9e82628bebd30b8054595e6217aa760f8e484a24 |
Background: How many MCP packages publish verified provenance →
Dependencies 196 packages
| Packages resolved | 196 |
|---|---|
| Deprecated | 1 |
| Stale | 63 |
| 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 →
clinical_trials_field_values ~154
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fields | string | yes | – |
| types | string | – | – |
No output schema declared.
No examples provided.
clinical_trials_metadata ~90
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| include_historic_only | boolean | – | – |
| include_indexed_only | boolean | – | – |
No output schema declared.
No examples provided.
clinical_trials_results ~88
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| nct_id | string | yes | – |
No output schema declared.
No examples provided.
clinical_trials_search ~688
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| agg_filters | string | – | – |
| condition | string | – | – |
| filter_advanced | string | – | – |
| intervention | string | – | – |
| lead_sponsor | string | – | – |
| location | string | – | – |
| outcomes | string | – | – |
| page_size | integer | – | – |
| page_token | string | – | – |
| phase | string | – | – |
| query | string | – | – |
| sort | string | – | – |
| sponsor | string | – | – |
| status | – | – | – |
| study_id | string | – | – |
| study_type | string | – | – |
| titles | string | – | – |
No output schema declared.
No examples provided.
clinical_trials_size_stats ~43
No description provided.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
clinical_trials_stats ~129
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| condition | string | yes | – |
| search_as_drug | boolean | – | – |
No output schema declared.
No examples provided.
cms_hospitals ~93
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | – |
| dataset | string | – | – |
| limit | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
cms_nursing_homes ~72
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | – | – |
| limit | number | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
cms_query ~138
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset_id | string | yes | – |
| filter_field | string | – | – |
| filter_value | string | – | – |
| limit | number | – | – |
| offset | number | – | – |
No output schema declared.
No examples provided.
cms_search ~72
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| keyword | string | yes | – |
No output schema declared.
No examples provided.
code_mode ~423
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | – |
| tool | string | yes | – |
| tool_args | object | – | – |
No output schema declared.
No examples provided.
congress_amendment_amendments ~76
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| amendment_number | string|number | yes | – |
| amendment_type | string | yes | – |
| congress | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_amendment_cosponsors ~72
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| amendment_number | string|number | yes | – |
| amendment_type | string | yes | – |
| congress | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_amendment_details ~73
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| amendment_number | string|number | yes | – |
| amendment_type | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_amendment_text ~72
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| amendment_number | string|number | yes | – |
| amendment_type | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_amendments ~142
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| amendment_type | string | – | – |
| congress | integer | – | – |
| fromDateTime | string | – | – |
| limit | integer | – | – |
| toDateTime | string | – | – |
No output schema declared.
No examples provided.
congress_bill_actions ~114
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_bill_amendments ~89
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_bill_committees ~72
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_bill_cosponsors ~109
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
| limit | integer | – | – |
| sort | string | – | – |
No output schema declared.
No examples provided.
congress_bill_details ~87
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_bill_full_profile ~204
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_bill_related ~84
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_bill_subjects ~84
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_bill_summaries ~81
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_bill_text ~77
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_bill_titles ~96
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_bill_votes ~176
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| bill_number | integer | yes | – |
| bill_type | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_bound_congressional_record ~86
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | – |
| limit | integer | – | – |
| month | integer | – | – |
| year | integer | – | – |
No output schema declared.
No examples provided.
congress_committee_bills ~100
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| committee_code | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_committee_details ~85
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| committee_code | string | yes | – |
No output schema declared.
No examples provided.
congress_committee_details_by_congress ~86
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| committee_code | string | yes | – |
| congress | integer | yes | – |
No output schema declared.
No examples provided.
congress_committee_full_profile ~176
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| committee_code | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_committee_house_communications ~56
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| committee_code | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_committee_meeting_details ~71
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| congress | integer | yes | – |
| event_id | string | yes | – |
No output schema declared.
No examples provided.
congress_committee_meetings ~123
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | – | – |
| congress | integer | – | – |
| fromDateTime | string | – | – |
| limit | integer | – | – |
| toDateTime | string | – | – |
No output schema declared.
No examples provided.
congress_committee_nominations_for_committee ~89
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| committee_code | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_committee_print_details ~61
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| congress | integer | yes | – |
| jacket_number | integer | yes | – |
No output schema declared.
No examples provided.
congress_committee_print_text ~53
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| congress | integer | yes | – |
| jacket_number | integer | yes | – |
No output schema declared.
No examples provided.
congress_committee_prints ~122
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | – | – |
| congress | integer | – | – |
| fromDateTime | string | – | – |
| limit | integer | – | – |
| toDateTime | string | – | – |
No output schema declared.
No examples provided.
congress_committee_report_details ~93
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| congress | integer | yes | – |
| report_number | integer | yes | – |
| report_type | string | yes | – |
No output schema declared.
No examples provided.
congress_committee_report_text ~80
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| congress | integer | yes | – |
| report_number | integer | yes | – |
| report_type | string | yes | – |
No output schema declared.
No examples provided.
congress_committee_reports ~177
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| conference | boolean | – | – |
| congress | integer | – | – |
| fromDateTime | string | – | – |
| limit | integer | – | – |
| report_type | string | – | – |
| toDateTime | string | – | – |
No output schema declared.
No examples provided.
congress_committee_reports_for_committee ~135
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | yes | – |
| committee_code | string | yes | – |
| fromDateTime | string | – | – |
| limit | integer | – | – |
| toDateTime | string | – | – |
No output schema declared.
No examples provided.
congress_committee_senate_communications ~58
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| committee_code | string | yes | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
congress_committees ~133
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| chamber | string | – | – |
| congress | integer | – | – |
| fromDateTime | string | – | – |
| limit | integer | – | – |
| toDateTime | string | – | – |
No output schema declared.
No examples provided.
congress_congressional_record ~90
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| day | integer | – | – |
| limit | integer | – | – |
| month | integer | – | – |
| year | integer | – | – |
No output schema declared.
No examples provided.
congress_crs_report_details ~75
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| report_number | string | yes | – |
No output schema declared.
No examples provided.
congress_crs_reports ~105
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| fromDateTime | string | – | – |
| limit | integer | – | – |
| toDateTime | string | – | – |
No output schema declared.
No examples provided.
congress_daily_congressional_record ~91
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| issue_number | integer | – | – |
| limit | integer | – | – |
| volume_number | integer | – | – |
No output schema declared.
No examples provided.
How do I install the U.S. Government Open Data MCP server?
U.S. Government Open Data runs locally as an npm package, launched with npx -y us-gov-open-data-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · us-gov-open-data-mcp
claude mcp add lzinga-us-gov-open-data-mcp -- npx -y us-gov-open-data-mcp
What is the U.S. Government Open Data MCP server?
U.S. Government Open Data is an MCP server listed in the public MCP registry as io.github.lzinga/us-gov-open-data-mcp. Open data from 40+ U.S. government APIs: economy, spending, Congress, health, energy, disasters. This page covers its npm package (us-gov-open-data-mcp).
Is the U.S. Government Open Data MCP server safe to use?
U.S. Government Open Data scores 63 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.
Is the U.S. Government Open Data MCP server still maintained?
U.S. Government Open Data 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 U.S. Government Open Data MCP server under?
U.S. Government Open Data declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.