Automotive Cybersecurity
Let your coding agent look up UN R155/R156, ISO 21434, TISAX, AUTOSAR, and Chinese GB/T while you design automotive software or security docs.
Overview
io.github.Ansvar-Systems/automotive-cybersecurity is a MCP server for the Ship phase that lets agents query automotive cybersecurity regulations and standards including R155/R156, ISO 21434, TISAX, AUTOSAR, and Chinese G
What is this MCP server?
- Covers UN R155/R156, ISO 21434, TISAX, AUTOSAR, and Chinese GB/T in one MCP surface
- Stdio npm package @ansvar/automotive-cybersecurity-mcp v1.0.1 for Claude Code, Cursor, and similar agents
- Purpose-built for automotive OEMs, suppliers, and embedded builders—not general web SaaS compliance
- Reduces manual PDF and standards browsing when drafting cybersecurity management evidence
- MCP integration that queries a structured compliance corpus, not a one-off prompt skill
- Server version 1.0.1 on npm as @ansvar/automotive-cybersecurity-mcp
- Stdio transport per MCP registry schema 2025-12-11
- Corpus spans R155/R156, ISO 21434, TISAX, AUTOSAR, and Chinese GB/T per publisher description
What problem does it solve?
Vehicle and embedded builders waste hours jumping between ISO, UN, and regional automotive cyber texts when the agent could answer in context.
Who is it for?
Indie or small-team builders shipping automotive or embedded connectivity who already use MCP and need regulation-aware drafting help.
Skip if: Solo web-SaaS founders who only need GDPR or generic OWASP guidance without automotive scope.
What do I get? / Deliverables
After you register the server, compliance-oriented questions get answers anchored in named automotive frameworks while you draft specs and security artifacts.
- Agent-grounded excerpts and explanations tied to named automotive cyber frameworks
- Faster drafts for cybersecurity management and supplier compliance narratives
- Repeatable MCP-backed Q&A without opening multiple standards portals
Recommended MCP Servers
Journey fit
How it compares
MCP compliance corpus for automotive standards, not a generic security audit skill or static checklist markdown.
Common Questions / FAQ
Who is io.github.Ansvar-Systems/automotive-cybersecurity for?
It is for developers and security leads in automotive supply chains who want Claude Code or Cursor to cite R155/R156, ISO 21434, TISAX, AUTOSAR, and GB/T while writing cyber documentation.
When should I use io.github.Ansvar-Systems/automotive-cybersecurity?
Use it during Ship-phase security work when you are mapping controls, preparing CSMS evidence, or explaining regulatory obligations before release or customer audit.
How do I add io.github.Ansvar-Systems/automotive-cybersecurity to my agent?
Install @ansvar/automotive-cybersecurity-mcp from npm, run it as a stdio MCP server, and add that command to your client’s MCP server list per the Automotive-MCP repository README.