Meok Vehicle Handover… vs Emilia Protocol | AllMCPs
Side-by-Side Model Context Protocol Comparison
Meok Vehicle Handover MCP vs Emilia Protocol
In-depth architectural comparison of the Meok Vehicle Handover MCP and Emilia Protocol MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Meok Vehicle Handover MCP
Security · Local stdio
Quality: 34/100 (Emerging) | Auth: No auth required
Emilia Protocol
Security · Local stdio
Quality: 71/100 (Great) | Auth: No auth required
Verdict Summary: Choose Meok Vehicle Handover MCP if you need specialized Security tools running via a local process. Choose Emilia Protocol if your workspace requires Security integration with local subprocess execution. Both servers can be configured concurrently in your client's mcpServers manifest.
Which MCP Server Should You Choose?
Choose Meok Vehicle Handover MCP when:
You need dedicated capabilities in the Security domain.
You prefer local stdio subprocess transport architecture.
Your security boundary fits: No auth required (Free / Open Source).
Vehicle handover compliance — NAMA Vehicle Grading, BVRLA Fair Wear & Tear, photographic POD
Human sign-off + trust receipts for AI agents: requires a named human's approval before an irreversible action (payment release, record change, deploy), then mints an offline-verifiable Ed25519 Trust Receipt. Also exposes trust profiles, receipt verification, disputes, and delegation. Apache-2.0; policy engine formally verified. Install: npx -y @emilia-protocol/mcp-server.
Category & Scope
Tools & Capabilities Breakdown
Meok Vehicle Handover MCP Tools (8)
grade_vehicle_condition
Auto-NAMA grade 1-5 from a panel-damage list.
validate_pod_photo_set
Are the POD photos enough? Count, GPS, resolution, age.
compare_collection_delivery
Diff pre vs post damage lists. Suggest liability.
apply_bvrla_fair_wear_tear
Fair W&T (operator off-hook) vs chargeable per defect.
generate_dispute_pack
Insurer-ready dispute bundle with suggested rebuttal text.
calculate_rha_vs_actual_liability
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Meok Vehicle Handover MCP is categorized under Security and uses a local stdio subprocess. In contrast, Emilia Protocol belongs to Security using local stdio subprocess. Select Meok Vehicle Handover MCP when you need capabilities focused on security and Emilia Protocol when you require tools for security.
£1,300/tonne cap vs claim. Flag if GIT recommended.
submit_to_bvrla_drs
Format dispute pack for BVRLA Dispute Resolution Service.
log_ev_soc_handover
State-of-charge handover record + OEM SLA compliance.
Emilia Protocol Tools (3)
ep_guard_action
Request authorization before an irreversible action: payments, wire transfers, fund releases, deletions, record or account changes, or sending messages with real-world effect. Submits the exact action for policy evaluation and human authorization. This MCP tool does not itself sit at the executor choke point: even after approval, the executor MUST match the returned action_hash and atomically consume the receipt before effect. If BLOCKED, poll ep_check_signoff with the receipt_id.
ep_check_signoff
Poll a pending authorization after ep_guard_action returns BLOCKED. Pass the receipt_id. Returns PENDING, APPROVED_PENDING_CONSUME, CONSUMED, or DENIED. Approval alone is not permission to execute: the executor must match action_hash and atomically consume the receipt at its own choke point.
ep_verify_receipt
Ask the configured EMILIA service to verify a stored trust receipt and report its hash and anchor status. Read-only, but not an offline verifier: the result is the service response for the supplied receipt_id.