
Meok Ev Recall Transport Mcp
io.github.CSOAI-ORGPublished by GitHub account CSOAI-ORGv1.0.4Updated Oct 30, 2026
EV-recall transport compliance — ADR Class 9 (UN3480/3481/3536/3556/3557/3558), DGSA workflow
Overview
Local MCP server that helps an assistant check ADR Class 9 compliance for moving damaged or recalled EVs by UK car transporter.
- What you can do
- Classify a transport job as ADR-exempt or full Class 9 and audit OEM recall protocols
- Draft transport documentation, driver instructions and emergency cards
- Check driver Class 9 endorsement validity and fire-suppression load requirements
- Determine placarding and orange-plate requirements and flag tunnels restricted for Class 9
- Route incident notifications to RIDDOR, DGSA and HSE
- When to use it
- Useful for UK car transport operators and Dangerous Goods Safety Advisers who need quick, repeatable checks and paperwork for damaged or recalled EV movements that fall under ADR Class 9.
- Requirements
- Runs locally as a Python package installed with pip and started as a stdio process, for example from a Claude Desktop config. No authentication or environment variables are declared, though the README mentions an optional MEOK_HMAC_SECRET for signing responses.
Installation
In SourceWeft
- Open Meok Ev Recall Transport Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
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
Claude Desktop config
Tools (8)
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)
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
Source: README.md at commit bc131c3
Tools
0Version history
1- v1.0.4LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts