Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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

+3 this week 62 Trust /100

Last scanned (19 hours ago)

Scores higher than 31% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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 26 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 Management67
  • Stability observed for 20 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 →

Changelog

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 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.

  • 22 Oct 26 +3
    • Stability: unverified → 0.23 ▲ functional
Diagnostics

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 4 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 →

MCP tools · 356 exposed · ~54,441 tokens partial

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 →

Tool Tokens
bea_dataset_info ~342

No description provided.

NameTypeReqDescription
actionstringyes–
dataset_namestring––
filtersstring––
parameter_namestring––
target_parameterstring––

No output schema declared.

No examples provided.

bea_fixed_assets ~160

No description provided.

NameTypeReqDescription
table_namestring––
yearstring––

No output schema declared.

No examples provided.

bea_gdp_by_industry ~246

No description provided.

NameTypeReqDescription
frequencystring––
industrystring––
table_idstring––
yearstring––

No output schema declared.

No examples provided.

bea_gdp_by_state ~238

No description provided.

NameTypeReqDescription
geo_fipsstring––
line_codestring––
table_namestring––
yearstring––

No output schema declared.

No examples provided.

bea_gdp_national ~211

No description provided.

NameTypeReqDescription
frequencystring––
table_namestring––
yearstring––

No output schema declared.

No examples provided.

bea_input_output ~103

No description provided.

NameTypeReqDescription
table_idstringyes–
yearstringyes–

No output schema declared.

No examples provided.

bea_international_investment ~260

No description provided.

NameTypeReqDescription
componentstring––
frequencystring––
type_of_investmentstring––
yearstring––

No output schema declared.

No examples provided.

bea_international_transactions ~267

No description provided.

NameTypeReqDescription
area_or_countrystring––
frequencystring––
indicatorstring––
yearstring––

No output schema declared.

No examples provided.

bea_intl_services_trade ~316

No description provided.

NameTypeReqDescription
affiliationstring––
area_or_countrystring––
trade_directionstring––
type_of_servicestring––
yearstring––

No output schema declared.

No examples provided.

bea_multinational_enterprises ~380

No description provided.

NameTypeReqDescription
classificationstringyes–
countrystring––
direction_of_investmentstringyes–
industrystring––
non_bank_affiliates_onlystring––
ownership_levelstring––
series_idstring––
statestring––
yearstringyes–

No output schema declared.

No examples provided.

bea_nipa_underlying_detail ~165

No description provided.

NameTypeReqDescription
frequencystring––
table_namestring––
yearstring––

No output schema declared.

No examples provided.

bea_personal_income ~297

No description provided.

NameTypeReqDescription
geo_fipsstring––
line_codestring––
table_namestring––
yearstring––

No output schema declared.

No examples provided.

bea_underlying_gdp_by_industry ~140

No description provided.

NameTypeReqDescription
industrystring––
table_idstring––
yearstring––

No output schema declared.

No examples provided.

bls_cpi_breakdown ~74

No description provided.

NameTypeReqDescription
end_yearinteger––
start_yearinteger––

No output schema declared.

No examples provided.

bls_employment_by_industry ~63

No description provided.

NameTypeReqDescription
end_yearinteger––
start_yearinteger––

No output schema declared.

No examples provided.

bls_search_series ~137

No description provided.

NameTypeReqDescription
statestring––
topicstringyes–

No output schema declared.

No examples provided.

bls_series_data ~458

No description provided.

NameTypeReqDescription
end_yearinteger––
laus_areasstring––
laus_measurestring––
oews_measurestring––
oews_occupationsstring––
oews_statestring––
series_idsstring––
start_yearinteger––

No output schema declared.

No examples provided.

bts_border_crossings ~201

No description provided.

NameTypeReqDescription
borderstring––
limitinteger––
measurestring––
port_namestring––
statestring––

No output schema declared.

No examples provided.

bts_transport_stats ~159

No description provided.

NameTypeReqDescription
end_datestring––
limitinteger––
start_datestring––

No output schema declared.

No examples provided.

calc_contract_rates ~92

No description provided.

NameTypeReqDescription
contract_numberstringyes–
page_sizenumber––

No output schema declared.

No examples provided.

calc_search_rates ~493

No description provided.

NameTypeReqDescription
business_sizestring––
categorystring––
education_levelstring––
experience_rangestring––
keywordstring––
min_years_experiencestring––
orderingstring––
pagenumber––
page_sizenumber––
price_rangestring––
searchstring––
security_clearancestring––
sinstring––
sortstring––
subcategorystring––
worksitestring––

No output schema declared.

No examples provided.

calc_suggest ~100

No description provided.

NameTypeReqDescription
fieldstringyes–
prefixstringyes–

No output schema declared.

No examples provided.

cdc_birth_indicators ~171

No description provided.

NameTypeReqDescription
limitinteger––
race_ethnicitystring––
topicstring––

No output schema declared.

No examples provided.

cdc_causes_of_death ~158

No description provided.

NameTypeReqDescription
limitinteger––
statestring––
yearinteger––

No output schema declared.

No examples provided.

cdc_covid ~98

No description provided.

NameTypeReqDescription
limitinteger––
statestring––

No output schema declared.

No examples provided.

cdc_death_rates_historical ~135

No description provided.

NameTypeReqDescription
causestring––
end_yearinteger––
limitinteger––
start_yearinteger––

No output schema declared.

No examples provided.

cdc_disability ~148

No description provided.

NameTypeReqDescription
disability_typestring––
limitinteger––
statestring––

No output schema declared.

No examples provided.

cdc_drug_overdose ~328

No description provided.

NameTypeReqDescription
drugstring––
limitinteger––
sexstring––
sourcestring––
statestring––
yearinteger––

No output schema declared.

No examples provided.

cdc_life_expectancy ~191

No description provided.

NameTypeReqDescription
limitinteger––
racestring––
sexstring––
statestring––
yearinteger––

No output schema declared.

No examples provided.

cdc_mortality_rates ~180

No description provided.

NameTypeReqDescription
causestring––
limitinteger––
quarterstring––
rate_typestring––

No output schema declared.

No examples provided.

cdc_nutrition_obesity ~130

No description provided.

NameTypeReqDescription
limitinteger––
statestring––
topicstring––

No output schema declared.

No examples provided.

cdc_places_city ~143

No description provided.

NameTypeReqDescription
citystring––
limitinteger––
statestring––

No output schema declared.

No examples provided.

cdc_places_health ~291

No description provided.

NameTypeReqDescription
limitinteger––
measurestring––
statestring––

No output schema declared.

No examples provided.

cdc_query ~267

No description provided.

NameTypeReqDescription
dataset_idstringyes–
groupstring––
limitinteger––
orderstring––
selectstring––
wherestring––

No output schema declared.

No examples provided.

cdc_weekly_deaths ~129

No description provided.

NameTypeReqDescription
limitinteger––
statestring––
yearinteger––

No output schema declared.

No examples provided.

census_place_profile ~232

No description provided.

NameTypeReqDescription
countystring––
placestring––
statestring––
yearinteger––
zctastring––

No output schema declared.

No examples provided.

census_population ~95

No description provided.

NameTypeReqDescription
statestring––
yearinteger––

No output schema declared.

No examples provided.

census_query ~265

No description provided.

NameTypeReqDescription
datasetstringyes–
for_geostringyes–
in_geostring––
variablesstringyes–

No output schema declared.

No examples provided.

census_search_variables ~104

No description provided.

NameTypeReqDescription
datasetstringyes–
keywordstringyes–
max_resultsinteger––

No output schema declared.

No examples provided.

cfpb_complaint_aggregations ~192

No description provided.

NameTypeReqDescription
companystring––
date_received_maxstring––
date_received_minstring––
fieldstringyes–
issuestring––
productstring––
statestring––

No output schema declared.

No examples provided.

cfpb_complaint_detail ~60

No description provided.

NameTypeReqDescription
complaint_idintegeryes–

No output schema declared.

No examples provided.

cfpb_complaint_trends ~291

No description provided.

NameTypeReqDescription
companystring––
date_received_maxstring––
date_received_minstring––
focusstring––
issuestring––
lensstring––
productstring––
statestring––
sub_lensstring––
sub_lens_depthinteger––
trend_intervalstringyes–

No output schema declared.

No examples provided.

cfpb_search_complaints ~369

No description provided.

NameTypeReqDescription
companystring––
date_received_maxstring––
date_received_minstring––
has_narrativeboolean––
issuestring––
productstring––
search_termstring––
sizeinteger––
sortstring––
statestring––
submitted_viastring––
tagsstring––
timelystring––
zip_codestring––

No output schema declared.

No examples provided.

cfpb_state_complaints ~143

No description provided.

NameTypeReqDescription
companystring––
date_received_maxstring––
date_received_minstring––
issuestring––
productstring––
tagsstring––

No output schema declared.

No examples provided.

cfpb_suggest_company ~73

No description provided.

NameTypeReqDescription
sizeinteger––
textstringyes–

No output schema declared.

No examples provided.

clear_cache ~176

No description provided.

NameTypeReqDescription
sourcestring––

No output schema declared.

No examples provided.

clinical_trials_by_location ~184

No description provided.

NameTypeReqDescription
conditionstring––
distancestring––
interventionstring––
latitudenumberyes–
longitudenumberyes–
page_sizeinteger––
statusstring––

No output schema declared.

No examples provided.

clinical_trials_detail ~107

No description provided.

NameTypeReqDescription
fieldsstring––
nct_idstringyes–

No output schema declared.

No examples provided.

clinical_trials_enums ~88

No description provided.

NameTypeReqDescription
enum_typestring––

No output schema declared.

No examples provided.

clinical_trials_field_sizes ~71

No description provided.

NameTypeReqDescription
fieldsstring––

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add lzinga-us-gov-open-data-mcp -- npx -y us-gov-open-data-mcp
Common questions

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 62 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.