@ansvar/automotive-cybersecurity-mcp 1.0.0

package/.prettierrc.json

@@ -0,0 +1,9 @@
+{
+  "semi": true,
+  "trailingComma": "es5",
+  "singleQuote": true,
+  "printWidth": 100,
+  "tabWidth": 2,
+  "useTabs": false,
+  "endOfLine": "lf"
+}

package/CHANGELOG.md

@@ -0,0 +1,63 @@
+# Changelog
+
+All notable changes to this project will be documented in this file.
+
+The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
+and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
+
+## [Unreleased]
+
+## [0.1.0] - 2026-01-29
+
+### Added
+- Complete UNECE R155 regulation content (12 articles + 5 annexes)
+  - Article 7: Full 22KB CSMS specifications
+  - Annex 5: Comprehensive 148KB threat catalog
+  - All official annexes (communication forms, approval marks, certificates)
+- Complete UNECE R156 regulation content (12 articles + 4 annexes)
+  - Article 7: SUMS requirements
+  - All official annexes
+- SQLite database with FTS5 full-text search (620KB)
+- Three MCP tools: `list_sources`, `get_requirement`, `search_requirements`
+- Comprehensive test suite (91 tests, 100% pass rate)
+- TypeScript with strict type checking
+- Complete documentation:
+  - README.md with quick start
+  - QUICK_START.md for 5-minute setup
+  - docs/USAGE_GUIDE.md with role-specific scenarios
+  - R155_R156_INTEGRATION_SUMMARY.md with technical details
+- CI/CD pipeline with:
+  - Multi-platform testing (Ubuntu, macOS, Windows)
+  - Multi-version Node.js support (18, 20, 22)
+  - Gitleaks secret scanning
+  - CodeQL security analysis
+  - Automated npm publishing
+
+### Changed
+- Database structure: Hierarchical (43 items) → Flat (33 items) with complete text
+- Content source: Manual summaries → Official UNECE text via EU Compliance MCP
+- Database size: 152KB → 620KB (4x increase)
+- Content size: ~50KB → 294KB (6x increase)
+
+### Attribution
+- R155/R156 content sourced from [EU Compliance MCP](https://github.com/Ansvar-Systems/EU_compliance_MCP)
+- License: Apache 2.0 (compatible)
+- Data: Official UNECE regulations from EUR-Lex
+
+### Technical
+- Node.js: 18+ required
+- Database: SQLite 3 with FTS5
+- Query performance: <1ms average
+- Package size: ~650KB (includes 620KB database)
+
+## [0.0.1] - 2026-01-28 (Initial Development)
+
+### Added
+- Initial MCP server structure
+- Sample R155 content (hierarchical structure)
+- ISO 21434 Clause 9.3 guidance
+- Basic testing framework
+
+[Unreleased]: https://github.com/Ansvar-Systems/Automotive-MCP/compare/v0.1.0...HEAD
+[0.1.0]: https://github.com/Ansvar-Systems/Automotive-MCP/releases/tag/v0.1.0
+[0.0.1]: https://github.com/Ansvar-Systems/Automotive-MCP/releases/tag/v0.0.1

package/CONTRIBUTING.md

@@ -0,0 +1,144 @@
+# Contributing to Automotive Cybersecurity MCP
+
+Thank you for your interest in contributing to the Automotive Cybersecurity MCP Server! This document provides guidelines and instructions for contributing.
+
+## Code of Conduct
+
+This project adheres to the [Contributor Covenant Code of Conduct](CODE_OF_CONDUCT.md). By participating, you are expected to uphold this code.
+
+## How to Contribute
+
+### Reporting Bugs
+
+Before creating bug reports, please check existing issues to avoid duplicates. When creating a bug report, include:
+
+- **Clear title** describing the issue
+- **Steps to reproduce** the behavior
+- **Expected behavior** vs actual behavior
+- **Environment details** (Node.js version, OS, Claude Desktop version)
+- **Error messages** or logs if applicable
+
+### Suggesting Enhancements
+
+Enhancement suggestions are welcome! Please include:
+
+- **Clear title** describing the enhancement
+- **Detailed description** of the proposed functionality
+- **Use case** explaining why this would be valuable
+- **Possible implementation** if you have ideas
+
+### Pull Requests
+
+1. **Fork the repository** and create your branch from `main`
+2. **Follow the coding style** of the project
+3. **Add tests** for any new functionality
+4. **Update documentation** if needed
+5. **Ensure CI passes** before requesting review
+
+## Development Setup
+
+### Prerequisites
+
+- Node.js 18 or higher
+- npm 9 or higher
+
+### Local Development
+
+```bash
+# Clone your fork
+git clone https://github.com/YOUR-USERNAME/Automotive-MCP.git
+cd Automotive-MCP
+
+# Install dependencies
+npm install
+
+# Build the database
+npm run build:db
+
+# Build TypeScript
+npm run build
+
+# Run tests
+npm test
+
+# Run in development mode
+npm run dev
+```
+
+### Project Structure
+
+```
+├── src/               # TypeScript source code
+│   ├── index.ts       # MCP server entry point
+│   ├── tools/         # Tool implementations
+│   ├── db/            # Database operations
+│   └── types/         # TypeScript type definitions
+├── scripts/           # Build and utility scripts
+├── data/              # Seed data and generated database
+├── tests/             # Test files
+└── .github/           # GitHub Actions and templates
+```
+
+## Coding Guidelines
+
+### TypeScript
+
+- Use TypeScript strict mode
+- Prefer `const` over `let`
+- Use meaningful variable names
+- Add JSDoc comments for public APIs
+
+### Commits
+
+Follow [Conventional Commits](https://www.conventionalcommits.org/):
+
+- `feat:` new feature
+- `fix:` bug fix
+- `docs:` documentation only
+- `test:` adding or updating tests
+- `refactor:` code change that neither fixes a bug nor adds a feature
+- `chore:` maintenance tasks
+- `ci:` CI/CD changes
+
+Examples:
+```
+feat: add support for ISO 21434 clause queries
+fix: handle empty search results gracefully
+docs: update installation instructions
+```
+
+### Testing
+
+- Write tests for new features
+- Maintain or improve test coverage
+- Run `npm test` before submitting PRs
+
+## Database Changes
+
+The automotive regulations database is built from seed files in `data/seed/`. If you need to modify the database schema or content:
+
+1. Update the relevant seed files
+2. Update the schema in `scripts/build-db.ts` if needed
+3. Rebuild with `npm run build:db`
+4. Add tests for new data
+
+## Review Process
+
+1. **Automated checks** must pass (CI, linting, tests)
+2. **Code review** by a maintainer
+3. **Approval** required before merging
+4. **Squash merge** is preferred for clean history
+
+## Getting Help
+
+- Open an issue for questions
+- Check existing documentation
+- Review closed issues for similar problems
+
+## Recognition
+
+Contributors are recognized in release notes. Thank you for helping improve automotive cybersecurity tooling!
+
+## License
+
+By contributing, you agree that your contributions will be licensed under the [Apache 2.0 License](LICENSE).

package/LICENSE

@@ -0,0 +1,201 @@
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Support. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright 2026 Jeffrey von Rotz / Ansvar Systems
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

package/QUICK_START.md

@@ -0,0 +1,189 @@
+# Quick Start: Automotive Cybersecurity MCP
+
+## What Is This?
+
+**Ask Claude questions about automotive cybersecurity regulations (UNECE R155/R156) and get instant answers with exact source references.**
+
+Stop searching through 200+ page PDFs. Just ask.
+
+---
+
+## 30-Second Setup
+
+1. Add to `~/.claude/claude_desktop_config.json`:
+```json
+{
+  "mcpServers": {
+    "automotive": {
+      "command": "npx",
+      "args": ["-y", "@ansvar/automotive-cybersecurity-mcp"]
+    }
+  }
+}
+```
+
+2. Restart Claude Desktop
+
+3. Done! Start asking questions.
+
+---
+
+## When to Use This
+
+### ✅ USE THIS WHEN:
+
+**1. Preparing for Type Approval**
+- "What CSMS documentation does R155 require?"
+- "Show me R155 Annex 4 certificate template"
+
+**2. Answering Customer Questions**
+- "What does R155 Article 7.2.2.2 say about vulnerability management?"
+- "Explain R156 software update requirements"
+
+**3. Creating Compliance Docs**
+- "List all R155 incident response requirements"
+- "Generate R155 Article 7 compliance checklist"
+
+**4. Gap Analysis**
+- "What are the R155 requirements for supply chain security?"
+- "Compare our process to R156 Article 7"
+
+**5. Training & Education**
+- "Explain R155 in simple terms"
+- "Create quiz questions from R155 Article 7"
+
+---
+
+## Common Questions
+
+### OEM Preparing for Approval
+```
+Q: "I'm preparing our R155 type approval package. What do I need?"
+A: [Claude returns Article 3, Annex 4, Annex 5 requirements]
+
+Q: "Show me the CSMS certificate template"
+A: [Claude returns Annex 4 complete template]
+```
+
+### Supplier Responding to RFQ
+```
+Q: "Customer asked about R155 Article 7.2.2.2.f - what is that?"
+A: [Claude returns supply chain security requirements]
+
+Q: "What evidence do I need to provide?"
+A: [Claude explains expected documentation]
+```
+
+### Security Engineer Implementing Controls
+```
+Q: "What does R155 require for penetration testing?"
+A: [Claude searches and returns Article 7.2.3 testing requirements]
+
+Q: "Search R155 for 'intrusion detection'"
+A: [Claude finds all mentions with context]
+```
+
+---
+
+## What You Get
+
+**Content:**
+- ✅ Complete R155 regulation (17 items, 12 articles + 5 annexes)
+- ✅ Complete R156 regulation (16 items, 12 articles + 4 annexes)
+- ✅ Full-text search across 294KB of regulation text
+- ✅ Exact article references for citations
+
+**Not Included:**
+- ❌ ISO 21434 full text (copyrighted - we have 1 clause guidance only)
+- ❌ Legal advice (regulations ≠ legal interpretation)
+- ❌ Certification decisions (contact type approval authority)
+
+---
+
+## ROI
+
+**Without MCP:**
+- Compliance consultant: $300/hour
+- 10 questions/month = $3,000/month
+- Annual cost: **$36,000**
+
+**With MCP:**
+- Cost: **$0** (open source)
+- Time per question: 2 minutes vs 1 hour
+- Annual savings: **$36,000**
+
+---
+
+## Example Workflow
+
+**Scenario:** You received RFQ asking about R155 compliance
+
+**Traditional Approach (2-3 days):**
+1. Download 200-page R155 PDF
+2. Search for relevant sections
+3. Read entire articles for context
+4. Cross-reference annexes
+5. Write response
+6. Have consultant review
+
+**With MCP (30 minutes):**
+```
+You: "What does R155 require for CSMS documentation?"
+→ Instant article list with references
+
+You: "Show me Article 7.2.2.2 supply chain requirements"
+→ Complete requirement text
+
+You: "What evidence would an auditor expect?"
+→ Guidance on documentation
+
+You: "Draft response email about our compliance"
+→ Claude generates response with citations
+```
+
+---
+
+## Sample Questions to Try
+
+**Understanding Requirements:**
+- "Explain R155 Article 7 in simple terms"
+- "What's the difference between R155 and R156?"
+- "Show me all R155 annexes"
+
+**Finding Specific Info:**
+- "Search R155 for 'vulnerability management'"
+- "What does R155 say about incident response?"
+- "Find all R156 requirements about software updates"
+
+**Creating Documentation:**
+- "Generate compliance checklist from R155 Article 7"
+- "Create gap analysis template for R155"
+- "List all R155 required work products"
+
+**Answering Auditor Questions:**
+- "What evidence does R155 require for CSMS approval?"
+- "Explain R155 Annex 5 threat categories"
+- "What is conformity of production in R155?"
+
+---
+
+## Technical Details
+
+**Database:** 620KB SQLite with FTS5 full-text search
+**Performance:** <1ms query response
+**Content:** 33 regulation items (294KB text)
+**Tests:** 91/91 passing
+**License:** Apache 2.0 (free commercial use)
+
+---
+
+## Need More?
+
+📖 **Full Usage Guide:** `docs/USAGE_GUIDE.md`
+📋 **Integration Summary:** `R155_R156_INTEGRATION_SUMMARY.md`
+🐛 **Issues:** https://github.com/Ansvar-Systems/Automotive-MCP/issues
+📚 **EU Regulations:** https://github.com/Ansvar-Systems/EU_compliance_MCP
+
+---
+
+**Ready? Just ask Claude your first R155/R156 question! 🚀**