io.github.CSOAI-ORG/meok-ev-recall-transport-mcp
EV-recall transport compliance — ADR Class 9 (UN3480/3481/3536/3556/3557/3558), DGSA workflow
Installation
Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).
meok-ev-recall-transport-mcpclaude mcp add meok-ev-recall-transport-mcp -- python meok-ev-recall-transport-mcp==1.0.4
{
"mcpServers": {
"meok-ev-recall-transport-mcp": {
"command": "python",
"args": [
"meok-ev-recall-transport-mcp==1.0.4"
]
}
}
}
Documentation
Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.
Sommaire
meok-ev-recall-transport-mcp
ADR Class 9 compliance toolkit for UK car transporters moving damaged or recalled EVs. By MEOK AI Labs.
Why this exists
UK car transporters move millions of vehicles per year. EVs being carried for use are exempt from full ADR rules under §1.1.3.7. But a damaged or RECALLED EV being carried for repair, return, or scrap loses that exemption and becomes full Class 9 dangerous goods — UN3556 (Li-ion), UN3557 (Li-metal), UN3558 (Na-ion).
The ZEV Mandate 2026 forces 33% of new UK car sales to be EV. Recall campaigns are ballooning (LG Chem, Hyundai Kona, Chevy Bolt, Stellantis). A single damaged-EV thermal runaway during transport = corporate manslaughter risk, £1m+ truck loss, £100k+ HSE fine, reputation kill.
This MCP gives car transport operators and DGSAs (Dangerous Goods Safety Advisers) the callable compliance toolkit they have been doing on paper.
Install
pip install meok-ev-recall-transport-mcp
Claude Desktop config
{
"mcpServers": {
"ev-recall-transport": {
"command": "meok-ev-recall-transport-mcp"
}
}
}
Tools (8)
| Tool | Use case |
|---|---|
classify_ev_transport_risk | Is this job ADR-exempt or full Class 9? Decide in seconds. |
generate_adr_class9_documentation | §5.4.1 Transport Document + driver instructions + emergency card. |
check_driver_adr_endorsement | Is the driver Class 9 valid? Expiry warnings. |
validate_vehicle_fire_suppression | ADR §8.1.4 fire-extinguisher load check. |
check_orange_plate_placarding | What goes on the truck — placards + plates per §5.3.2. |
route_thermal_runaway_risk | Flag UK tunnels (Dartford, Rotherhithe, Mersey etc.) banned/restricted for Class 9. |
log_incident_to_dgsa | RIDDOR + DGSA + HSE notification routing. |
audit_oem_recall_compliance | OEM-specific protocols: Tesla, JLR, MG SAIC, Stellantis, BYD. |
Pricing
- Free — MIT self-host
- Starter — £79/mo (signed attestations + email support)
- Pro — £249/mo (DGSA dashboard + multi-user)
- Fleet — £999/mo (50+ trucks, audit-export, SLA)
Subscribe Pro → £79/mo · Talk to Nick
Regulatory basis
- ADR 2025 §1.1.3.7 (transport-for-use exemption + scope)
- ADR 2025 §2.2.9 (Class 9 miscellaneous DG)
- ADR 2025 §3.2 (Dangerous Goods List)
- ADR 2025 §5.3.2 (Marking + placarding)
- ADR 2025 §5.4 (Documentation)
- ADR 2025 §8.1.4 (Fire-extinguisher requirements)
- ADR 2025 §8.2 (Driver training)
- ADR 2025 §1.8.3 (DGSA appointment + duties)
- HSE NIE-1 — Notification of Incident
- RIDDOR 2013 — Reporting of dangerous occurrences
Sign your responses (production)
export MEOK_HMAC_SECRET="your-secret"
meok-ev-recall-transport-mcp
Every tool response returns an HMAC-SHA256 signature for audit-trail evidence.
Companion MCPs
Part of the MEOK Car Transport stack on haulage.app:
meok-car-transport-uk-mcp— DVSA + tacho + C&Umeok-vehicle-handover-mcp— NAMA + BVRLA + PODmeok-ev-recall-transport-mcp— this one
License
MIT © 2026 Nicholas Templeman / MEOK AI Labs · haulage.app
Questions fréquentes
Qu'est-ce que io.github.CSOAI-ORG/meok-ev-recall-transport-mcp ?
EV-recall transport compliance — ADR Class 9 (UN3480/3481/3536/3556/3557/3558), DGSA workflow
Comment installer io.github.CSOAI-ORG/meok-ev-recall-transport-mcp ?
Il s'exécute sur votre machine. Dans Claude Code : claude mcp add meok-ev-recall-transport-mcp -- python meok-ev-recall-transport-mcp==1.0.4. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.
Faut-il une clé API pour io.github.CSOAI-ORG/meok-ev-recall-transport-mcp ?
Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.
io.github.CSOAI-ORG/meok-ev-recall-transport-mcp est-il open source ?
Oui. Son code est sur GitHub sous licence MIT.
Qui maintient io.github.CSOAI-ORG/meok-ev-recall-transport-mcp ?
Il est publié par CSOAI-ORG. AI.tn le référence sans le maintenir ni le recommander.
Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.