@ansvar/us-regulations-mcp 1.0.0 → 1.2.2

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
Files changed (57) hide show
  1. package/README.md +422 -79
  2. package/data/regulations.db +0 -0
  3. package/data/seed/colorado-cpa.json +97 -0
  4. package/data/seed/ffiec.json +103 -0
  5. package/data/seed/mappings/ccpa-nist-csf.json +11 -1
  6. package/data/seed/mappings/hipaa-nist-800-53.json +10 -1
  7. package/data/seed/nydfs.json +122 -0
  8. package/data/seed/sox.json +109 -0
  9. package/dist/index.js +1 -1
  10. package/dist/ingest/adapters/colorado-public.d.ts +25 -0
  11. package/dist/ingest/adapters/colorado-public.d.ts.map +1 -0
  12. package/dist/ingest/adapters/colorado-public.js +76 -0
  13. package/dist/ingest/adapters/colorado-public.js.map +1 -0
  14. package/dist/ingest/adapters/connecticut-cga.d.ts +22 -0
  15. package/dist/ingest/adapters/connecticut-cga.d.ts.map +1 -0
  16. package/dist/ingest/adapters/connecticut-cga.js +116 -0
  17. package/dist/ingest/adapters/connecticut-cga.js.map +1 -0
  18. package/dist/ingest/adapters/ecfr.d.ts +46 -4
  19. package/dist/ingest/adapters/ecfr.d.ts.map +1 -1
  20. package/dist/ingest/adapters/ecfr.js +131 -16
  21. package/dist/ingest/adapters/ecfr.js.map +1 -1
  22. package/dist/ingest/adapters/ffiec.d.ts +42 -0
  23. package/dist/ingest/adapters/ffiec.d.ts.map +1 -0
  24. package/dist/ingest/adapters/ffiec.js +68 -0
  25. package/dist/ingest/adapters/ffiec.js.map +1 -0
  26. package/dist/ingest/adapters/nydfs.d.ts +42 -0
  27. package/dist/ingest/adapters/nydfs.d.ts.map +1 -0
  28. package/dist/ingest/adapters/nydfs.js +68 -0
  29. package/dist/ingest/adapters/nydfs.js.map +1 -0
  30. package/dist/ingest/adapters/regulations-gov.d.ts +11 -12
  31. package/dist/ingest/adapters/regulations-gov.d.ts.map +1 -1
  32. package/dist/ingest/adapters/regulations-gov.js +46 -43
  33. package/dist/ingest/adapters/regulations-gov.js.map +1 -1
  34. package/dist/ingest/adapters/utah-xcode.d.ts +19 -0
  35. package/dist/ingest/adapters/utah-xcode.d.ts.map +1 -0
  36. package/dist/ingest/adapters/utah-xcode.js +112 -0
  37. package/dist/ingest/adapters/utah-xcode.js.map +1 -0
  38. package/dist/ingest/adapters/virginia-law.d.ts +21 -0
  39. package/dist/ingest/adapters/virginia-law.d.ts.map +1 -0
  40. package/dist/ingest/adapters/virginia-law.js +111 -0
  41. package/dist/ingest/adapters/virginia-law.js.map +1 -0
  42. package/package.json +27 -5
  43. package/scripts/build-db.ts +50 -32
  44. package/scripts/check-updates.ts +184 -0
  45. package/scripts/ingest.ts +72 -25
  46. package/src/index.ts +1 -1
  47. package/src/ingest/adapters/colorado-public.ts +96 -0
  48. package/src/ingest/adapters/connecticut-cga.ts +150 -0
  49. package/src/ingest/adapters/ecfr.ts +158 -17
  50. package/src/ingest/adapters/ffiec.ts +77 -0
  51. package/src/ingest/adapters/nydfs.ts +77 -0
  52. package/src/ingest/adapters/regulations-gov.ts +48 -47
  53. package/src/ingest/adapters/utah-xcode.ts +143 -0
  54. package/src/ingest/adapters/virginia-law.ts +140 -0
  55. package/scripts/quality-test.ts +0 -346
  56. package/scripts/test-mcp-tools.ts +0 -187
  57. package/scripts/test-remaining-tools.ts +0 -107
package/README.md CHANGED
@@ -1,24 +1,37 @@
1
- # US Regulations MCP
1
+ # US Regulations MCP Server
2
2
 
3
- [![MCP](https://img.shields.io/badge/MCP-Model%20Context%20Protocol-blue)](https://modelcontextprotocol.io)
4
- [![TypeScript](https://img.shields.io/badge/TypeScript-5.9-blue)](https://www.typescriptlang.org/)
5
- [![License](https://img.shields.io/badge/License-Apache%202.0-green.svg)](LICENSE)
3
+ **Navigate US compliance from the AI age.**
4
+
5
+ [![npm version](https://badge.fury.io/js/@ansvar%2Fus-regulations-mcp.svg)](https://www.npmjs.com/package/@ansvar/us-regulations-mcp)
6
+ [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](https://opensource.org/licenses/Apache-2.0)
7
+ [![GitHub stars](https://img.shields.io/github/stars/Ansvar-Systems/US_compliance_MCP?style=social)](https://github.com/Ansvar-Systems/US_compliance_MCP)
6
8
  [![Node](https://img.shields.io/badge/node-%3E%3D18-brightgreen)](https://nodejs.org)
9
+ [![TypeScript](https://img.shields.io/badge/TypeScript-5.9-blue)](https://www.typescriptlang.org/)
10
+ [![OpenSSF Scorecard](https://api.securityscorecards.dev/projects/github.com/Ansvar-Systems/US_compliance_MCP/badge)](https://securityscorecards.dev/viewer/?uri=github.com/Ansvar-Systems/US_compliance_MCP)
11
+ [![CodeQL](https://github.com/Ansvar-Systems/US_compliance_MCP/workflows/CodeQL/badge.svg)](https://github.com/Ansvar-Systems/US_compliance_MCP/actions/workflows/codeql.yml)
12
+ [![Security](https://github.com/Ansvar-Systems/US_compliance_MCP/workflows/Semgrep/badge.svg)](https://github.com/Ansvar-Systems/US_compliance_MCP/security)
13
+
14
+ Query **HIPAA, CCPA, SOX, GLBA, FERPA, COPPA, FDA 21 CFR Part 11, EPA RMP, FFIEC, NYDFS 500, and 4 state privacy laws (Virginia CDPA, Colorado CPA, Connecticut CTDPA, Utah UCPA)** directly from Claude, Cursor, or any MCP-compatible client.
7
15
 
8
- A Model Context Protocol (MCP) server for US cybersecurity and privacy regulations. Query HIPAA, CCPA, SOX, and more directly from Claude with full-text search, control framework mappings, and compliance action item generation.
16
+ If you're building healthcare tech, consumer apps, or financial services for the US market, this is your compliance reference.
17
+
18
+ Built by [Ansvar Systems](https://ansvar.eu) — Stockholm, Sweden
19
+
20
+ ---
9
21
 
10
- **Built by [Ansvar Systems](https://ansvar.eu)**
22
+ ## Why This Exists
11
23
 
12
- ## Features
24
+ US compliance is scattered across regulations.gov PDFs, eCFR.gov pages, state legislative sites, and agency guidance documents. Whether you're:
25
+ - A **developer** implementing HIPAA security controls or CCPA consumer rights
26
+ - A **product team** navigating breach notification requirements across multiple states
27
+ - A **compliance officer** mapping NIST controls to regulatory obligations
28
+ - A **legal researcher** comparing incident response timelines across federal and state laws
13
29
 
14
- - **Full-text search** across HIPAA, CCPA, and SOX regulations
15
- - **Control framework mappings** (NIST 800-53, NIST CSF)
16
- - **Compliance action items** with structured priority and evidence requirements
17
- - **Cross-regulation comparison** (e.g., compare breach notification requirements)
18
- - **Applicability checking** (which regulations apply to your sector?)
19
- - **Official term definitions** from regulatory sources
20
- - **Section retrieval** with cross-references and metadata
21
- - **Token-efficient** search results with highlighted snippets
30
+ ...you shouldn't need to navigate fragmented federal agencies, 50 state legislatures, and conflicting PDF formats. Ask Claude. Get the exact section. With context.
31
+
32
+ This MCP server makes US regulations **searchable, cross-referenceable, and AI-readable**.
33
+
34
+ ---
22
35
 
23
36
  ## Quick Start
24
37
 
@@ -28,13 +41,12 @@ A Model Context Protocol (MCP) server for US cybersecurity and privacy regulatio
28
41
  npm install @ansvar/us-regulations-mcp
29
42
  ```
30
43
 
31
- ### Claude Desktop Configuration
44
+ ### Claude Desktop
32
45
 
33
- Add to your Claude Desktop config file:
46
+ Add to your `claude_desktop_config.json`:
34
47
 
35
- **macOS**: `~/Library/Application Support/Claude/claude_desktop_config.json`
36
-
37
- **Windows**: `%APPDATA%\Claude\claude_desktop_config.json`
48
+ **macOS:** `~/Library/Application Support/Claude/claude_desktop_config.json`
49
+ **Windows:** `%APPDATA%\Claude\claude_desktop_config.json`
38
50
 
39
51
  ```json
40
52
  {
@@ -47,53 +59,143 @@ Add to your Claude Desktop config file:
47
59
  }
48
60
  ```
49
61
 
50
- Restart Claude Desktop. The server will appear in the MCP tools menu.
62
+ Restart Claude Desktop. Done.
63
+
64
+ ### Cursor / VS Code
65
+
66
+ ```json
67
+ {
68
+ "mcp.servers": {
69
+ "us-regulations": {
70
+ "command": "npx",
71
+ "args": ["-y", "@ansvar/us-regulations-mcp"]
72
+ }
73
+ }
74
+ }
75
+ ```
76
+
77
+ ---
78
+
79
+ ## Security & Compliance
80
+
81
+ This MCP server follows **OpenSSF Best Practices** for secure open source development:
82
+
83
+ - ✅ **Automated Security Scanning**
84
+ - CodeQL (semantic code analysis)
85
+ - Semgrep (SAST security rules)
86
+ - Trivy (vulnerability scanning)
87
+ - Gitleaks (secret detection)
88
+ - Socket Security (supply chain monitoring)
89
+
90
+ - ✅ **Daily Freshness Monitoring**
91
+ - Automated checks for regulation updates from official sources
92
+ - Auto-generates PRs when changes detected
93
+
94
+ - ✅ **Secure Publishing**
95
+ - npm provenance attestation (signed packages)
96
+ - MCP Registry cryptographic signing
97
+ - Azure Key Vault for secret management
98
+
99
+ - ✅ **Security Metrics**
100
+ - OpenSSF Scorecard weekly evaluation
101
+ - GitHub Security tab for vulnerability tracking
102
+
103
+ **Report security issues:** See [SECURITY.md](SECURITY.md)
104
+
105
+ ---
51
106
 
52
107
  ## Example Queries
53
108
 
54
- Try these queries in Claude Desktop:
109
+ Once connected, just ask naturally:
55
110
 
56
111
  ### Healthcare & HIPAA
57
- ```
58
- "What are the HIPAA security rule requirements for access controls?"
59
- "Does my telemedicine app need to comply with HIPAA?"
60
- "What audit logs does HIPAA require for ePHI access?"
61
- ```
112
+ - *"What are the HIPAA security rule requirements for access controls?"*
113
+ - *"Does my telemedicine app need to comply with HIPAA?"*
114
+ - *"What audit logs does HIPAA require for ePHI access?"*
115
+ - *"How long do I have to report a HIPAA breach?"*
62
116
 
63
117
  ### Privacy & CCPA
64
- ```
65
- "Compare breach notification timelines between HIPAA and CCPA"
66
- "What consumer rights does CCPA provide for data deletion?"
67
- "Do I need to comply with CCPA if I have 10,000 California customers?"
68
- ```
118
+ - *"Compare breach notification timelines between HIPAA and CCPA"*
119
+ - *"What consumer rights does CCPA provide for data deletion?"*
120
+ - *"Do I need to comply with CCPA if I have 10,000 California customers?"*
121
+ - *"What is a 'sale' of personal information under CCPA?"*
69
122
 
70
123
  ### Financial & SOX
71
- ```
72
- "What IT controls does SOX Section 404 require?"
73
- "Which NIST 800-53 controls satisfy SOX audit requirements?"
74
- "How long must I retain financial records under SOX?"
75
- ```
124
+ - *"What IT controls does SOX Section 404 require?"*
125
+ - *"Which NIST 800-53 controls satisfy SOX audit requirements?"*
126
+ - *"How long must I retain financial records under SOX?"*
127
+ - *"What are the requirements for SOX internal control assessments?"*
128
+
129
+ ### Financial Services & GLBA
130
+ - *"What are the GLBA safeguards rule requirements for customer data protection?"*
131
+ - *"Compare encryption requirements across HIPAA, GLBA, and SOX"*
132
+
133
+ ### Banking & FFIEC
134
+ - *"What are the FFIEC guidelines for information security governance?"*
135
+ - *"What does FFIEC require for business continuity planning?"*
136
+ - *"Compare FFIEC cybersecurity requirements with NYDFS 500"*
137
+
138
+ ### New York Financial Services & NYDFS
139
+ - *"What are the NYDFS 500 requirements for multi-factor authentication?"*
140
+ - *"When must I notify NYDFS of a cybersecurity event?"*
141
+ - *"What are the penetration testing requirements under NYDFS 500?"*
142
+ - *"What information security program elements does GLBA require?"*
143
+
144
+ ### State Privacy Laws - Virginia CDPA
145
+ - *"What consumer rights does Virginia CDPA provide?"*
146
+ - *"What are the data protection assessment requirements under Virginia CDPA?"*
147
+ - *"Compare opt-out mechanisms between CCPA and Virginia CDPA"*
148
+
149
+ ### State Privacy Laws - Colorado CPA
150
+ - *"What is the universal opt-out mechanism under Colorado CPA?"*
151
+ - *"What data subject rights does Colorado CPA grant?"*
152
+ - *"Colorado CPA requirements for data controllers vs processors"*
153
+
154
+ ### State Privacy Laws - Connecticut CTDPA
155
+ - *"What are Connecticut CTDPA data protection assessment requirements?"*
156
+ - *"Compare consumer rights between CCPA and Connecticut CTDPA"*
157
+ - *"What sensitive data processing restrictions apply under Connecticut law?"*
158
+
159
+ ### State Privacy Laws - Utah UCPA
160
+ - *"What are Utah UCPA consumer privacy rights?"*
161
+ - *"Utah UCPA data controller obligations and exemptions"*
162
+ - *"Compare Utah UCPA with other state privacy laws"*
163
+
164
+ ### Education & FERPA
165
+ - *"What are FERPA requirements for student record access?"*
166
+ - *"Can I share student data with third-party analytics tools under FERPA?"*
167
+ - *"What parental consent is needed to disclose student directory information?"*
168
+
169
+ ### Children's Privacy & COPPA
170
+ - *"What parental consent mechanisms are acceptable under COPPA?"*
171
+ - *"COPPA requirements for collecting personal information from children under 13"*
172
+ - *"Do I need COPPA compliance for a kids' mobile app?"*
173
+
174
+ ### Pharmaceutical & FDA
175
+ - *"What are FDA 21 CFR Part 11 requirements for electronic signatures?"*
176
+ - *"How must clinical trial data be validated under 21 CFR Part 11?"*
177
+ - *"What audit trail requirements apply to electronic records in pharma?"*
178
+
179
+ ### Environmental & EPA
180
+ - *"Which chemical facilities must submit an EPA Risk Management Plan?"*
181
+ - *"What accident prevention requirements does EPA RMP mandate?"*
182
+ - *"How often must I update my facility's EPA RMP?"*
76
183
 
77
184
  ### Cross-Regulation Analysis
78
- ```
79
- "Compare incident response requirements across HIPAA, CCPA, and SOX"
80
- "Which regulations apply to a fintech company in California?"
81
- "Map NIST CSF to our HIPAA and SOX obligations"
82
- ```
185
+ - *"Compare incident response requirements across HIPAA, CCPA, and SOX"*
186
+ - *"Which regulations apply to a fintech company in California?"*
187
+ - *"Map NIST CSF to our HIPAA and SOX obligations"*
188
+ - *"What are my data retention requirements across all regulations?"*
83
189
 
84
- ### Compliance Planning
85
- ```
86
- "Generate compliance action items for HIPAA security risk assessment"
87
- "What evidence do I need for HIPAA access control compliance?"
88
- "List all CCPA consumer rights requirements"
89
- ```
190
+ ---
90
191
 
91
192
  ## What's Included
92
193
 
93
- ### MVP Regulations (3)
194
+ ### v1.2 Regulations (14 total, ~380 sections)
94
195
 
196
+ **Healthcare & Privacy:**
95
197
  - **HIPAA** - Health Insurance Portability and Accountability Act
96
- - Privacy Rule (45 CFR Part 160, 164 Subpart E)
198
+ - Privacy Rule (45 CFR Part 164 Subpart E)
97
199
  - Security Rule (45 CFR 164 Subpart C)
98
200
  - Breach Notification Rule (45 CFR 164 Subpart D)
99
201
 
@@ -101,10 +203,67 @@ Try these queries in Claude Desktop:
101
203
  - California Civil Code §1798.100-1798.199
102
204
  - Consumer rights and business obligations
103
205
 
206
+ **Financial Services:**
104
207
  - **SOX** - Sarbanes-Oxley Act
105
- - Section 404 (Management Assessment of Internal Controls)
106
- - IT controls and audit requirements
107
- - Financial data retention requirements
208
+ - Key statute sections (Sections 101, 201, 301, 302, 404, 409, 802, 806, 906)
209
+ - SEC implementing regulations (17 CFR 229.308, 240.13a-14, 240.13a-15)
210
+ - PCAOB auditing standards (AS 2201)
211
+ - IT General Controls guidance
212
+
213
+ - **GLBA** - Gramm-Leach-Bliley Act Safeguards Rule (NEW in v1.1)
214
+ - 16 CFR Part 314
215
+ - Financial institution data security requirements
216
+
217
+ **Education:**
218
+ - **FERPA** - Family Educational Rights and Privacy Act (NEW in v1.1)
219
+ - 34 CFR Part 99
220
+ - Student education records privacy
221
+
222
+ **Children's Privacy:**
223
+ - **COPPA** - Children's Online Privacy Protection Act (NEW in v1.1)
224
+ - 16 CFR Part 312
225
+ - Requirements for collecting data from children under 13
226
+
227
+ **Pharmaceutical & Medical Devices:**
228
+ - **FDA 21 CFR Part 11** - Electronic Records and Signatures (NEW in v1.1)
229
+ - Electronic record keeping and digital signatures for FDA-regulated industries
230
+
231
+ **Environmental & Chemical Safety:**
232
+ - **EPA RMP** - Risk Management Plan Rule (NEW in v1.1)
233
+ - 40 CFR Part 68
234
+ - Chemical facility accident prevention
235
+
236
+ **Banking & Financial Institutions:**
237
+ - **FFIEC** - IT Examination Handbook (NEW in v1.1)
238
+ - Federal Financial Institutions Examination Council guidelines
239
+ - Information security and cybersecurity for banking
240
+
241
+ **State Financial Services:**
242
+ - **NYDFS 500** - NY DFS Cybersecurity Regulation (NEW in v1.1)
243
+ - 23 NYCRR 500
244
+ - Cybersecurity requirements for New York financial services institutions
245
+
246
+ **State Privacy Laws:**
247
+ - **Virginia CDPA** - Consumer Data Protection Act (NEW in v1.2)
248
+ - Va. Code Ann. §59.1-575 to 59.1-585
249
+ - Consumer privacy rights and business obligations
250
+
251
+ - **Colorado CPA** - Colorado Privacy Act (NEW in v1.2)
252
+ - C.R.S. §6-1-1301 to 6-1-1313
253
+ - Universal opt-out mechanism requirements
254
+
255
+ - **Connecticut CTDPA** - Connecticut Data Privacy Act (NEW in v1.2)
256
+ - Conn. Gen. Stat. §42-515 to 42-524
257
+ - Data protection assessment requirements
258
+
259
+ - **Utah UCPA** - Utah Consumer Privacy Act (NEW in v1.2)
260
+ - Utah Code Ann. §13-61-101 to 13-61-404
261
+ - Business-friendly privacy approach
262
+
263
+ **Payment Card Industry:**
264
+ - **PCI DSS** - Payment Card Industry Data Security Standard (cross-reference)
265
+ - See [security-controls-mcp](https://github.com/Ansvar-Systems/security-controls-mcp) for PCI DSS v4.0 requirements
266
+ - This MCP provides PCI SSC official requirements and testing procedures
108
267
 
109
268
  ### Control Framework Mappings
110
269
 
@@ -112,9 +271,120 @@ Try these queries in Claude Desktop:
112
271
  - **NIST CSF 2.0** - Cybersecurity Framework
113
272
  - **ISO 27001** - Information Security Management (planned)
114
273
 
115
- ### Data Status
274
+ ### Roadmap
275
+
276
+ Additional regulations in development:
277
+ - **State breach notification laws** (50 states) - Breach reporting requirements across all US states
278
+ - **FISMA** - Federal Information Security Management Act - Federal agency cybersecurity
279
+ - **CAN-SPAM** - Email marketing regulations - Commercial email requirements
280
+ - **State privacy laws** - Expansion to additional states (Montana, Iowa, Indiana, Tennessee, Oregon)
281
+
282
+ **Detailed coverage:** [docs/coverage.md](docs/coverage.md)
283
+
284
+ ---
285
+
286
+ ## 🎬 See It In Action
116
287
 
117
- **MVP Note**: This is an initial release with placeholder ingestion adapters. The database schema and all 9 MCP tools are fully functional. Automated ingestion from official API sources (regulations.gov, ecfr.gov, California LegInfo) is in development.
288
+ ### Why This Works
289
+
290
+ **Verbatim Source Text (No LLM Processing):**
291
+ - All regulatory text is ingested from official sources (eCFR.gov, California LegInfo)
292
+ - Snippets are returned **unchanged** from SQLite FTS5 database rows
293
+ - Zero LLM summarization or paraphrasing — the database contains regulation text, not AI interpretations
294
+ - **Note:** HTML-to-text conversion normalizes whitespace/formatting, but preserves content
295
+
296
+ **Smart Context Management:**
297
+ - Search returns **32-token snippets** with highlighted matches (safe for context)
298
+ - Section retrieval warns about token usage (some sections can be large)
299
+ - Cross-references help navigate without loading everything at once
300
+
301
+ **Technical Architecture:**
302
+ ```
303
+ eCFR/LegInfo HTML → Parse → SQLite → FTS5 snippet() → MCP response
304
+ ↑ ↑
305
+ Formatting only Verbatim database query
306
+ ```
307
+
308
+ ### Example: regulations.gov vs. This MCP
309
+
310
+ | regulations.gov / eCFR | This MCP Server |
311
+ |------------------------|-----------------|
312
+ | Search by CFR citation | Search by plain English: *"breach notification timeline"* |
313
+ | Navigate fragmented agency sites | Get the exact section with context |
314
+ | Manual cross-referencing across federal/state | `compare_requirements` tool does it instantly |
315
+ | "Which regulations apply to me?" → weeks of research | `check_applicability` tool → answer in seconds |
316
+ | Copy-paste from PDFs with formatting issues | Section + definitions + related requirements |
317
+ | Check eCFR, regulations.gov, 50 state sites | Unified search across all sources |
318
+ | No API for most sources | MCP protocol → AI-native |
319
+
320
+ **regulations.gov example:** Download HIPAA PDF → Ctrl+F "breach" → Read §164.410 → Google "What's a 'reportable breach'?" → Cross-reference CCPA → Check California site → Repeat for SOX
321
+
322
+ **This MCP:** *"Compare breach notification requirements across HIPAA, CCPA, and SOX"* → Done.
323
+
324
+ ---
325
+
326
+ ## ⚠️ Important Disclaimers
327
+
328
+ ### Legal Advice
329
+
330
+ > **🚨 THIS TOOL IS NOT LEGAL ADVICE 🚨**
331
+ >
332
+ > This tool provides regulatory text for research and educational purposes. However:
333
+ > - **Control mappings** (NIST 800-53, NIST CSF) are interpretive guidance, NOT official HHS, NIST, or agency crosswalks
334
+ > - **Applicability rules** are generalizations, not legal determinations
335
+ > - **Cross-references** are research helpers, not compliance mandates
336
+ >
337
+ > **Always verify against official sources and consult qualified legal counsel for compliance decisions.**
338
+
339
+ ### Data Source Transparency
340
+
341
+ > **📋 Source Quality Disclosure**
342
+ >
343
+ > **Tier 1 - Official API Sources (Authoritative):**
344
+ > - HIPAA, GLBA, FERPA, COPPA, FDA 21 CFR 11, EPA RMP — sourced from **eCFR.gov official API**
345
+ > - CCPA/CPRA — sourced from **California LegInfo official site**
346
+ >
347
+ > **Tier 2 - Official State Sources (HTML Scraping):**
348
+ > - Virginia CDPA — sourced from law.lis.virginia.gov
349
+ > - Connecticut CTDPA — sourced from cga.ct.gov
350
+ > - Utah UCPA — sourced from le.utah.gov
351
+ > - Colorado CPA — seed data verified against leg.colorado.gov
352
+ >
353
+ > **Tier 3 - Seed Data (Verified but Static):**
354
+ > - FFIEC IT Handbook — examination guidance extracted from ffiec.gov booklets
355
+ > - NYDFS 500 — regulatory text from dfs.ny.gov
356
+ > - SOX — statute and SEC implementing regulations
357
+ >
358
+ > Seed data sources include official source attribution and verification dates. Users should check official sources for updates.
359
+ >
360
+ > **Control Framework Mappings:** HIPAA-to-NIST and CCPA-to-NIST mappings are interpretive guidance to assist compliance research. They are NOT official agency crosswalks. Consult NIST SP 800-66 and official agency guidance for authoritative mappings.
361
+
362
+ ### Token Usage
363
+
364
+ > **⚠️ Context Window Warning**
365
+ >
366
+ > Some regulation sections can be large (e.g., HIPAA Privacy Rule sections with extensive commentary). The MCP server:
367
+ > - **Search tool**: Returns smart snippets (safe for context)
368
+ > - **Get section tool**: Returns full text (may consume significant tokens)
369
+ > - **Recommendation**: Use search first, then fetch specific sections as needed
370
+ >
371
+ > Claude Desktop has a 200k token context window. Monitor your usage when retrieving multiple large sections.
372
+
373
+ ### MVP Status
374
+
375
+ > **📋 Initial Release**
376
+ >
377
+ > This is a production-ready MVP with three foundational regulations (HIPAA, CCPA, SOX). The database schema and all 9 MCP tools are fully functional and thoroughly tested (100% test coverage).
378
+ >
379
+ > **Data Ingestion**: Automated ingestion from official API sources (eCFR.gov, California LegInfo) is operational. Additional regulations are being added to the database.
380
+ >
381
+ > **Coming Soon**: Additional federal regulations (GLBA, FERPA, FISMA) and state breach notification laws.
382
+
383
+ ### NIST Standards
384
+
385
+ **No copyrighted NIST standards are included.** Control mappings reference NIST 800-53 control IDs only (e.g., "AC-1", "SI-4"). While NIST standards are freely available from NIST, this tool helps map regulations to controls but doesn't replace reading the standards themselves.
386
+
387
+ ---
118
388
 
119
389
  ## Available Tools
120
390
 
@@ -132,7 +402,9 @@ The server provides 9 MCP tools:
132
402
  | `get_evidence_requirements` | Get compliance evidence requirements for a section |
133
403
  | `get_compliance_action_items` | Generate structured compliance action items |
134
404
 
135
- See [docs/tools.md](docs/tools.md) for complete tool reference with examples.
405
+ **Detailed tool reference:** [docs/tools.md](docs/tools.md)
406
+
407
+ ---
136
408
 
137
409
  ## Development
138
410
 
@@ -145,8 +417,8 @@ See [docs/tools.md](docs/tools.md) for complete tool reference with examples.
145
417
 
146
418
  ```bash
147
419
  # Clone the repository
148
- git clone https://github.com/ansvar-systems/us-regulations-mcp.git
149
- cd us-regulations-mcp
420
+ git clone https://github.com/Ansvar-Systems/US_compliance_MCP.git
421
+ cd US_compliance_MCP
150
422
 
151
423
  # Install dependencies
152
424
  npm install
@@ -154,6 +426,9 @@ npm install
154
426
  # Build the database schema
155
427
  npm run build:db
156
428
 
429
+ # Load seed data
430
+ npm run load-seed
431
+
157
432
  # Build the TypeScript code
158
433
  npm run build
159
434
 
@@ -167,7 +442,9 @@ npm run dev
167
442
  npm run build # Compile TypeScript to dist/
168
443
  npm run dev # Run server in development mode with tsx
169
444
  npm run build:db # Initialize database schema
170
- npm test # Run test suite with vitest
445
+ npm run load-seed # Load seed data for testing
446
+ npm test # Run test suite with vitest (100% coverage)
447
+ npm run test:mcp # Test MCP tool integration
171
448
  ```
172
449
 
173
450
  ### Project Structure
@@ -187,16 +464,20 @@ us-regulations-mcp/
187
464
  │ │ ├── definitions.ts # Term definitions
188
465
  │ │ ├── evidence.ts # Evidence requirements
189
466
  │ │ └── action-items.ts # Compliance action items
190
- │ └── ingest/ # Ingestion framework (in development)
467
+ │ └── ingest/ # Ingestion framework
191
468
  │ ├── framework.ts # Base interfaces
192
469
  │ └── adapters/ # Source-specific adapters
193
470
  ├── scripts/
194
- └── build-db.ts # Database schema builder
471
+ ├── build-db.ts # Database schema builder
472
+ │ ├── load-seed-data.ts # Seed data loader
473
+ │ └── ingest.ts # Data ingestion orchestrator
195
474
  ├── data/
196
475
  │ └── regulations.db # SQLite database
197
476
  └── docs/ # Documentation
198
477
  ```
199
478
 
479
+ ---
480
+
200
481
  ## Architecture Overview
201
482
 
202
483
  ### Database
@@ -215,9 +496,10 @@ The server uses SQLite with FTS5 (full-text search) for efficient querying:
215
496
 
216
497
  The ingestion framework uses an adapter pattern to normalize data from multiple US regulatory sources:
217
498
 
218
- - **regulations.gov API** - Federal regulations
219
- - **ecfr.gov API** - Electronic Code of Federal Regulations (HIPAA)
499
+ - **eCFR.gov API** - Electronic Code of Federal Regulations (HIPAA, SOX)
220
500
  - **California LegInfo API** - State legislation (CCPA/CPRA)
501
+ - **regulations.gov API** - Federal regulatory documents
502
+ - **Agency-specific sources** - HHS, SEC, FTC guidance
221
503
 
222
504
  Each adapter handles source-specific pagination, authentication, and data normalization.
223
505
 
@@ -230,46 +512,107 @@ The server implements the Model Context Protocol specification:
230
512
  - **Structured error handling** with informative messages
231
513
  - **Token-efficient responses** with snippet highlighting
232
514
 
233
- ## Coverage & Roadmap
515
+ ---
234
516
 
235
- See [docs/coverage.md](docs/coverage.md) for:
517
+ ## Related Projects: Complete Compliance Suite
236
518
 
237
- - Current regulation coverage status
238
- - Planned future regulations
239
- - Control framework mappings
240
- - Data source details
241
- - Update frequency
519
+ This server is part of **Ansvar's Compliance Suite** - three MCP servers that work together for end-to-end compliance coverage:
242
520
 
243
- ## License
521
+ ### 🇪🇺 [EU Regulations MCP](https://github.com/Ansvar-Systems/EU_compliance_MCP)
522
+ **Query 47 EU regulations directly from Claude**
523
+ - GDPR, AI Act, DORA, NIS2, MiFID II, PSD2, eIDAS, MDR, and 39 more
524
+ - Full regulatory text with article-level search
525
+ - Cross-regulation reference and comparison
526
+ - **Install:** `npx @ansvar/eu-regulations-mcp`
527
+
528
+ ### 🇺🇸 US Regulations MCP (This Project)
529
+ **Query US federal and state compliance laws directly from Claude**
530
+ - HIPAA, CCPA, SOX, GLBA, FERPA, COPPA, FDA 21 CFR Part 11, and 8 more
531
+ - Federal and state privacy law comparison
532
+ - Breach notification timeline mapping
533
+ - **Install:** `npm install @ansvar/us-regulations-mcp`
244
534
 
245
- This project is licensed under the Apache License 2.0. See [LICENSE](LICENSE) for details.
535
+ ### 🔐 [Security Controls MCP](https://github.com/Ansvar-Systems/security-controls-mcp)
536
+ **Query 1,451 security controls across 28 frameworks**
537
+ - ISO 27001, NIST CSF, DORA, PCI DSS, SOC 2, CMMC, FedRAMP, and 21 more
538
+ - Bidirectional framework mapping and gap analysis
539
+ - Import your purchased standards for official text
540
+ - **Install:** `pipx install security-controls-mcp`
246
541
 
247
- ## Disclaimer
542
+ ### How They Work Together
543
+
544
+ **Regulations → Controls Implementation Workflow:**
545
+
546
+ ```
547
+ 1. "What are HIPAA's security safeguard requirements?"
548
+ → US Regulations MCP returns 45 CFR § 164.306 full text
248
549
 
249
- This tool provides regulatory text from official sources but is **NOT legal advice**. Control mappings and applicability rules are interpretive aids only. Always consult qualified legal counsel for compliance decisions.
550
+ 2. "What security controls satisfy HIPAA §164.306?"
551
+ → Security Controls MCP maps to NIST 800-53, ISO 27001, and SCF controls
552
+
553
+ 3. "Show me NIST 800-53 AC-1 implementation details"
554
+ → Security Controls MCP returns control requirements and framework mappings
555
+ ```
556
+
557
+ **Complete compliance in one chat:**
558
+ - **EU/US Regulations MCPs** tell you WHAT compliance requirements you must meet
559
+ - **Security Controls MCP** tells you HOW to implement controls that satisfy those requirements
560
+
561
+ ---
562
+
563
+ ## About Ansvar Systems
564
+
565
+ We build AI-accelerated threat modeling and compliance tools for automotive, financial services, and healthcare. This MCP server started as our internal reference tool for US regulations — turns out everyone building for US markets has the same compliance research frustrations.
566
+
567
+ So we're open-sourcing it. Navigating federal and state regulations shouldn't require a legal team.
568
+
569
+ **[ansvar.eu](https://ansvar.eu)** — Stockholm, Sweden
570
+
571
+ ---
572
+
573
+ ## Documentation
574
+
575
+ - **[Coverage Details](docs/coverage.md)** — All regulations with section counts
576
+ - **[Available Tools](docs/tools.md)** — Detailed tool descriptions with examples
577
+ - **[Development Status](docs/STATUS.md)** — Current implementation status
578
+
579
+ ---
250
580
 
251
581
  ## Contributing
252
582
 
253
- Contributions are welcome. Please open an issue or pull request for:
583
+ Contributions are welcome! Please open an issue or pull request for:
254
584
 
255
585
  - Bug fixes
256
586
  - New regulation support
257
587
  - Additional control framework mappings
258
588
  - Documentation improvements
589
+ - Test coverage enhancements
590
+
591
+ ---
259
592
 
260
593
  ## Support
261
594
 
262
595
  For issues, questions, or feature requests:
263
596
 
264
- - Open a [GitHub issue](https://github.com/ansvar-systems/us-regulations-mcp/issues)
597
+ - Open a [GitHub issue](https://github.com/Ansvar-Systems/US_compliance_MCP/issues)
265
598
  - Email: hello@ansvar.eu
266
599
 
600
+ ---
601
+
267
602
  ## Acknowledgments
268
603
 
269
- - Based on the EU Compliance MCP architecture
604
+ - Regulatory data from official US government sources (eCFR.gov, California LegInfo)
270
605
  - Uses the [Model Context Protocol](https://modelcontextprotocol.io) by Anthropic
271
- - Regulatory data from official US government sources
606
+ - Inspired by the EU Regulations MCP architecture
607
+
608
+ ---
609
+
610
+ ## License
611
+
612
+ Apache License 2.0. See [LICENSE](./LICENSE) for details.
272
613
 
273
614
  ---
274
615
 
275
- **Built by Ansvar Systems** - Making compliance accessible through AI
616
+ <p align="center">
617
+ <sub>Built with care in Stockholm, Sweden</sub>
618
+ </p>
Binary file