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.

NHANES (design-correct survey analysis)

PYPI · NHANES-MCP

Design-correct NHANES analysis: survey weights, pooled cycles, CIs and NCHS reliability flags.

Available components

−12 this week 60 Trust /100

Last scanned (1 day ago)

Scores higher than 57% of PyPI servers

Category Health and Science

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 Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 0 of 38 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency45
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Context-footprint check failed: tool/resource definitions use about 2009 tokens (~118/item across 17 items; 17 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 Management67
  • Stability observed for 20 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (6% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 17 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
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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 2 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 1 Nov 26 0
    • Provenance: unverified → fail ▼ security
  • 31 Oct 26 +16
    • Provenance: fail → unverified ▼ security
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 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.

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 pypi/nhanes-mcp@0.5.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 38 packages
Packages resolved 38
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 17 exposed · ~2,009 tokens

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
analysis_guidance ~26

Rules for valid NHANES estimation that this server enforces. Read before analyzing.

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultstringyes–

No examples provided.

build_dataset ~237

Build an analysis-ready dataset: DEMO universe (all participants, needed for valid domain estimation) left-joined to the requested tables on SEQN, for one or more cycles. tables: base names without cycle suffix, e.g. ["BMX", "TCHOL", "BPQ"] (DEMO is always included). variables: columns to keep from those tables (default: all). Weight/design variables are always kept. The analysis weight is chosen and rescaled automatically -> column WT_ANALYSIS. Subsample weights carried by a file (fasting WTSAF2YR, phlebotomy WTPH2YR, surplus serum WTSSMC2Y/4Y, ...) are detected. weight: optional weight kind to force, e.g. 'WTSSMC' or 'WTMEC' (without the 2YR/4YR suffix). The server warns if it is less restrictive than the automatic choice.

NameTypeReqDescription
cyclesarrayyes–
include_mortalityboolean––
tablesarrayyes–
variables–––
weight–––

No output schema declared.

No examples provided.

derive_variable ~193

Create a variable from an expression over existing columns, e.g. name='OBESE', expression='BMXBMI >= 30' (booleans become 0/1). missing: 'any' -> result missing if ANY referenced column is missing (default, conservative); 'all' -> missing only if ALL referenced columns are missing (for OR-type definitions); 'none' -> no propagation. Missing-aware functions: coalesce(a, b, ...), fillna(x, value), isna(x), notna(x), where(cond, a, b). Columns used only inside them are exempt from the missing rule. Design columns (WT_ANALYSIS, strata, PSU, SEQN, CYCLE) cannot be overwritten here; use set_weight.

NameTypeReqDescription
dataset_idstringyes–
expressionstringyes–
missingstring––
namestringyes–

No output schema declared.

No examples provided.

describe_dataset ~32

Columns, non-missing counts, weight choice, derived-variable definitions and warnings.

NameTypeReqDescription
dataset_idstringyes–

No output schema declared.

No examples provided.

describe_variable ~67

Codebook entry (label, question text, target population, value codes) plus observed distribution. Flags codes that look like refused/don't-know so they can be set to missing.

NameTypeReqDescription
cyclestringyes–
tablestringyes–
variablestringyes–

No output schema declared.

No examples provided.

export_dataset ~49

Write the analytic dataset (with WT_ANALYSIS, SDMVSTRA_U, SDMVPSU) to CSV plus a provenance sidecar.

NameTypeReqDescription
dataset_idstringyes–
filename–––

No output schema declared.

No examples provided.

flag_from_long_table ~157

Add a per-person 0/1 indicator from a file with several rows per participant (e.g. RXQ_RX prescriptions, DR1IFF foods). Flag = 1 if ANY row's value in ANY of `columns` matches the regex `pattern` (case-insensitive), e.g. table='RXQ_RX', columns=['RXDRSC1','RXDRSC2','RXDRSC3'], pattern='^G40' for ICD-10 epilepsy as the reason for use. People absent from the file are missing.

NameTypeReqDescription
columnsarrayyes–
dataset_idstringyes–
namestringyes–
patternstringyes–
tablestringyes–

No output schema declared.

No examples provided.

list_cycles ~25

List NHANES cycles this server supports, their file-name conventions and weight rules.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_files ~42

List data files for a cycle and component (Demographics, Dietary, Examination, Laboratory, Questionnaire).

NameTypeReqDescription
componentstringyes–
cyclestringyes–

No output schema declared.

No examples provided.

search_variables ~65

Search NHANES variable names/descriptions (regex, case-insensitive) across cycles/components. Defaults to the 2017-2018 cycle and all components.

NameTypeReqDescription
components–––
cycles–––
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

set_missing ~59

Recode sentinel values (e.g. 7, 9, 77, 99 for refused/don't know) to missing.

NameTypeReqDescription
codesarrayyes–
dataset_idstringyes–
variablestringyes–

No output schema declared.

No examples provided.

set_weight ~117

Replace the analysis weight with a custom expression over existing columns, e.g. 'coalesce(WTSSMC4Y * 4/6, WTSSMC2Y * 2/6)'. Use only when build_dataset cannot select the right weight. The change is recorded and reported (weight kind 'CUSTOM' + a warning) in every later result. Negative or missing weights become 0 (out of sample).

NameTypeReqDescription
dataset_idstringyes–
expressionstringyes–
reasonstringyes–

No output schema declared.

No examples provided.

show_results ~384

Present design-based results: headline estimate, subgroup panels, the analysis plan (so the user can check how the question was interpreted), server warnings, NCHS benchmarks and provenance. Returns a text summary plus structured data; when the optional NHANES Results Explorer add-on is installed, MCP Apps hosts also render it as an interactive view. Same estimation arguments as survey_estimate (dataset_id, variable, statistic, domain, age_adjust); by: one panel per grouping variable, e.g. ['RIAGENDR', 'RIDRETH3', 'AGEGRP'] (age-adjustment is skipped for age groupings -- names starting with AGE or RIDAGE, or containing _AGE -- whose panels are age-specific). title / question / outcome_label / population_label / rationale: plain-language analysis plan. group_names: {"AGEGRP": "Age group"}; group_labels: {"AGEGRP": {"1": "20-39", ...}} (common NHANES demographics are labeled automatically). benchmarks: published comparators, e.g. [{"label": "Obesity 2021-23", "published": 40.3, "source_label": "NCHS Data Brief 508", "source_url": "https://...", "by": "RIAGENDR", "level": "1"}] (published in percent for proportions; omit by/level for the overall estimate).

NameTypeReqDescription
age_adjust–––
benchmarks–––
by–––
dataset_idstringyes–
domain–––
group_labels–––
group_names–––
outcome_label–––
population_label–––
question–––
rationale–––
statisticstring––
title–––
variablestringyes–

No output schema declared.

No examples provided.

survey_cox ~129

Survey-weighted Cox proportional hazards model (Breslow ties, Binder linearized variance; same estimator as SUDAAN SURVIVAL / R svycoxph). Typical use with include_mortality=True: time='PERMTH_INT' (or PERMTH_EXM), event='MORTSTAT', domain including 'ELIGSTAT == 1'. Categorical predictors must be dummy-coded first with derive_variable.

NameTypeReqDescription
dataset_idstringyes–
domain–––
eventstringyes–
predictorsarrayyes–
timestringyes–

No output schema declared.

No examples provided.

survey_estimate ~247

Design-based estimate (Taylor linearization) of a mean, proportion (0/1 variable) or total. domain: expression defining the subpopulation, e.g. 'RIDAGEYR >= 20 & RIDEXPRG != 1' (the design is NOT subset; out-of-domain records get zero weight). by: grouping variables, e.g. ['RIAGENDR']. age_adjust: a preset name ('nchs_adults_20plus': 2000 census, 20-39/40-59/60+) or a custom standard {"groups": [[6,11],[12,19],[20,29]], "population": [24.6, 32.5, 38.3]} (or "proportions"), optionally "age_var" (default RIDAGEYR) and "note" naming the source of the standard. Proportions come with Korn-Graubard CIs and NCHS reliability flags.

NameTypeReqDescription
age_adjust–––
by–––
dataset_idstringyes–
domain–––
statisticstring––
variablestringyes–

No output schema declared.

No examples provided.

survey_frequency ~104

Weighted distribution of a categorical variable (Table 1 style): for each level, unweighted n, weighted percent, SE and Korn-Graubard CI, within the domain and optionally by group. labels: optional {code: label} map, e.g. {"1": "Male", "2": "Female"}.

NameTypeReqDescription
by–––
dataset_idstringyes–
domain–––
labels–––
variablestringyes–

No output schema declared.

No examples provided.

survey_regression ~76

Survey-weighted linear ('gaussian') or logistic ('binomial') regression with design-based SEs. Categorical predictors must be dummy-coded first with derive_variable.

NameTypeReqDescription
dataset_idstringyes–
domain–––
familystring––
outcomestringyes–
predictorsarrayyes–

No output schema declared.

No examples provided.

Install

How do I install the NHANES (design-correct survey analysis) MCP server?

NHANES (design-correct survey analysis) runs locally as a PyPI package, launched with uvx nhanes-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · nhanes-mcp

# add to Claude Code
claude mcp add com-blackswancausallabs-nhanes-mcp -- uvx nhanes-mcp
Common questions

What is the NHANES (design-correct survey analysis) MCP server?

NHANES (design-correct survey analysis) is an MCP server listed in the public MCP registry as com.blackswancausallabs/nhanes-mcp. Design-correct NHANES analysis: survey weights, pooled cycles, CIs and NCHS reliability flags. This page covers its PyPI package (nhanes-mcp).

Is the NHANES (design-correct survey analysis) MCP server safe to use?

NHANES (design-correct survey analysis) scores 60 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. 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 NHANES (design-correct survey analysis) MCP server expose?

NHANES (design-correct survey analysis) exposes 17 tools: list_cycles, analysis_guidance, list_files, search_variables, describe_variable, and 12 more. Their descriptions and schemas cost roughly 2,009 tokens of context every time the server is loaded.

Is the NHANES (design-correct survey analysis) MCP server still maintained?

NHANES (design-correct survey analysis) 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 NHANES (design-correct survey analysis) MCP server under?

NHANES (design-correct survey analysis) declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.