Automotive Cybersecurity MCP server

by Ansvar-Systems·io.github.Ansvar-Systems/automotive-cybersecurity·v1.0.1

Automotive cybersecurity: R155/R156 regulations, ISO 21434, TISAX, AUTOSAR, Chinese GB/T

C65/100grade C

What users say

No reviews yet

Safety scan

C65/100

Adoption

New

45 downloads/wk

Reviews

Nobody has reviewed Automotive Cybersecurity yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

export_compliance_matrix
Generate a compliance traceability matrix showing regulation requirements mapped to ISO 21434 clauses and work products. Export as Markdown table or CSV for spreadsheet import. Useful for audit documentation, gap analysis, and compliance tracking.
get_requirement
Retrieve a specific regulation article or standard clause. For regulations (UNECE R155/R156), returns full text. For standards (ISO 21434), returns guidance and work products only (full text requires paid license). Optionally includes cross-framework mappings.
list_sources
List available automotive cybersecurity regulations and standards. Returns metadata including version, type (regulation/standard), item counts, and whether full text is available.
list_work_products
List ISO 21434 work products (deliverables) required for cybersecurity engineering. Shows which artifacts to produce for each clause, whether CAL-dependent, and which R155 requirements they help satisfy. Filter by specific clause or lifecycle phase.
search_requirements
Full-text search across all regulations and standards using FTS5 with BM25 ranking. Search regulations (UNECE R155/R156 full text) and standards (ISO 21434 guidance). Returns results sorted by relevance with highlighted snippets. Useful for finding requirements by topic, keyword, or concept.

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

no findings

Code scan21 source files scanned25/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancerepository not readable: repo not found3/15
Maintainer identityno repository or website to verify2/10

Overall 65/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

Runs npx -y @ansvar/automotive-cybersecurity-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add automotive-cybersecurity -- npx -y @ansvar/automotive-cybersecurity-mcp

Is Automotive Cybersecurity MCP server safe?: With care: it is graded C, so read the findings first (65/100). Read the Automotive Cybersecurity safety report
How do I install Automotive Cybersecurity?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Automotive Cybersecurity need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Automotive Cybersecurity maintained?: The latest release is v1.0.1.