Unofficial MCP Server for USWDS
NPM · USWDS-MCP
Unofficial USWDS MCP: official markup, class-aware validator, and page composer for AI tools.
Available components
Last scanned (11 hours ago)
Scores higher than 38% of npm servers
Category Developer Tools
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
- A known CVE affects braces, but no fixed version has been published, so there is nothing to upgrade to. View diagnostics → Partial
- No install/post-install scripts declared.Pass
- 53 of 150 dependencies flagged as unhealthy (1 deprecated). View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- 98% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 6433 tokens (~36/item across 176 items; 12 tools + 164 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage70
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 11% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 13 Oct 26 +29
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 98 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 11 functional
- First check of Schema quality: fail functional
- First check of Schema quality: fair functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- 12 Oct 26 38
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 17 Oct 2026 · Analysed npm/uswds-mcp@0.2.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 2 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-vfj7-8cjw-p6xm | CVE-2026-93687 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | no |
| GHSA-hp3w-g68c-fv3c | CVE-2026-97058 | medium | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:L | no |
Background: What a vulnerability scan can and cannot prove →
Dependencies 150 packages
| Packages resolved | 150 |
|---|---|
| Deprecated | 1 |
| Stale | 53 |
| 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 →
compose_uswds_page Compose USWDS Page ~134
Build a complete, accessible USWDS page from structured sections (hero, content, alert, summary_box, card_group, process_list, step_indicator, accordion, table, form, contact). Output mirrors official markup and is validated automatically.
| Name | Type | Req | Description |
|---|---|---|---|
| agency | string | yes | – |
| asset_path | string | – | – |
| breadcrumbs | array | – | – |
| contact | object | – | – |
| include_identifier | boolean | – | – |
| lang | string | – | – |
| nav_links | array | – | – |
| parent_agency | string | – | – |
| sections | array | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
find_uswds_classes Find USWDS Classes ~67
Look up real USWDS class names, including utilities and responsive variants (e.g. "margin top 2", "tablet grid col 6", "bg primary lighter"). Prevents invented class names.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
No output schema declared.
No examples provided.
generate_uswds_page Generate USWDS Page ~103
Quick starting point: infer sections from free-text requirements and generate a validated USWDS page with [bracketed] placeholders. For real content prefer compose_uswds_page.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_context | string | yes | – |
| asset_path | string | – | URL prefix where USWDS dist assets are served (default /uswds) |
| content_requirements | string | yes | – |
| framework | string | – | – |
| page_type | string | yes | – |
No output schema declared.
No examples provided.
get_component Get USWDS Component ~45
Return component guidance (usage, accessibility, variants) plus the official canonical HTML for the default variant. Call this before writing any component markup.
| Name | Type | Req | Description |
|---|---|---|---|
| slug_or_name | string | yes | – |
No output schema declared.
No examples provided.
get_component_markup Get Canonical USWDS Markup ~135
Return the official, verified USWDS HTML for a component or page template (rendered from the official @uswds/uswds templates). Use this instead of writing usa-* markup from memory. Call with no arguments to list everything available.
| Name | Type | Req | Description |
|---|---|---|---|
| all_variants | boolean | – | – |
| asset_path | string | – | URL prefix where USWDS dist assets are served (default /uswds) |
| component | string | – | Component or page-template name, e.g. accordion, button, footer, sign-in |
| variant | string | – | Variant such as bordered, slim, big, outline, error |
No output schema declared.
No examples provided.
get_pattern Get USWDS Pattern ~26
Return structured pattern guidance and related implementation notes.
| Name | Type | Req | Description |
|---|---|---|---|
| slug_or_name | string | yes | – |
No output schema declared.
No examples provided.
get_template Get USWDS Template ~25
Return structured template guidance and markup references.
| Name | Type | Req | Description |
|---|---|---|---|
| slug_or_name | string | yes | – |
No output schema declared.
No examples provided.
get_uswds_integration_recipe Get USWDS Integration Recipe ~58
Return framework-specific USWDS setup guidance for npm, assets, JavaScript, CSS, and migration.
| Name | Type | Req | Description |
|---|---|---|---|
| framework | string | yes | – |
| migration_scope | string | – | – |
| no_cdn | boolean | – | – |
No output schema declared.
No examples provided.
recommend_uswds_structure Recommend USWDS Structure ~63
Recommend a USWDS-first page or site structure for an agency service.
| Name | Type | Req | Description |
|---|---|---|---|
| agency_type | string | yes | – |
| audience | string | yes | – |
| constraints | string | – | – |
| framework | string | – | – |
| service_goal | string | yes | – |
No output schema declared.
No examples provided.
search_uswds Search USWDS ~41
Search structured USWDS docs and implementation records.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | – |
| query | string | yes | – |
| types | array | – | – |
No output schema declared.
No examples provided.
validate_uswds_markup Validate USWDS Markup ~78
Validate HTML against real USWDS class names, component structure (BEM, required children, ARIA wiring), forms, and accessibility basics. Fragment-aware. Fix every error before finalizing.
| Name | Type | Req | Description |
|---|---|---|---|
| html | string | yes | – |
| mode | string | – | auto detects full pages vs fragments |
| page_context | string | – | – |
No output schema declared.
No examples provided.
validate_uswds_project_setup Validate USWDS Project Setup ~88
Check provided project files for common USWDS framework integration issues such as import paths, assets, scripts, CDN usage, and global CSS risk.
| Name | Type | Req | Description |
|---|---|---|---|
| file_paths | array | – | – |
| files | object | – | – |
| framework | string | – | – |
| migration_scope | string | – | – |
| no_cdn | boolean | – | – |
| package_json | string | – | – |
No output schema declared.
No examples provided.
How do I install the Unofficial MCP Server for USWDS server?
Unofficial MCP Server for USWDS runs locally as an npm package, launched with npx -y uswds-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 · uswds-mcp
claude mcp add bibekpdl-uswds-mcp -- npx -y uswds-mcp
What is the Unofficial MCP Server for USWDS server?
Unofficial MCP Server for USWDS is listed in the public MCP registry as io.github.bibekpdl/uswds-mcp. Unofficial USWDS MCP: official markup, class-aware validator, and page composer for AI tools. This page covers its npm package (uswds-mcp).
Is the Unofficial MCP Server for USWDS server safe to use?
Unofficial MCP Server for USWDS scores 67 out of 100 on VerifyMCP. We recorded 2 known advisories against it as of 17 October 2026. It declares no install or post-install scripts. 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 Unofficial MCP Server for USWDS server expose?
Unofficial MCP Server for USWDS exposes 12 tools: search_uswds, get_component, get_pattern, get_template, recommend_uswds_structure, and 7 more. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.
Is the Unofficial MCP Server for USWDS server still maintained?
Unofficial MCP Server for USWDS is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Unofficial MCP Server for USWDS server under?
Unofficial MCP Server for USWDS declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.